fastboot sometimes stops finding devices and needs a chroot 'shutdown'

Just a small inconvenience: While working with my Xperia Z1C (amami) device on Arch Linux, there have been a few instances where pmbootstrap flasher stops seeing the device. Flashing commands get stuck in < waiting for any device >.

However, when I run fastboot devices or other commands outside the chroot, they work fine.

The workaround is to shut down the chroot using pmbootstrap shutdown; next time around it works again. I have now documented this on the wiki: https://wiki.postmarketos.org/wiki/Troubleshooting#flasher_.28fastboot.29_is_stuck_in_.3C_waiting_for_any_device_.3E

changed the description

By Marti Raudsepp on 2018-08-06T21:40:17

If you encounter this again, could you please do the following:

• compare mountpoints
  • run mount > /tmp/broken.txt to save the currently set mountpoints
  • run shutdown and flasher again, so it's working
  • run mount > /tmp/working.txt to save the currently set mountpoints
  • run diff /tmp/broken.txt /tmp/working.txt, now it should show the difference.
• if you would like to, you could also attach strace on the stuck fastboot process to see what it is waiting for (but providing the mountpoint diff from above would already be very helpful!)

Thanks for reporting this and especially for documenting your workaround in the wiki, @intgr!

By Oliver Smith on 2018-08-15T20:45:45

mentioned in commit wiki@0702c58a

By postmarketOS Wiki bot on 2018-08-15T21:42:56