This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.9

---------------
linux-firmware (20230919.git3672ccab-0ubuntu2.9) mantic; urgency=medium

  * Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP: 
#2049220)
    - linux-firmware: update firmware for MT7922 WiFi device
    - linux-firmware: update firmware for mediatek bluetooth chip (MT7922)

linux-firmware (20230919.git3672ccab-0ubuntu2.8) mantic; urgency=medium

  * DP connection swap to break eDP behavior on AMD 7735U (LP: #2049758)
    - SAUCE: Update DCN312 DMCUB firmware

linux-firmware (20230919.git3672ccab-0ubuntu2.7) mantic; urgency=medium

  * Miscellaneous Ubuntu changes
    - [Packaging] scripts: Fix shellcheck warnings
    - [Workflow] Add initial gitea workflow file
    - SAUCE: [Workflow] Disable markdownlint pre-commit hook
    - SAUCE: [Workflow] check_whence.py: Update list of known files
    - [Packaging] scripts/generate-changelog: Fix array initialization
    - [Packaging] control: Add XSBC-Original-Maintainer field
    - [Packaging] scripts/install-firmware: Fix installation of license files
  * AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress 
loading (LP: #2051636)
    - amdgpu: update PSP 13.0.4 firmware from 5.7 branch
    - amdgpu: update GC 11.0.1 firmware from 5.7 branch
    - amdgpu: update GC 11.0.4 firmware from 5.7 branch
    - amdgpu: update PSP 13.0.11 firmware from 5.7 branch
    - amdgpu: update GC 11.0.1 firmware
    - amdgpu: update PSP 13.0.4 firmware
    - amdgpu: update VCN 4.0.2 firmware
    - amdgpu: update GC 11.0.4 firmware
    - amdgpu: update PSP 13.0.11 firmware
  * Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP: 
#2049220)
    - linux-firmware: update firmware for MT7921 WiFi device
    - linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
  * WCN6856 Wi-FI Unavailable and no function during suspend stress (LP: 
#2048977)
    - ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37

linux-firmware (20230919.git3672ccab-0ubuntu2.6) mantic; urgency=medium

  * occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start 
RT ucode: -110 (LP: #2048853)
    - iwlwifi: add new FWs from core83-55 release
    - iwlwifi: fix for the new FWs from core83-55 release
    - iwlwifi: update gl FW for core80-165 release
  * WCN6856 Wi-FI Unavailable and no function during suspend stress (LP: 
#2048977)
    - ath11k: WCN6855 hw2.0: update board-2.bin
    - ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36

 -- Juerg Haefliger <juerg.haefli...@canonical.com>  Wed, 21 Feb 2024
10:41:18 +0100

** Changed in: linux-firmware (Ubuntu Mantic)
       Status: Fix Committed => Fix Released

-- 
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:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

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

Reply via email to