Re: iwlwifi WARNING in dmesg

From: Bjoern A. Zeeb <bz_at_freebsd.org>
Date: Tue, 10 Jun 2025 08:43:37 UTC
On Mon, 9 Jun 2025, Chuck Tuffli wrote:

> On Mon, Jun 9, 2025 at 4:28 PM Bjoern A. Zeeb <bz@freebsd.org> wrote:
>
>> 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 finding that resuming the laptop hangs unless the WiFi is disabled
> before suspending. After resuming, running restart fixes things for me.

Thank you.  Makes sense.  Another way to do this automatically is documented here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263632#c27


>>> 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 ...
>
>
> iwlwifi0@pci0:170:0:0: class=0x028000 rev=0x1a hdr=0x00 vendor=0x8086
> device=0x2725 subvendor=0x8086 subdevice=0x0024
>    vendor         = ‘Intel Corporation’
>    device          = ‘Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak]’
>    class             = network
>
>
>>> 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
>>
>

-- 
Bjoern A. Zeeb                                                     r15:7