** Changed in: snapd
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2114779
Title:
Unable to boot to 6.8.0-1029.33 pi-kernel
Status in canonical-kernel-snaps:
Invalid
Status in snapd:
Fix Released
Status in linux-raspi package in Ubuntu:
Invalid
Status in snapd package in Ubuntu:
Fix Released
Status in snapd source package in Jammy:
Fix Released
Status in snapd source package in Noble:
Fix Released
Status in snapd source package in Plucky:
Fix Released
Bug description:
[SRU] 2.71:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2118396
[ Impact ]
Ubuntu Core & snapd snap only.
Requires a new version of initrd and per implication a new kernel build.
Unable to boot after refresh to 6.8.0-1029.33 and this triggers
automatic rollback to previous kernel.
[ Test Plan ]
This test is best suited for the reporting team using the same setup
as was used when the issue was encountered. Alfonso B confirmed the
new initrd and kernel was released.
1. Not required to reproduce the issue, it is clear that non-gpt was
not supported in fallback mode for RPi.
2. Prove fix with new kernel that includes the initrd with the changes
in snap-bootstrap based on snapd 2.71
Provision a rpi4b8g with UC24 dangerous grade ARM64 raspi image with
Testflinger.
Run `sudo snap refresh pi-kernel --channel=24/edge` on the target
system.
---original---
Test steps:
1. Provision a rpi4b8g with UC24 dangerous grade ARM64 raspi image with
Testflinger.
2. Run `sudo snap refresh pi-kernel --channel=24/edge` on the target system.
Expected result:
* System can boot with 6.8.0-1029.33 pi-kernel.
Actual result:
* System failed to boot with 6.8.0-1029.33 pi-kernel and it automatically
rollback to the previous kernel.
Output from `snap changes`
ubuntu@localhost:~$ snap changes
ID Status Spawn Ready Summary
1 Done today at 13:05 UTC today at 13:07 UTC Initialize system state
2 Done today at 13:07 UTC today at 13:07 UTC Initialize device
3 Done today at 13:07 UTC today at 13:11 UTC Auto-refresh 4 snaps
4 Error today at 13:43 UTC today at 13:44 UTC Refresh "pi-kernel" snap
from "24/edge" channel
ubuntu@localhost:~$ sudo snap change 4
Status Spawn Ready Summary
Done today at 13:43 UTC today at 13:44 UTC Ensure prerequisites for
"pi-kernel" are available
Undone today at 13:43 UTC today at 13:44 UTC Download snap "pi-kernel"
(989) from channel "24/edge"
Done today at 13:43 UTC today at 13:44 UTC Fetch and check assertions
for snap "pi-kernel" (989)
Undone today at 13:43 UTC today at 13:44 UTC Mount snap "pi-kernel" (989)
Undone today at 13:43 UTC today at 13:44 UTC Run pre-refresh hook of
"pi-kernel" snap if present
Undone today at 13:43 UTC today at 13:44 UTC Stop snap "pi-kernel" services
Undone today at 13:43 UTC today at 13:44 UTC Remove aliases for snap
"pi-kernel"
Undone today at 13:43 UTC today at 13:44 UTC Make current revision for
snap "pi-kernel" unavailable
Undone today at 13:43 UTC today at 13:44 UTC Prepare kernel driver tree
for "pi-kernel" (989)
Done today at 13:43 UTC today at 13:44 UTC Update assets from kernel
"pi-kernel" (989)
Undone today at 13:43 UTC today at 13:44 UTC Copy snap "pi-kernel" data
Undone today at 13:43 UTC today at 13:44 UTC Setup snap "pi-kernel" (989)
security profiles
Undone today at 13:43 UTC today at 13:44 UTC Make snap "pi-kernel" (989)
available to the system
Error today at 13:43 UTC today at 13:44 UTC Automatically connect
eligible plugs and slots of snap "pi-kernel"
Hold today at 13:43 UTC today at 13:44 UTC Set automatic aliases for
snap "pi-kernel"
Hold today at 13:43 UTC today at 13:44 UTC Setup snap "pi-kernel" aliases
Hold today at 13:43 UTC today at 13:44 UTC Run post-refresh hook of
"pi-kernel" snap if present
Hold today at 13:43 UTC today at 13:44 UTC Discard previous kernel
driver tree for "pi-kernel" (989)
Hold today at 13:43 UTC today at 13:44 UTC Start snap "pi-kernel" (989)
services
Hold today at 13:43 UTC today at 13:44 UTC Clean up "pi-kernel" (989)
install
Hold today at 13:43 UTC today at 13:44 UTC Run configure hook of
"pi-kernel" snap if present
Hold today at 13:43 UTC today at 13:44 UTC Run health check of
"pi-kernel" snap
Done today at 13:43 UTC today at 13:44 UTC Monitoring snap "pi-kernel"
to determine whether extra refresh steps are required
......................................................................
Update assets from kernel "pi-kernel" (989)
2025-06-16T13:43:54Z INFO No gadget assets update needed
......................................................................
Make snap "pi-kernel" (989) available to the system
2025-06-16T13:43:54Z INFO Task set to wait until a system restart
allows to continue
......................................................................
Automatically connect eligible plugs and slots of snap "pi-kernel"
2025-06-16T13:44:07Z ERROR cannot finish pi-kernel installation, there
was a rollback across reboot
......................................................................
Monitoring snap "pi-kernel" to determine whether extra refresh steps are
required
2025-06-16T13:43:54Z INFO Task set to wait until a system restart
allows to continue
The following log is the serial console output that I monitored before
running the `refresh` command and `reboot`:
Ubuntu Core 24 on 127.0.0.1 (ttyS0)
localhost login:
Ubuntu Core 24 on $IP-redacted (ttyS0)
localhost login: [ 224.289681] watchdog: watchdog0: watchdog did not stop!
[ 224.955881] (sd-umoun[2290]: Failed to unmount
/run/shutdown/mounts/f013da2d4005fb00: Device or resource busy
[ 224.981707] (sd-remou[2291]: Failed to remount
'/run/shutdown/mounts/73e1fdd754a5199d' read-only: Device or resource busy
[ 224.996895] (sd-umoun[2292]: Failed to unmount
/run/shutdown/mounts/73e1fdd754a5199d: Device or resource busy
[ 225.025081] shutdown[1]: Could not detach loopback /dev/loop1: Device or
resource busy
[ 225.033540] shutdown[1]: Unable to finalize remaining file systems, loop
devices, ignoring.
[ 225.149315] reboot: Restarting system with command '0 tryboot'
[ 102.135157] watchdog: watchdog0: watchdog did not stop!
[ 102.277385] reboot: Restarting system
[ 16.283965] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { P879 } 21 jiffies s: 429 root: 0x0/T
[ 16.306243] rcu: blocking rcu_node structures (internal RCU debug):
[ 16.538967] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { P879 } 21 jiffies s: 445 root: 0x0/T
[ 16.563957] rcu: blocking rcu_node structures (internal RCU debug):
[ 19.110982] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { P905 } 21 jiffies s: 501 root: 0x0/T
[ 19.137973] rcu: blocking rcu_node structures (internal RCU debug):
Ubuntu Core 24 on 127.0.0.1 (ttyS0)
localhost login:
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2114779/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
