Meteor Lake PCH WiFi broken on Linux (Not valid error log pointer 0x0024B5C0 for RT uCode)

[OlegAn]

openSUSE Tumbleweed, updating kernel-firmware-iwlwifi to 20240618 breaks WiFi.

[ 7.488052] [ C12] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
[ 7.488120] [ T1010] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f
[ 7.488143] [ T1010] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 7.488150] [ T1010] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x80
[ 7.488159] [ T1010] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[ 7.488799] [ T511] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[ 7.578017] [ T1010] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP, with index: 0
[ 7.578273] [ T811] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[ 7.578333] [ T811] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 7.578339] [ T811] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 6
[ 7.578345] [ T811] iwlwifi 0000:00:14.3: Loaded firmware version: 89.202a2f7b.0 ma-b0-gf-a0-89.ucode
[ 7.578350] [ T811] iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL

(Full error in attached file)

Rolling back kernel-firmware-iwlwifi to 20240519 helps.

Hardware:

0000:00:14.3 Network controller: Intel Corporation Meteor Lake PCH CNVi WiFi (rev 20)

Software:

Operating System: openSUSE Tumbleweed-Slowroll 20240605
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.5-1-default (64-bit)
Graphics Platform: Wayland
Processors: 14 × Intel® Core™ Ultra 7 155U
Memory: 30.9 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ASUS Zenbook S 13 UX5304MA_UX5304MA
System Version: 1.0

[Mike_Intel]

Hello OlegAn,

Thank you for posting in Intel community Forum.

For us to further check this, please help provide the following details:

1. What is the model of the wireless controller?
2. What do you mean broken?
3. Did you upgrade the wireless controller or you are using the embedded card?
4. What is the Operating System of this unit when you purchased it?

If you have questions, please let us know. Thank you.

Best regards,

Michael L.

Intel Customer Support Technician

[Mike_Intel]

Hello OlegAn,

I hope this message finds you well. 

Were you able to check the previous post?

Please let us know if you still need assistance.

Best regards,

Michael L.

Intel Customer Support Technician

[OlegAn]

https://bugzilla.suse.com/show_bug.cgi?id=1226544

[Mike_Intel]

Hello OlegAn,

Thank you for the quick reply.

As per the link that you provided, issue is fixed. Can you tell us if you still need assistance?

If you have questions, please let us know. Thank you.

Best regards,

Michael L.

Intel Customer Support Technician

[OlegAn]

Fixed in kernel 6.9.7

[Aaron77]

Hi,

Sorry for jumping on this thread but I am seeing the same error "Not valid error log pointer 0x0024B5C0 for RT uCode" in Kernel 6.14.0. 

[Fri May 23 09:31:08 2025] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
[Fri May 23 09:31:09 2025] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
[Fri May 23 09:36:29 2025] warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[Fri May 23 16:02:39 2025] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
[Fri May 23 17:09:13 2025] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
[Fri May 23 18:48:25 2025] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
[Fri May 23 19:40:03 2025] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode

I've attached a dmesg log file for more detailed info and some system info is shown below. Please let me know if you need anything else.

I seem to be on the latest available firmware module: 

$ sudo dmesg | grep iwlwifi | grep 'firmware version'
[ 14.888210] iwlwifi 0000:00:14.3: loaded firmware version 89.4d42c933.0 ma-b0-gf-a0-89.ucode op_mode iwlmvm

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/

Thanks,

Aaron

# System Details Report
---

## Report details
- **Date generated:** 2025-05-23 10:36:10

## Hardware Information:
- **Hardware Model:** Lenovo ThinkPad T14s Gen 5
- **Memory:** 64.0 GiB
- **Processor:** Intel® Core™ Ultra 7 165U × 14
- **Graphics:** Intel® Graphics (MTL)
- **Disk Capacity:** 2TB

## Software Information:
- **Firmware Version:** N46ET21W (1.11 )
- **OS Name:** Ubuntu 25.04
- **OS Build:** (null)
- **OS Type:** 64-bit
- **GNOME Version:** 48
- **Windowing System:** Wayland
- **Kernel Version:** Linux 6.14.0-15-generic

OS: Ubuntu 25.04 x86_64

$ uname -a
Linux t14s 6.14.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Sun Apr 6 15:05:05 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

$ lspci -nnk | grep -A3 Network
00:08.0 System peripheral [0880]: Intel Corporation Meteor Lake-P Gaussian & Neural-Network Accelerator [8086:7e4c] (rev 20)
Subsystem: Lenovo Device [17aa:2329]
00:0a.0 Signal processing controller [1180]: Intel Corporation Meteor Lake-P Platform Monitoring Technology [8086:7d0d] (rev 01)
Subsystem: Lenovo Device [17aa:2329]
--
00:14.3 Network controller [0280]: Intel Corporation Meteor Lake PCH CNVi WiFi [8086:7e40] (rev 20)
Subsystem: Intel Corporation Device [8086:0090]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

[lgo]

Hello Aaron,

Did you manage to solve your issue?

I'm having the same problem "Not valid error log pointer 0x0024B5C0 for RT uCode" in Kernel 6.14.0. 

[Aaron77]

The problem still exists. There's a bug in the microcode and Intel needs to fix this.

[zlrs]

I seem to be having the same/similar problem as Aaron and lgo: "iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode". 

Symptom for me seems to be is that my wifi slows right down around 10-100kb/s (or stops working completely). 

# System Details:

## Hardware Information:
- **Hardware Model:** Lenovo ThinkPad P14s Gen 5
- **Memory:** 32.0 GiB
- **Processor:** Intel Ultra 7 155H
- **Disk Capacity:** 1TB

## Software Information:
- **OS Name:** Ubuntu 24.04.3 LTS x86_64 
- **GNOME Version:** 46
- **Windowing System:** Wayland
- **Kernel Version:** 6.14.0-33-generic

DMESG logs:

[ 4.762643] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 4.780753] iwlwifi 0000:00:14.3: Detected crf-id 0x400410, cnv-id 0x1080800 wfpm id 0x80005b20
[ 4.780765] iwlwifi 0000:00:14.3: PCI dev 7e40/0090, rev=0x441, rfid=0x2010d000
[ 4.780767] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz
[ 4.794479] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.3.94
[ 4.795104] iwlwifi 0000:00:14.3: loaded firmware version 89.1a492d28.0 ma-b0-gf-a0-89.ucode op_mode iwlmvm
[ 5.337684] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
[ 5.337712] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f
[ 5.337728] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 5.337734] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: [redacted]
[ 5.337741] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[ 5.337804] iwlwifi 0000:00:14.3: Detected RF GF, rfid=0x2010d000
[ 5.338567] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[ 5.339671] iwlwifi 0000:00:14.3: loaded PNVM version 581d4936
[ 5.420106] iwlwifi 0000:00:14.3: base HW address: [redacted]
[ 5.455908] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
[ 6.881805] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
[ 6.881846] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f
[ 6.881860] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 6.881876] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: [redacted]
[ 6.881884] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[ 6.882680] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[ 6.967813] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP, with index: 1

[Jerkwad_Robot]

Created a login just to add that I have the same issue. 

Currently running Chimera Linux on Kernel 6.17.10.

I get the error message: Not valid error log pointer 0x0024B5C0 for RT uCode.

It's peppered throughout the log, and it sometimes causes network manager to crash and force a full reboot to fix. 

I found this bugzilla, which they added (harmless print) to the bug. You can read through it to see why, but it's certainly not harmless in my case. Anyway, a "fix" was submitted for 6.19, but I dunno what it's going to actually do. Resolve or hide the messages?!?