We have over the last month or so seen a fairly substantial number bricked devices that all end up in the following state (as in multiple reports per day):
Here are some observations:
- It happens both on RPI3 and CM3
- It appears to happen when snapd is upgrading
- It’s hard to reproduce and our theory is that it happens when snapd is upgrading between certain versions
If you connect a serial console to the device, this is the out you receive:
-Boot 2017.05-dirty (Mar 12 2018 - 09:55:39 +0000) DRAM: 752 MiB RPI 3 Model B (0xa22082) MMC: bcm2835_sdhci: 0 reading uboot.env In: serial Out: serial Err: lcd Net: Net Initialization Skipped No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device LOADBOOTENV reading uEnv.txt ** Unable to read file uEnv.txt ** Running uenvcmd ... ENVCMD Saving Environment to FAT... writing uboot.env FAT: Misaligned buffer address (2eb00560) FAT: Misaligned buffer address (2eb00760) done reading pi2-kernel_52.snap/kernel.img 5724256 bytes read in 919 ms (5.9 MiB/s) reading pi2-kernel_52.snap/initrd.img 3059751 bytes read in 509 ms (5.7 MiB/s) reading psplash.img FAT: Misaligned buffer address (023eb027) 1343508 bytes read in 6139 ms (212.9 KiB/s) Kernel image @ 0x200000 [ 0x000000 - 0x575860 ] ## Flattened Device Tree blob at 02000000 Booting using the fdt blob at 0x2000000 Loading Ramdisk to 2e6ec000, end 2eb1f03b ... OK Loading Device Tree to 2e6e4000, end 2e6eb350 ... OK Starting kernel ...
After the last line, it is unresponsive (both over the serial console and with a keyboard).
We’ve also provided @ondra with a disk image.
Since we cannot control these updates, it is also rather unpredictable but we have had at least 20 devices in this state over the last week or two.