Commit 318c64abf touches PNVM as well:

$ git log --oneline --stat 318c64abf
318c64abf (tag: iwlwifi-fw-2023-12-21, korg-iwlwifi/for-upstream) iwlwifi: 
update gl FW for core80-165 release
 WHENCE                       |   2 +-
 iwlwifi-gl-c0-fm-c0-83.ucode | Bin 1799504 -> 1797996 bytes
 iwlwifi-gl-c0-fm-c0.pnvm     | Bin 226668 -> 246228 bytes
 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
f27dec616 (tag: iwlwifi-fw-2023-11-16-fixed) iwlwifi: fix for the new FWs from 
core83-55 release
 iwlwifi-gl-c0-fm-c0-86.ucode  | Bin 1840116 -> 1840116 bytes
 iwlwifi-gl-c0-fm-c0.pnvm      | Bin 226668 -> 226668 bytes
 iwlwifi-ma-b0-gf-a0-86.ucode  | Bin 1695788 -> 1695788 bytes
 iwlwifi-ma-b0-gf-a0.pnvm      | Bin 55092 -> 55092 bytes
 iwlwifi-ma-b0-gf4-a0-86.ucode | Bin 1670940 -> 1670940 bytes
 iwlwifi-ma-b0-gf4-a0.pnvm     | Bin 27820 -> 27820 bytes
 iwlwifi-ma-b0-hr-b0-86.ucode  | Bin 1520636 -> 1520636 bytes
 iwlwifi-so-a0-gf-a0-86.ucode  | Bin 1679788 -> 1679788 bytes
 iwlwifi-so-a0-gf-a0.pnvm      | Bin 55172 -> 55172 bytes
 iwlwifi-so-a0-gf4-a0-86.ucode | Bin 1653836 -> 1653836 bytes
 iwlwifi-so-a0-gf4-a0.pnvm     | Bin 27860 -> 27860 bytes
 iwlwifi-so-a0-hr-b0-86.ucode  | Bin 1507388 -> 1507388 bytes
 iwlwifi-ty-a0-gf-a0-86.ucode  | Bin 1632464 -> 1632464 bytes
 iwlwifi-ty-a0-gf-a0.pnvm      | Bin 55020 -> 55020 bytes
 14 files changed, 0 insertions(+), 0 deletions(-)

$ git log --oneline --stat a07fd0b96
a07fd0b96 (tag: iwlwifi-fw-2023-11-15) iwlwifi: add new FWs from core83-55 
release
 WHENCE                        |  24 ++++++++++++++++++++++++
 iwlwifi-gl-c0-fm-c0-86.ucode  | Bin 0 -> 1840116 bytes
 iwlwifi-gl-c0-fm-c0.pnvm      | Bin 246228 -> 226668 bytes
 iwlwifi-ma-b0-gf-a0-86.ucode  | Bin 0 -> 1695788 bytes
 iwlwifi-ma-b0-gf-a0.pnvm      | Bin 55500 -> 55092 bytes
 iwlwifi-ma-b0-gf4-a0-86.ucode | Bin 0 -> 1670940 bytes
 iwlwifi-ma-b0-gf4-a0.pnvm     | Bin 28024 -> 27820 bytes
 iwlwifi-ma-b0-hr-b0-86.ucode  | Bin 0 -> 1520636 bytes
 iwlwifi-so-a0-gf-a0-86.ucode  | Bin 0 -> 1679788 bytes
 iwlwifi-so-a0-gf-a0.pnvm      | Bin 55580 -> 55172 bytes
 iwlwifi-so-a0-gf4-a0-86.ucode | Bin 0 -> 1653836 bytes
 iwlwifi-so-a0-gf4-a0.pnvm     | Bin 28064 -> 27860 bytes
 iwlwifi-so-a0-hr-b0-86.ucode  | Bin 0 -> 1507388 bytes
 iwlwifi-ty-a0-gf-a0-86.ucode  | Bin 0 -> 1632464 bytes
 iwlwifi-ty-a0-gf-a0.pnvm      | Bin 55484 -> 55020 bytes
 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.

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

Bug description:
  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