[Bug 293125] Panic after issuing ifconfig wlan0 list scan

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

Bjoern A. Zeeb <bz@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bz@FreeBSD.org
           Assignee|wireless@FreeBSD.org        |bz@FreeBSD.org
             Blocks|                            |273622

--- Comment #1 from Bjoern A. Zeeb <bz@FreeBSD.org> ---
Hi Deb,

interesting given this is a CNVio system.

List scan would only show what's in the scan cache;  ifconfig wlan0 scan would
possibly trigger a new scan and further changes.
Likely something else was going on at the same time given this is a net80211
state change.  Haven't seen a panic in lkpi_iv_newstate() in years.

On my system that offset points to a clause with a printf and a return()
statement, which in theory should only be triggered in case of a Channel Switch
Announcement (CSA).
But nothing which should panic.  I'll go and double-check offsets for 15.0-p2
specifically as well.

Do you by any chance have the core.<n>.txt file matching that vmcore.last?
If you do and it's significantly larger than 300 bytes, would you mind emailing
it out-of-band to bz@, as it may have the kernel message buffer (dmesg) in it
and we may possibly see if anything happened before that panic which is
relevant.
If it is around 300 bytes +/- a few hundred, then likely gdb is not installed
and crashinfo could not create the report.  I can help setting that up (and
re-running) if needed.


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273622
[Bug 273622] LinuxKPI based wireless drivers meta-bug
-- 
You are receiving this mail because:
You are the assignee for the bug.