Public bug reported:
Description:
Upon updating to kernel 7.0.0-1015-raspi in resolute-proposed, piboot-try
staged boot assets in /boot/firmware/new/ and initiated a test boot. piboot-try
fails and reverted to a known good image.
There are no journald logs for the -1015 boot attempt which indicates
there may be an underlying issue while attempting to boot this kernel
version.
=== SYSTEM & HARDWARE INFO ===
Linux ubuntu 7.0.0-1009-raspi #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Apr 13 16:37:04
UTC 2026 aarch64 GNU/Linux
PRETTY_NAME="Ubuntu 26.04 LTS"
VERSION_CODENAME=resolute
Raspberry Pi Compute Module 4 Rev 1.0
=== INSTALLED KERNELS & INITRD ===
ii linux-image-7.0.0-1009-raspi 7.0.0-1009.9
arm64 Linux kernel image for version 7.0.0
ii linux-image-7.0.0-1014-raspi 7.0.0-1014.14
arm64 Linux kernel image for version 7.0.0
ii linux-image-7.0.0-1015-raspi 7.0.0-1015.15
arm64 Linux kernel image for version 7.0.0
ii linux-image-raspi 7.0.0-1015.15
arm64 Raspberry Pi Linux kernel image
ii linux-modules-7.0.0-1009-raspi 7.0.0-1009.9
arm64 Linux kernel modules for version 7.0.0
ii linux-modules-7.0.0-1014-raspi 7.0.0-1014.14
arm64 Linux kernel modules for version 7.0.0
ii linux-modules-7.0.0-1015-raspi 7.0.0-1015.15
arm64 Linux kernel modules for version 7.0.0
ii piboot-try 1.1ubuntu0.1
arm64 manages the A/B boot mechanism on the Raspberry Pi
lrwxrwxrwx 1 root root 27 Jul 28 00:01 /boot/initrd.img ->
initrd.img-7.0.0-1015-raspi
-rw------- 1 root root 63M Jul 27 23:43 /boot/initrd.img-7.0.0-1009-raspi
-rw------- 1 root root 63M Jul 28 00:02 /boot/initrd.img-7.0.0-1014-raspi
-rw------- 1 root root 68M Jul 28 00:13 /boot/initrd.img-7.0.0-1015-raspi
lrwxrwxrwx 1 root root 27 Jul 28 00:01 /boot/initrd.img.old ->
initrd.img-7.0.0-1014-raspi
lrwxrwxrwx 1 root root 24 Jul 28 00:01 /boot/vmlinuz ->
vmlinuz-7.0.0-1015-raspi
-rw------- 1 root root 15M Apr 13 14:57 /boot/vmlinuz-7.0.0-1009-raspi
-rw------- 1 root root 15M Jun 29 12:25 /boot/vmlinuz-7.0.0-1014-raspi
-rw------- 1 root root 15M Jun 30 13:57 /boot/vmlinuz-7.0.0-1015-raspi
lrwxrwxrwx 1 root root 24 Jul 28 00:01 /boot/vmlinuz.old ->
vmlinuz-7.0.0-1014-raspi
=== PIBOOT-TRY STATES ===
/boot/firmware/current/state: good
/boot/firmware/new/state: bad
=== BOOT CONFIGURATION ===
--- config.txt ---
[all]
os_prefix=current/
[tryboot]
os_prefix=new/
[all]
arm_64bit=1
kernel=vmlinuz
cmdline=cmdline.txt
initramfs initrd.img followkernel
# Enable the audio output, I2C and SPI interfaces on the GPIO header. As these
# parameters related to the base device-tree they must appear *before* any
# other dtoverlay= specification
dtparam=audio=on
dtparam=i2c_arm=on
dtparam=spi=on
dtparam=watchdog=on
# Comment out the following line if the edges of the desktop appear outside
# the edges of your display
disable_overscan=1
# If you have issues with audio, you may try uncommenting the following line
# which forces the HDMI output into HDMI mode instead of DVI (which doesn't
# support audio output)
#hdmi_drive=2
# Enable the KMS ("full" KMS) graphics overlay, leaving GPU memory as the
# default (the kernel is in control of graphics memory with full KMS)
dtoverlay=vc4-kms-v3d
disable_fw_kms_setup=1
# Enable the serial pins
enable_uart=1
# Autoload overlays for any recognized cameras or displays that are attached
# to the CSI/DSI ports. Please note this is for libcamera support, *not* for
# the legacy camera stack
camera_auto_detect=1
display_auto_detect=1
# Config settings specific to arm64
dtoverlay=dwc2
[pi4]
max_framebuffers=2
arm_boost=1
[pi3+]
# Use a smaller contiguous memory area, specifically on the 3A+ to avoid an
# OOM oops on boot. The 3B+ is also affected by this section, but it shouldn't
# cause any issues on that board
dtoverlay=vc4-kms-v3d,cma-128
[pi02]
# The Zero 2W is another 512MB board which is occasionally affected by the same
# OOM oops on boot.
dtoverlay=vc4-kms-v3d,cma-128
[cm4]
# Enable the USB2 outputs on the IO board (assuming your CM4 is plugged into
# such a board)
dtoverlay=dwc2,dr_mode=host
[all]
dtoverlay=dwc2
=== Journalctl ===
-- list-boots --
journalctl --list-boots
IDX BOOT ID FIRST ENTRY LAST ENTRY
-8 f7a95a86f4244e1a9706f27c82ea5601 Mon 2026-07-27 23:53:58 UTC Mon 2026-07-27
23:55:34 UTC
-7 6cc1e5d916fc400a9029d37444f7df86 Wed 2026-04-15 18:32:54 UTC Wed 2026-04-15
18:33:09 UTC
-6 66c044221e334fdd82a463e3a7ba27a5 Wed 2026-04-15 18:32:54 UTC Tue 2026-07-28
00:05:54 UTC
-5 2569d9a6a7324c8598b9bd5811c40e50 Wed 2026-04-15 18:32:54 UTC Wed 2026-04-15
18:33:08 UTC
-4 00e5d0b6aa3442f78a7ddd4c04745845 Wed 2026-04-15 18:32:54 UTC Tue 2026-07-28
00:14:05 UTC
-3 683fd8eed8714d8baa5ca138439cf997 Wed 2026-04-15 18:32:54 UTC Wed 2026-07-22
17:07:29 UTC
-2 6fcf87b9f3f64472b2d38a2b97f75711 Wed 2026-04-15 18:32:54 UTC Tue 2026-07-28
00:16:00 UTC
-1 fa8388dfcde845aaa9b29b242db793be Wed 2026-04-15 18:32:54 UTC Tue 2026-07-28
00:25:27 UTC
0 db7cdb6127244f09919bed541aa66d56 Wed 2026-04-15 18:32:54 UTC Tue 2026-07-28
00:41:11 UTC
-- last journalctl --
Jul 27 23:55:33 ubuntu systemd[1]: finalrd.service: Deactivated successfully.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped finalrd.service - Create final
runtime dir for shutdown pivot root.
Jul 27 23:55:33 ubuntu systemd[1]: finalrd.service: Consumed 2.714s CPU time
over 24min 38.479s wall clock time, 46.3M memory peak.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped target local-fs.target - Local File
Systems.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped target snapd.mounts.target - Mounted
snaps.
Jul 27 23:55:33 ubuntu systemd[1]: Unmounting boot-firmware.mount -
/boot/firmware...
Jul 27 23:55:33 ubuntu systemd[1]: Unmounting snap-snapd-26869.mount - Mount
unit for snapd, revision 26869...
Jul 27 23:55:33 ubuntu systemd[1]: Unmounting tmp.mount - Temporary Directory
/tmp...
Jul 27 23:55:33 ubuntu systemd[1]: tmp.mount: Deactivated successfully.
Jul 27 23:55:33 ubuntu systemd[1]: Unmounted tmp.mount - Temporary Directory
/tmp.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped target swap.target - Swaps.
Jul 27 23:55:33 ubuntu systemd[1]: snap-snapd-26869.mount: Deactivated
successfully.
Jul 27 23:55:33 ubuntu systemd[1]: Unmounted snap-snapd-26869.mount - Mount
unit for snapd, revision 26869.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped target snapd.mounts-pre.target -
Mounting snaps.
Jul 27 23:55:33 ubuntu systemd[1]: boot-firmware.mount: Deactivated
successfully.
Jul 27 23:55:33 ubuntu systemd[1]: Unmounted boot-firmware.mount -
/boot/firmware.
Jul 27 23:55:33 ubuntu systemd[1]: Reached target umount.target - Unmount All
Filesystems.
Jul 27 23:55:33 ubuntu systemd[1]:
systemd-fsck@dev-disk-by\x2dlabel-system\x2dboot.service: Deactivated
successfully.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped
systemd-fsck@dev-disk-by\x2dlabel-system\x2dboot.service - File System Check on
/dev/disk/by-label/system-boot.
Jul 27 23:55:33 ubuntu systemd[1]: Removed slice system-systemd\x2dfsck.slice -
Slice /system/systemd-fsck.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped target local-fs-pre.target -
Preparation for Local File Systems.
Jul 27 23:55:33 ubuntu systemd[1]: Stopping lvm2-monitor.service - Monitoring
of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Jul 27 23:55:33 ubuntu systemd[1]: systemd-tmpfiles-setup-dev.service:
Deactivated successfully.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped systemd-tmpfiles-setup-dev.service -
Create Static Device Nodes in /dev.
Jul 27 23:55:33 ubuntu systemd[1]: systemd-sysusers.service: Deactivated
successfully.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped systemd-sysusers.service - Create
System Users.
Jul 27 23:55:33 ubuntu systemd[1]: systemd-remount-fs.service: Deactivated
successfully.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped systemd-remount-fs.service - Remount
Root and Kernel File Systems.
Jul 27 23:55:33 ubuntu systemd[1]: systemd-fsck-root.service: Deactivated
successfully.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped systemd-fsck-root.service - File
System Check on Root Device.
Jul 27 23:55:33 ubuntu systemd[1]: systemd-tmpfiles-setup-dev-early.service:
Deactivated successfully.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped
systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev
gracefully.
Jul 27 23:55:33 ubuntu systemd[1]: lvm2-monitor.service: Deactivated
successfully.
Jul 27 23:55:33 ubuntu systemd[1]: Stopped lvm2-monitor.service - Monitoring of
LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Jul 27 23:55:33 ubuntu systemd[1]: Reached target shutdown.target - System
Shutdown.
Jul 27 23:55:33 ubuntu systemd[1]: Reached target final.target - Late Shutdown
Services.
Jul 27 23:55:33 ubuntu systemd[1]: systemd-reboot.service: Deactivated
successfully.
Jul 27 23:55:33 ubuntu systemd[1]: Finished systemd-reboot.service - System
Reboot.
Jul 27 23:55:33 ubuntu systemd[1]: Reached target reboot.target - System Reboot.
Jul 27 23:55:33 ubuntu systemd[1]: Shutting down.
Jul 27 23:55:33 ubuntu systemd[1]: Using hardware watchdog /dev/watchdog0:
'Broadcom BCM2835 Watchdog timer', version 0.
Jul 27 23:55:33 ubuntu systemd[1]: Watchdog running with a hardware timeout of
10min.
Jul 27 23:55:33 ubuntu kernel: watchdog: watchdog0: watchdog left running
Jul 27 23:55:33 ubuntu systemd-shutdown[1]: Using hardware watchdog
/dev/watchdog0: 'Broadcom BCM2835 Watchdog timer', version 0.
Jul 27 23:55:33 ubuntu systemd-shutdown[1]: Watchdog running with a hardware
timeout of 10min.
Jul 27 23:55:33 ubuntu systemd-shutdown[1]: Syncing filesystems and block
devices.
Jul 27 23:55:34 ubuntu systemd-shutdown[1]: Sending SIGTERM to remaining
processes...
Jul 27 23:55:34 ubuntu systemd-journald[18520]: Received SIGTERM from PID 1
(systemd-shutdow).
Jul 27 23:55:34 ubuntu systemd-udevd[18529]: Failed to remove file descriptor
"config-serialization" from the store, ignoring: Connection refused
Jul 27 23:55:34 ubuntu systemd-journald[18520]: Journal stopped
=== Manual steps ===
I manually attempted without success:
$ sudo piboot-try --reset-new
Marked new boot assets unknown
Please be aware next reboot will boot twice
$ sudo piboot-try --reboot
Rebooting to test new boot assets
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2161936
Title:
[CM4] Unable to boot 7.0.0-1015-raspi from resolute proposed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2161936/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
