Bugzilla – Bug 1226717
kernel-firmare-iwlwifi 20240618 breaks wifi (Not valid error log pointer 0x0024B5C0 for RT uCode)
Last modified: 2024-06-21 12:40:13 UTC
Created attachment 875633 [details] dmesg output openSUSE Tumbleweed-Slowroll, 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 Post on Intel's forum https://community.intel.com/t5/Wireless/Meteor-Lake-PCH-WiFi-broken-on-Linux-Not-valid-error-log-pointer/m-p/1608808#M54935
Duplicate of bug 1226544
Duplicate of bug 1226544 *** This bug has been marked as a duplicate of bug 1226544 ***