Re: New iwlwifi firmware for testing in main

On Mon, 8 Aug 2022 13:29:25 +0200
"J.R. Oldroyd" <fbsd@opal.com> wrote:

> On Mon, 8 Aug 2022 02:46:25 +0000 (UTC) "Bjoern A. Zeeb" <bz@FreeBSD.org> wrote:
> >
> > 
> > Thanks for confirming this!
> > 
> 
> Björn,
> 
> Back on 7/13 at 09:33 UTC, I sent you an email also showing a panic.
> It may be similar as it also involves lkpi_sta_auth_to_scan() and then
> lkpi_lsta_remove().
> 
> In my case, it was triggered by doing:
> 	ifconfig wlan0 down up
> on an already-associated interface with an address from DHCP.
> 
> This is on the 8265.
> 
> Here's the backtrace again...
> 
> 	-jr
> 
> 
> (kgdb) bt
> ^M#0  __curthread () at /usr/src-13stb/sys/amd64/include/pcpu_aux.h:55
> #1  dump_savectx () at ../../../kern/kern_shutdown.c:394
> #2  0xffffffff80c245e8 in dumpsys (di=0x0) at /usr/src-13stb/sys/x86/include/dump.h:87
> #3  doadump (textdump=<optimized out>) at ../../../kern/kern_shutdown.c:423
> #4  kern_reboot (howto=260) at ../../../kern/kern_shutdown.c:497
> #5  0xffffffff80c24a4e in vpanic (fmt=<optimized out>, ap=ap@entry=0xfffffe00c701db50) at ../../../kern/kern_shutdown.c:930
> #6  0xffffffff80c24883 in panic (fmt=<unavailable>) at ../../../kern/kern_shutdown.c:854
> #7  0xffffffff810ba005 in trap_fatal (frame=0xfffffe00c701dc40, eva=0) at ../../../amd64/amd64/trap.c:940
> #8  0xffffffff810ba05f in trap_pfault (frame=0xfffffe00c701dc40, usermode=false, signo=<optimized out>, ucode=<optimized out>) at ../../../amd64/amd64/trap.c:759
> #9  <signal handler called>
> #10 0xffffffff80e60d3c in lkpi_lsta_remove (lsta=0xfffff80061658000, lsta@entry=0xfffffe00cca06000, lvif=lvif@entry=0xfffffe00cca06000) at ../../../compat/linuxkpi/common/src/linux_80211.c:177
> #11 0xffffffff80e5c674 in lkpi_sta_auth_to_scan (vap=0xfffffe00cca06010, nstate=<optimized out>, arg=<optimized out>) at ../../../compat/linuxkpi/common/src/linux_80211.c:1128
> #12 0xffffffff80e61938 in lkpi_iv_newstate (vap=0xfffffe00cca06010, nstate=IEEE80211_S_SCAN, arg=<optimized out>) at ../../../compat/linuxkpi/common/src/linux_80211.c:1983
> #13 0xffffffff80da733a in ieee80211_newstate_cb (xvap=0xfffffe00cca06010, npending=<optimized out>) at ../../../net80211/ieee80211_proto.c:2555
> #14 0xffffffff80c866a1 in taskqueue_run_locked (queue=queue@entry=0xfffff80009cf3200) at ../../../kern/subr_taskqueue.c:514
> #15 0xffffffff80c879c2 in taskqueue_thread_loop (arg=<optimized out>, arg@entry=0xfffffe00c8eaa110) at ../../../kern/subr_taskqueue.c:826
> #16 0xffffffff80be0d1e in fork_exit (callout=0xffffffff80c87900 <taskqueue_thread_loop>, arg=0xfffffe00c8eaa110, frame=0xfffffe00c701df40) at ../../../kern/kern_fork.c:1105
> #17 <signal handler called>
> #18 0x0276000000000000 in ?? ()

I've bitten similar, but maybe not the same crash.
Happenes when:

 *Successfully associated on boot, switch to wired (em0) connection,
  then switch again to iwlwifi. Not always, so maybe racy.

 *Wired and wireless connection is on the same network, using AP.


On stable/13 cherry-picking all (I think) 802.11 related commits by bz@
silently reboots.
On main at git 038405f32f71ad8ba0280ae066417f986ede79db entered kdb,
showing trap12. So I could take photos.

Please see attached (typed up reading photo) for detail.

Note that main at git 258828d03b9f8414043c112fab97e9e9730560dc showed
the same behaviour.  The addresses are different, but functions on bt
are the same.


-- 
Tomoaki AOKI    <junchoon@dec.sakura.ne.jp>