Re: iwlwifi WARNING in dmesg

On Mon, 9 Jun 2025, Chuck Tuffli wrote:

Hi,

wireless@ is a better place for this.

> I'm running a recent-ish -CURRENT (15.0-CURRENT
> main-n277741-898a886b4504) on a Framework 13 (Gen 11) and am seeing
> the following in dmesg:
>
> Jun  9 15:23:29 chuck-laptop dhclient[61298]: New IP Address (wlan0):
> 192.168.5.253
> Jun  9 15:23:29 chuck-laptop dhclient[61302]: New Subnet Mask (wlan0):
> 255.255.255.0
> Jun  9 15:23:29 chuck-laptop dhclient[61306]: New Broadcast Address
> (wlan0): 192.168.5.255
> Jun  9 15:23:29 chuck-laptop dhclient[61310]: New Routers (wlan0): 192.168.5.1
> Jun  9 15:23:29 chuck-laptop kernel: wlan0: link state changed to UP
> Jun  9 15:23:29 chuck-laptop kernel: WARNING
> ((__typeof(*mvm->baid_map[baid]) *)({ __typeof(mvm->baid_map[baid])
> __var = ({ __asm__ __volatile__("": : :"memory"); (*(const volatile
> __typeof(mvm->baid_map[baid]) *)&(mvm->baid_map[baid])); }); __asm__
> __volatile__("": : :"memory"); __var; })) failed at
> /home/pkgbuild/worktrees/main/sys/contrib/dev/iwlwifi/mvm/sta.c:3004
> Jun  9 15:23:34 chuck-laptop syslogd: last message repeated 1 times
> Jun  9 15:30:24 chuck-laptop syslogd: last message repeated 1 times
>
> This occurred after running:
>
> # service netif restart wlan0

Why did you have to run restart in first place?

I am trying to understand the state you are coming from to figure out
what might have triggered this.


> I'm assuming "this is fine" as it is labeled a warning, but also
> figured someone might be interested. As for the hardware, lspci shows
>
> aa:00.0 Network controller: Intel Corporation Wi-Fi 6E(802.11ax)
> AX210/AX1675* 2x2 [Typhoon Peak] (rev 1a)

And what does pciconf -lv iwlwifi0 show?  Not that it matters much in
this case but ...


> and the relevant drivers (I think) are:
>
> $ kldstat | grep if
> 14    1 0xffffffff84358000    b1340 if_iwlwifi.ko
> 15    1 0xffffffff8440a000    171b0 if_iwx.ko
>
>

-- 
Bjoern A. Zeeb                                                     r15:7