[Bug 284421] iwlwifi: kernel panic: lkpi_sta_scan_to_auth:1346: mo_sta_state(NONE) failed: -5 [Intel 8260]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284421

--- Comment #7 from Shirkdog <mshirk@daemon-security.com> ---
I believe reporting this bug has caused the issue not to happen as much...and
this is probably due to interacting with the laptop and not letting it sit idle
for a long time. I will report back on this bug when I can provide answers to
your questions. Specifically when it happens again I will tell you about this.

>>>If instead of doing a netif restart wlan0, can you simply try:
>>>        ifconfig wlan0 down
>>>        ifconfig wlan0 up
>>>        ifconfig wlan0 scan
>>>and see if that helps to get you associated again without the panic when this happens?

I will load up the latest FreeBSD 15-CURRENT build, setting debug on
wpa_supplicant over the weekend when I am not using this laptop to see if I can
get the panic condition again. 


Now some responses to your other comments:

>>>Right, and why is that?  What happened before?

>>>I see beacon misses in the log below.

>>>Crowded spectrum?  Low signal?  ..?

Crowded spectrum is interesting, as this has happened with different wireless
routers (Netgear, TP_Link) at two different locations where there is definite
overlap of wireless signals. For both locations, I had the laptop very close to
the router. The Intel driver works negotiates on the 2.4GHz band with 802.11g.
Of interest, the modulation does appear to change over time, from OFDM to DS, 

>>>But I didn't manage a follow-up panic.

>>>You mentioned that you had that problem with iwm(4) already?
>>>Did it just drop or did you get firmware crashes there as well?

>>>I would really be interested on how this showed on iwm(8) given this seems to be related to older chipsets.

The iwm driver acted the same way you have found, after a period of time, I
would come back and find "no carrier" on "wlan0", but I would simply refresh
the interface and get an IP address. I never got a panic with the iwm driver,
this is something I have only seen with the iwlwifi driver. The laptop is
getting old, but since intel wireless is pretty common, I wanted to raise this
issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.