https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286219
Bjoern A. Zeeb <b...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |273620
CC| |b...@freebsd.org
Status|New |Open
--- Comment #2 from Bjoern A. Zeeb <b...@freebsd.org> ---
And what happened before the firmware crash in the log? Hmm dmesg from #2
doesn't have much more.
I could be wrong but this is not a valid command by the driver:
iwlwifi0: 0x01000112 | last cmd Id
The backtrace from the firmware crash indicates there was an ADD_STA going on.
The kernel panic happened on a different path in the follow-up.
lkpi_sta_auth_to_scan+0x74 according to the crash info is l2240:
2237 KASSERT(lsta != NULL && lsta->ni != NULL, ("%s: lsta %p ni %p "
2238 "lvif %p vap %p\n", __func__,
2239 lsta, (lsta != NULL) ? lsta->ni : NULL, lvif, vap));
2240 ni = lsta->ni; /* Reference held for lvif_bss.
*/
2241 sta = LSTA_TO_STA(lsta);
(gdb) p/x &((struct lkpi_sta *)0)->ni
$1 = 0x10
would mean the ni on the lsta went NULL, something in a DEBUG kernel the
kassert would catch; given the kassert documnets this should not happen, I
wonder even more. especially given we haven't seen problems with that since
last year some point I believe.
Is this reproducible on your build?
Referenced Bugs:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273620
[Bug 273620] iwlwifi meta-bug
--
You are receiving this mail because:
You are the assignee for the bug.
