Verified running autopkgtest locally using LXD. 1. Create an autopkgtest image:
$ autopkgtest-build-lxd ubuntu-daily:jammy 2. Verify current linux-firmware 20220329.git681281e4-0ubuntu3.37 is broken: $ autopkgtest initramfs-tools -- lxd autopkgtest/ubuntu/jammy/amd64 2>&1 | tee bad.log $ grep 'Setting up linux-firmware' bad.log Setting up linux-firmware (20220329.git681281e4-0ubuntu3.37) ... Setting up linux-firmware (20220329.git681281e4-0ubuntu3.37) ... $ tail bad.log autopkgtest [16:21:53]: @@@@@@@@@@@@@@@@@@@@ summary shellcheck PASS (superficial) unit-tests PASS qemu-klibc PASS qemu-busybox PASS qemu-ata-only FAIL stderr: find: ‘/tmp/autopkgtest.Vhn6Jo/autopkgtest_tmp/mkinitramfs_B56ASN/lib/firmware’: No such file or directory qemu-virtio-only FAIL stderr: find: ‘/tmp/autopkgtest.Vhn6Jo/autopkgtest_tmp/mkinitramfs_6UVa4n/lib/firmware’: No such file or directory qemu-separate-usr FAIL stderr: find: ‘/tmp/autopkgtest.Vhn6Jo/autopkgtest_tmp/mkinitramfs_CDItZf/lib/firmware’: No such file or directory qemu-panic-shell FAIL stderr: find: ‘/tmp/autopkgtest.Vhn6Jo/autopkgtest_tmp/mkinitramfs_3fbzdR/lib/firmware’: No such file or directory qemu-net FAIL stderr: find: ‘/tmp/autopkgtest.Vhn6Jo/autopkgtest_tmp/mkinitramfs_EBUZvp/lib/firmware’: No such file or directory 3. Verify linux-firmware 20220329.git681281e4-0ubuntu3.38 from proposed is fixed: $ autopkgtest --apt-pocket=proposed initramfs-tools -- lxd autopkgtest/ubuntu/jammy/amd64 2>&1 | tee good.log $ grep 'Setting up linux-firmware' good.log Setting up linux-firmware (20220329.git681281e4-0ubuntu3.38) ... Setting up linux-firmware (20220329.git681281e4-0ubuntu3.38) ... $ tail good.log autopkgtest [16:38:23]: @@@@@@@@@@@@@@@@@@@@ summary shellcheck PASS (superficial) unit-tests PASS qemu-klibc PASS qemu-busybox PASS qemu-ata-only PASS qemu-virtio-only PASS qemu-separate-usr PASS qemu-panic-shell PASS qemu-net PASS ** Tags added: verification-done-jammy -- 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/2085503 Title: initramfs-tools/0.140ubuntu13.4 ADT test failure with linux/5.15.0-125.135 Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] initramfs-tools fails if no firmware is installed in the initrd. [Test Case] Run autopkgtest or any other test that uses initramfs-tools to create an inird that doesn't contain any firmware. [Where Problems Could Occur] Creating an initrd might fail or its content might be incorrect. [Original Description] This is a scripted bug report about ADT failures while running initramfs-tools tests for linux/5.15.0-125.135 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20241018_134359_e7fcd@/log.gz Multiple sub-tests fail because of missing firmware (directory): 813s amd64-ata-only FAIL stderr: find: ‘/tmp/autopkgtest.uid9aC/autopkgtest_tmp/mkinitramfs_mtEnT4/lib/firmware’: No such file or directory 813s amd64-virtio-only FAIL stderr: find: ‘/tmp/autopkgtest.uid9aC/autopkgtest_tmp/mkinitramfs_nYMKag/lib/firmware’: No such file or directory 813s amd64-separate-usr FAIL stderr: find: ‘/tmp/autopkgtest.uid9aC/autopkgtest_tmp/mkinitramfs_uRFQTf/lib/firmware’: No such file or directory 813s amd64-panic-shell FAIL stderr: find: ‘/tmp/autopkgtest.uid9aC/autopkgtest_tmp/mkinitramfs_yfrEDD/lib/firmware’: No such file or directory 813s amd64-net FAIL stderr: find: ‘/tmp/autopkgtest.uid9aC/autopkgtest_tmp/mkinitramfs_zKpc2Z/lib/firmware’: No such file or directory This message happens early in the test and when booting the 2nd level VM it is missing modules. I tried to re-create locally and could not see this happening. Also this does not sound like a kernel issue and there are no kernel error messages visible either. Other than in the boot and that would be a result of previous problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2085503/+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
