occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
New
|
Undecided
|
Unassigned | ||
linux-firmware (Ubuntu) |
Fix Released
|
High
|
You-Sheng Yang | ||
Jammy |
Fix Released
|
High
|
You-Sheng Yang | ||
Mantic |
Fix Released
|
High
|
You-Sheng Yang | ||
Noble |
Fix Released
|
High
|
You-Sheng Yang |
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-
iwlwifi 0000:05:00.0: 0x00000071 | NMI_INTERRUPT_
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.
[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-
Oct 12 00:16:21 32090 kernel: iwlwifi 0000:05:00.0: 0x00000071 | NMI_INTERRUPT_
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.
Proposed fix:
tags: | added: oem-priority originate-from-2039134 somerville |
description: | updated |
Changed in linux-firmware (Ubuntu Jammy): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → You-Sheng Yang (vicamo) |
Changed in linux-firmware (Ubuntu Mantic): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → You-Sheng Yang (vicamo) |
Changed in linux-firmware (Ubuntu Noble): | |
assignee: | nobody → You-Sheng Yang (vicamo) |
importance: | Undecided → High |
status: | New → In Progress |
description: | updated |
Changed in linux-firmware (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux-firmware (Ubuntu Mantic): | |
status: | In Progress → Fix Committed |
Commit 318c64abf touches PNVM as well:
$ git log --oneline --stat 318c64abf fw-2023- 12-21, korg-iwlwifi/ for-upstream) iwlwifi: update gl FW for core80-165 release gl-c0-fm- c0-83.ucode | Bin 1799504 -> 1797996 bytes gl-c0-fm- c0.pnvm | Bin 226668 -> 246228 bytes
318c64abf (tag: iwlwifi-
WHENCE | 2 +-
iwlwifi-
iwlwifi-
3 files changed, 1 insertion(+), 1 deletion(-)
Which then pulls two more commits due the the modification chain of the PNVM file:
$ git log --oneline --stat f27dec616 fw-2023- 11-16-fixed) iwlwifi: fix for the new FWs from core83-55 release gl-c0-fm- c0-86.ucode | Bin 1840116 -> 1840116 bytes gl-c0-fm- c0.pnvm | Bin 226668 -> 226668 bytes ma-b0-gf- a0-86.ucode | Bin 1695788 -> 1695788 bytes ma-b0-gf- a0.pnvm | Bin 55092 -> 55092 bytes ma-b0-gf4- a0-86.ucode | Bin 1670940 -> 1670940 bytes ma-b0-gf4- a0.pnvm | Bin 27820 -> 27820 bytes ma-b0-hr- b0-86.ucode | Bin 1520636 -> 1520636 bytes so-a0-gf- a0-86.ucode | Bin 1679788 -> 1679788 bytes so-a0-gf- a0.pnvm | Bin 55172 -> 55172 bytes so-a0-gf4- a0-86.ucode | Bin 1653836 -> 1653836 bytes so-a0-gf4- a0.pnvm | Bin 27860 -> 27860 bytes so-a0-hr- b0-86.ucode | Bin 1507388 -> 1507388 bytes ty-a0-gf- a0-86.ucode | Bin 1632464 -> 1632464 bytes ty-a0-gf- a0.pnvm | Bin 55020 -> 55020 bytes
f27dec616 (tag: iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
14 files changed, 0 insertions(+), 0 deletions(-)
$ git log --oneline --stat a07fd0b96 fw-2023- 11-15) iwlwifi: add new FWs from core83-55 release +++++++ +++++++ +++ gl-c0-fm- c0-86.ucode | Bin 0 -> 1840116 bytes gl-c0-fm- c0.pnvm | Bin 246228 -> 226668 bytes ma-b0-gf- a0-86.ucode | Bin 0 -> 1695788 bytes ma-b0-gf- a0.pnvm | Bin 55500 -> 55092 bytes ma-b0-gf4- a0-86.ucode | Bin 0 -> 1670940 bytes ma-b0-gf4- a0.pnvm | Bin 28024 -> 27820 bytes ma-b0-hr- b0-86.ucode | Bin 0 -> 1520636 bytes so-a0-gf- a0-86.ucode | Bin 0 -> 1679788 bytes so-a0-gf- a0.pnvm | Bin 55580 -> 55172 bytes so-a0-gf4- a0-86.ucode | Bin 0 -> 1653836 bytes so-a0-gf4- a0.pnvm | Bin 28064 -> 27860 bytes so-a0-hr- b0-86.ucode | Bin 0 -> 1507388 bytes ty-a0-gf- a0-86.ucode | Bin 0 -> 1632464 bytes ty-a0-gf- a0.pnvm | Bin 55484 -> 55020 bytes
a07fd0b96 (tag: iwlwifi-
WHENCE | 24 +++++++
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
iwlwifi-
15 files changed, 24 insertions(+)
While the two commits are for ucode 86 releases that is currently not supported by all available kernels in Jammy, there is not hard/effect that may be introduced by pulling both of them.