Date: Tue, 14 May 2024 06:31:48 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 275255] iwlwifi: panic after iwlwifi0: lkpi_iv_newstate: error -5 during state transition 5 (RUN) -> 0 (INIT) (8xxx/9xxx chipsets) Message-ID: <bug-275255-21060-xBB8h5xCYe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275255-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-275255-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=3D275255 --- Comment #16 from Bakul Shah <bakul@iitbombay.org> --- I tested this in a VM with a fairly recent -current (commit da4230af3fda). ifconfig wlan0 create wlandev iwlwifi0 service netif start wlan0 works fine and the machine stayed up quite a while. But when I did a "shutdown now" it paniced. I repeated this a few times: syslogd: exiting on signal 15 iwlwifi0: Couldn't drain frames for staid 0, status 0x8 iwlwifi0: lkpi_sta_run_to_init:2309: mo_sta_state(NOTEXIST) failed: -5 iwlwifi0: lkpi_iv_newstate: error -5 during state transition 5 (RUN) -> 0 (INIT) panic: INIT state change failed cpuid =3D 0 time =3D 1715667397 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00688bb= c60 vpanic() at vpanic+0x13f/frame 0xfffffe00688bbd90 panic() at panic+0x43/frame 0xfffffe00688bbdf0 ieee80211_newstate_cb() at ieee80211_newstate_cb+0x422/frame 0xfffffe00688b= be40 taskqueue_run_locked() at taskqueue_run_locked+0x1c2/frame 0xfffffe00688bbe= c0 taskqueue_thread_loop() at taskqueue_thread_loop+0xd3/frame 0xfffffe00688bb= ef0 fork_exit() at fork_exit+0x82/frame 0xfffffe00688bbf30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00688bbf30 --- trap 0xc, rip =3D 0x39f11dbd331a, rsp =3D 0x39f122c47f48, rbp =3D 0x39f= 122c47f60 --- KDB: enter: panic [ thread pid 0 tid 100266 ] Stopped at kdb_enter+0x33: movq $0,0x1053452(%rip) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275255-21060-xBB8h5xCYe>