▎ Sorry for the confusion — the failed-boot.log is not the failed attempt itself. Both boots run 7.0.0-1020-raspi because the new boot assets were the same kernel: the only file differing ▎ between /boot/firmware/new and /boot/firmware/current is initrd.img (regenerated by an initramfs-tools trigger during apt upgrade on 2026-11-06; 84753441 → 84753583 bytes). Kernel, DTBs, ▎ overlays, firmware and cmdline.txt are identical. ▎ ▎ Sequence on 2026-11-08: ▎ - boot -1 (failed-boot.log): normal boot from current/; piboot-try-reboot should set new→trying and reboot "1 tryboot". The journal ends ~1 s in, before that is logged. ▎ - boot 0: booted from current/ again with /proc/device-tree/chosen/bootloader/tryboot = 0 (partition = 1), so piboot-try-reboot hit the 0/-/good/trying case and logged "Marked new boot ▎ assets bad". current/state = good, new/state = bad. ▎ ▎ So the new assets never reached Linux: either the tryboot reboot didn't happen or the bootloader fell back to current/ before loading the kernel. That is why there is no kernel log of ▎ the failed attempt. The same mechanism worked on 2026-10-29 (tryboot boot, then "Switched new boot assets to current successfully") with the same disks attached. ▎ ▎ Hardware: Raspberry Pi 5 Model B Rev 1.0, piboot-try 1.1ubuntu0.1, Ubuntu 26.04.1.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2173687 Title: Raspberry Pi 5: new linux-raspi kernel hangs during early userspace (udev coldplug), piboot-try falls back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2173687/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
