Date: Tue, 11 Jan 2022 14:30:02 -0600 From: Kyle Evans <kevans@freebsd.org> To: "Bjoern A. Zeeb" <bz@freebsd.org> Cc: wireless@freebsd.org Subject: Re: iwlwifi auth->scan error/panic Message-ID: <CACNAnaEuCZ0ECmsNoq5NEX9o-%2BwaAK8y3cVXTcj9KWttv=Ct-Q@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.2112312357170.68830@ai.fobar.qr> References: <alpine.BSF.2.00.2112312357170.68830@ai.fobar.qr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 31, 2021 at 6:03 PM Bjoern A. Zeeb <bz@freebsd.org> wrote:
>
> Hi,
>
> I got two reports in the last three days from people who have traces
> showing the driver attaching, scanning and starting to authenticate/associate
> and (in one case) apparently having succeeded but then bounce back to
> scanning.
>
> The two cases are different but essentially mean net80211 or
> iwlwifi/firmware didn't see some frames it expected (or there is also
> a possibility of a logic bug between mac80211/iwlwifi still; I had
> cherry-picked some fixes for that already).
>
> Long story short: in the follow-up of the auth_to_scan change people
> are seeing firmware crashes or in a follow-up even a panic.
>
> I'll be looking into those the first days in the New Year.
> If you have such a case please make sure to turn on wlandebug with
> "+auth +scan +state +node" at least (see wiki for how to do this in
> rc.conf [1]) and drop me a private email with the log.
>
I'm seeing something that goes a little like (transcribed from a
picture, swap partition too small):
wlan0: no link ...
WARNING mva_sta->dup_data == ((void *0)) failed at
/usr/src/sys/contrib/dev/iwlwifi/mvm/rxmq.c:509
wlan0: ieee80211_new_state_locked: pending ASSOC -> RUN transition lost
wlan0: link state changed to UP
wlan0: link state changed to DOWN
WARNING mva_sta->dup_data == ((void *0)) failed at
/usr/src/sys/contrib/dev/iwlwifi/mvm/rxmq.c:509 (repeated at least a
dozen times)
panic: lkpi_sta_assoc_to_auth: lsta ... state not AUTH: 0
...
Related? This is with main at bec766282f242aab3a4bfba402ea74cb0ccf96fb
("LinuxKPi: 802.11 fix locking ..."). I'm seeing this on maybe 70-80%
of boots now, while the last snapshot before it entered the tree was
relatively-ish stable.
Thanks,
Kyle Evans
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaEuCZ0ECmsNoq5NEX9o-%2BwaAK8y3cVXTcj9KWttv=Ct-Q>