This bug is awaiting verification that the linux-raspi/5.13.0-1018.20 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1959102 Title: Kernel fails to boot in ScalingStack Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi-5.4 package in Ubuntu: Invalid Status in linux-raspi-5.4 source package in Bionic: New Status in linux-raspi source package in Focal: Fix Committed Status in linux-raspi source package in Impish: Fix Committed Status in linux-raspi source package in Jammy: Fix Released Bug description: [ Impact ] The raspi kernel fails to boot in ScalingStack which is our OpenStack cluster for running ADT/autopkgtest tests. [ Test Case ] Boot a VM in ScalingStack, install raspi kernel, reboot. VM won't come back. [ Fix ] Enable VIRTIO PCI driver. ScalingStack uses virtio so the guest kernel needs to support that. [ Where Problems Could Occur ] New module means new code which could trigger kernel problems when loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1959102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
