All autopkgtests for the newly accepted linux-firmware (20220329.git681281e4-0ubuntu3.33) for jammy have finished running. The following regressions have been reported in tests triggered by the package:
linux-firmware-raspi/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-firmware [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2077490 Title: Error: out of memory while booting after installing the linux-firmware in proposed Status in initramfs-tools package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] I found that there are some machines in cert lab can't boot after installing the linux-frimware in proposed with 6.8.0-40 kernel. After selecting booting with the 6.8.0-40 kernel, it shows error: out of memory on the screen then freeze. There aren't any journal logs available, since they froze at very early stage. Following are the machines got impacted for now https://certification.canonical.com/hardware/202306-31695/ https://certification.canonical.com/hardware/202306-31696/ Problem details: The linux-firmware package provides new (gigantic) firmware blobs and symlinks to directories that contain those. initramfs-tools can't handle the directory symlinks and puts multiple copies of the same blobs into the initrd blowing it up to a size where it becomes problematic on some machines. [Test Case] Verify the affected machine boots again with the updated firmware package. Install updated linux-firmware package and confirm that there are no duplicate firmware files in /lib/firmware and inside the initrd. Also verify that there are no broken symlinks. [Where Problems Could Occur] If the new symlinks are broken, we end up with drivers not finding their firmwares which results in non-functional HW components. [Notes] This is not a general solution for the problem of the ever growing size of the initrd. It just alleviate it some. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2077490/+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
