linux-kernel - Re: wlwifi AX201: WARN_ON in iwl_mvm_mld_mac_ctxt_cmd_common repeated UMAC FW crashes on 6.16-rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAL=B37mqrHOzEQzPX3=6S5XaUZexYRUXNBgUuGsiX6+4iHWO8g@mail.gmail.com>
Date: Sun, 22 Jun 2025 21:45:14 +0200
From: Damian Tometzki <damian@...cv-rocks.de>
To: miriam.rachel.korenblit@...el.com
Cc: linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: wlwifi AX201: WARN_ON in iwl_mvm_mld_mac_ctxt_cmd_common repeated
 UMAC FW crashes on 6.16-rc2

On Sun, Jun 22, 2025 at 6:30 PM Damian Tometzki <damian@...cv-rocks.de> wrote:
>
> Hi Miri,
> Hi all,
>
> with v6.16-rc2 I consistently hit a Wi-Fi firmware crash on a
> Lenovo ThinkPad X1 Carbon Gen 9.
>
> Hardware / FW
> -------------
>  * NIC  : Intel Wi-Fi 6 AX201 160 MHz (PCI ID a0f0:0070, rev 0x351)
>  * FW   : 77.864baa2e.0 QuZ-a0-hr-b0-77.ucode (auto-loaded)
>  * BIOS : N32ET96W (1.72)
>  * Platform: 20XWCTO1WW
>
> Kernel: 6.16.0-rc2 #440 PREEMPT(lazy)
>
> Symptoms
> --------
> Immediately after NetworkManager (or plain `ip link set wlp0s20f3 up`)
> the driver warns:
>
>     WARNING at drivers/net/wireless/intel/iwlwifi/mvm/mld-mac.c:37
>     iwl_mvm_mld_mac_ctxt_cmd_common+0x175/0x1d0
>
> The firmware then aborts:
>
>     FW error in SYNC CMD MAC_CONFIG_CMD
>     NMI_INTERRUPT_UMAC_FATAL
>     ADVANCED_SYSASSERT 0x20103126
>     Microcode SW error detected. Restarting 0x0.
>
> The cycle repeats every few seconds; the interface never becomes usable.
> Full dmesg attached.
>
> --
> VG
> Demian Tometzki

Hi together,

I identified commit 83f3ac2848b46e3e5af5d06b5f176c as the cause of the issue.
After reverting it, the system is working again.

Best regards
Damian