Closed studavekar closed 6 years ago
@tkaman / @hug-dev ..could you please take a look at this?
Hi @studavekar I will look into this and try to see what we can do!
Hi @studavekar, I could not reproduce the problem so far. How often did you see this? Only once or many times? What I experienced is that the D drive disconnected, and did not reconnected until I manually reseted the board. Did you experienced this issue, or just the no space left problem?
Which HT version are you using? I am using 1.3.1. As I see you are using Linux. Did you try this with Windows as well?
Anyway, this does not seem like a HAL issue, it is rather a MPS2 board or maybe an environment problem.
I could not reproduce this issue as well (having executed around 15 tests).
The only thing I could see sometimes is that after copying the reboot.txt
file and after the board reboots, it is not automounted by the OS anymore, I had to manually mount it or in the worst case reset the board manually (pushing the RESET
button).
Configuration:
mbedgt
version 1.3.3
mbedls
version 1.4.1
mbedhtrun
version 1.3.1
2.2.6
@studavekar ..bump!
@tkaman @hug-dev
Hi @studavekar, I could not reproduce the problem so far. How often did you see this? Only once or many times?
Once we see this problem I have no way to recover the device. Cold hot, unplugging sdcard doesn't help much.
What I experienced is that the D drive disconnected, and did not reconnected until I manually reseted the board. Did you experienced this issue, or just the no space left problem?
Yes i did see this issue, as you pointed out resetting device helps to recover.
Which HT version are you using? I am using 1.3.1.
yes 1.3.1
As I see you are using Linux. Did you try this with Windows as well?
I am using Linux.
Anyway, this does not seem like a HAL issue, it is rather a MPS2 board or maybe an environment problem.
@hug-dev
I could not reproduce this issue as well (having executed around 15 tests). This board was connected in staging CI, The number of tests it executed were of higher order.
on side one was on vacation and have few more devices let me try to reproduce it on other device.
Did an overnight test with 2 boards didn't see No space left on device
issue. However tests were stopped stalled because of device failed to reboot using reboot,txt.
@ashok-rao , @studavekar Can we close this ticket now? Looks like the problem is seen only once, so we can't make progress on this.
For the reboot issue you can open a new ticket, although it should be investigated by the MPS2 team, as it does not look like a CM3DS issue. Let me know if you need anything from our side.
closing this ticket as we are not able to reproduce this issue. Have opened https://github.com/ARMmbed/mbed-os/issues/6966 for tracking reboot.txt not been rebooting the device.
Description
Bug
Target ARM_CM3DS_MPS2
Toolchain: GCC_ARM|ARM|IAR
mbed-cli version: 1.5.0
mbed-os sha: d97d55a Merge pull request #6450 from 0xc0170/fix_#6449
Expected behavior During the execution of tests, the device storage should not be used up.
Actual behavior we see No space left on device error
Steps to reproduce Running tests in loop mbed test -m ARM_CM3DS_MPS2 -t GCC_ARM -v
Snippet of exception
arm@austin-ci-linux-002:/mnt$ df -i /mnt/pci-0000_00_14_0-usb-0_7_1_0-scsi-0_0_0_0 Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sdb1 0 0 0 - /mnt/pci-0000_00_14_0-usb-0_7_1_0-scsi-0_0_0_0
arm@austin-ci-linux-002:/mnt/pci-0000_00_14_0-usb-0_7_1_0-scsi-0_0_0_0$ touch reboot.txt touch: cannot touch 'reboot.txt': No space left on device
arm@austin-ci-linux-002:/mnt/pci-0000_00_14_0-usb-0_7_1_0-scsi-0_0_0_0$ ls config.txt MB mbed.elf mbed.htm SOFTWARE System Volume Information
arm@austin-ci-linux-002:/mnt/pci-0000_00_14_0-usb-0_7_1_0-scsi-0_0_0_0$ rm mbed.elf
arm@austin-ci-linux-002:/mnt/pci-0000_00_14_0-usb-0_7_1_0-scsi-0_0_0_0$ touch reboot.txt