Date: Tue, 10 Jan 2023 09:31:18 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 268565] panic after "killall wpa_supplicant" followed by "/etc/rc.d/netif start" with rtw880 Message-ID: <bug-268565-21060-Vm7iNSLSHo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268565-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-268565-21060@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268565 Mikhail Pchelin <misha@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #239027|0 |1 is obsolete| | --- Comment #5 from Mikhail Pchelin <misha@freebsd.org> --- Created attachment 239374 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D239374&action= =3Dedit patch v3 Next attempt to fix the panic. Thinking about it more, I must agree that fixing lsta in xmit function is wrong. Panic occurs while transiting from INIT state to SCAN, currently this transition is not handled in a special way, the handler is lkpi_sta_state_do_nada(), which is a stub. I suggest to check for lsta existence in the new handler and allocating it, if it's not set. INIT->SCAN also happens on boot, but in that case we also create a VAP, so = lsta allocation is handled in that chain, so there is no crash. Opinions? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268565-21060-Vm7iNSLSHo>