Hello You-Sheng, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.26 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2048853 Title: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Triaged Bug description: [SRU Justification] [Impact] Within stress reboot tests, iwlwifi may fail to load firmware, triggers retries, and finally makes wifi operative. iwlwifi 0000:05:00.0: Loaded firmware version: 83.d24e06ed.0 gl-c0-fm-c0-83.ucode iwlwifi 0000:05:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL iwlwifi 0000:05:00.0: 0x000002F0 | trm_hw_status0 iwlwifi 0000:05:00.0: 0x00000000 | trm_hw_status1 iwlwifi 0000:05:00.0: 0x002C27F2 | branchlink2 iwlwifi 0000:05:00.0: 0x002B79AE | interruptlink1 ...... iwlwifi 0000:05:00.0: UMAC CURRENT PC: 0x8026934e iwlwifi 0000:05:00.0: LMAC1 CURRENT PC: 0xd0 iwlwifi 0000:05:00.0: LMAC2 CURRENT PC: 0xd0 iwlwifi 0000:05:00.0: UMAC CURRENT PC 1: 0x8026934c iwlwifi 0000:05:00.0: TCM1 CURRENT PC: 0xd0 iwlwifi 0000:05:00.0: RCM1 CURRENT PC: 0xd0 iwlwifi 0000:05:00.0: RCM2 CURRENT PC: 0xd0 iwlwifi 0000:05:00.0: Function Scratch status: iwlwifi 0000:05:00.0: 0x01010101 | Func Scratch iwlwifi 0000:05:00.0: Failed to start RT ucode: -110 iwlwifi 0000:05:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fix] Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for core80-165 release"). While the iwlwifi firmware updates come with a sequential manner, it pulls a few more: * 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic * a07fd0b96 ("iwlwifi: add new FWs from core83-55 release") * f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release") These contain firmware blob for ucore 84/86, and are not used by kernels < v6.7. [Test Case] Use checkbox reboot stress test case to observe iwlwifi dmesg logs: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] Opaque firmware update. No known issue found yet after the update. [Other Info] This affects series with kernels that load iwlwifi ucode 83 firmware, namely Noble, Mantic, and for oem-6.5, Jammy. ========== original bug report ========== Within stress reboot tests, iwlwifi may fail to load firmware and triggers retry, and finally makes wifi operative. Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: Loaded firmware version: 83.d24e06ed.0 gl-c0-fm-c0-83.ucode Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: 0x000002F0 | trm_hw_status0 Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: 0x00000000 | trm_hw_status1 Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: 0x002C27F2 | branchlink2 Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: 0x002B79AE | interruptlink1 ...... Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: UMAC CURRENT PC: 0x8026934e Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: LMAC1 CURRENT PC: 0xd0 Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: LMAC2 CURRENT PC: 0xd0 Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: UMAC CURRENT PC 1: 0x8026934c Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: TCM1 CURRENT PC: 0xd0 Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: RCM1 CURRENT PC: 0xd0 Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: RCM2 CURRENT PC: 0xd0 Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: Function Scratch status: Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: 0x01010101 | Func Scratch Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: Failed to start RT ucode: -110 Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). Test steps: $ checkbox-cli run com.canonical.certification::stress/reboot Proposed fix: * https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux- firmware.git/commit/?id=318c64abfb33c4211b002f5e5b4ff25cd19f712b To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2048853/+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