[Bug 277432] iwlwifi panic: Sleeping thread owns a non-sleepable lock

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 24 Nov 2024 08:00:52 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277432

zhang feng <bsdlisp@yeah.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bsdlisp@yeah.net

--- Comment #3 from zhang feng <bsdlisp@yeah.net> ---
I got the similar panic at 14.1.

FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC amd64

/var/log/messages:
Nov 23 17:39:00 zfeng wpa_supplicant[340]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=c4:48:fa:4d:92:c0 reason=0
Nov 23 17:39:00 zfeng kernel: iwlwifi0: linuxkpi_ieee80211_connection_loss: vif
0xfffffe0110c46e80 vap 0xfffffe0110c46010 state RUN
Nov 23 17:39:00 zfeng kernel: wlan0: link state changed to DOWN
Nov 23 17:39:00 zfeng wpa_supplicant[340]: ioctl[SIOCS80211, op=20, val=0,
arg_len=7]: Can't assign requested address
Nov 23 17:39:01 zfeng kernel: iwlwifi0: Couldn't drain frames for staid 0,
status 0x8
Nov 23 17:39:01 zfeng kernel: iwlwifi0: lkpi_sta_run_to_init:2310:
mo_sta_state(NOTEXIST) failed: -5
Nov 23 17:39:01 zfeng kernel: iwlwifi0: lkpi_iv_newstate: error -5 during state
transition 5 (RUN) -> 0 (INIT)
Nov 23 17:39:02 zfeng wpa_supplicant[340]: wlan0: Trying to associate with
c4:48:fa:4d:92:c0 (SSID='ChinaNet-007' freq=2412 MHz)
Nov 23 17:39:02 zfeng kernel: iwlwifi0: lkpi_sta_scan_to_auth:1131: lvif
0xfffffe0110c46000 vap 0xfffffe0110c46010 iv_bss 0xfffffe010eb9e000 lvif_bss
0xfffff8000b211800 lvif_bss->ni 0xfffffe010eabe000 synched 0
Nov 23 17:39:02 zfeng kernel: iwlwifi0: lkpi_iv_newstate: error 16 during state
transition 1 (SCAN) -> 2 (AUTH)
Nov 23 17:40:14 zfeng syslogd: kernel boot file is /boot/kernel/kernel
Nov 23 17:40:14 zfeng kernel: Sleeping thread (tid 100866, pid 0) owns a
non-sleepable lock
Nov 23 17:40:14 zfeng kernel: KDB: stack backtrace of thread 100866:
Nov 23 17:40:14 zfeng kernel: #0 0xffffffff80b3faab at mi_switch+0xbb
Nov 23 17:40:14 zfeng kernel: #1 0xffffffff80b3f228 at _sleep+0x1e8
Nov 23 17:40:14 zfeng kernel: #2 0xffffffff80b96341 at
taskqueue_thread_loop+0xb1
Nov 23 17:40:14 zfeng kernel: #3 0xffffffff80aecd1f at fork_exit+0x7f
Nov 23 17:40:14 zfeng kernel: #4 0xffffffff80fd7aae at fork_trampoline+0xe
Nov 23 17:40:14 zfeng kernel: panic: sleeping thread
Nov 23 17:40:14 zfeng kernel: cpuid = 0
Nov 23 17:40:14 zfeng kernel: time = 1732354742
Nov 23 17:40:14 zfeng kernel: KDB: stack backtrace:
Nov 23 17:40:14 zfeng kernel: #0 0xffffffff80b7fbfd at kdb_backtrace+0x5d
Nov 23 17:40:14 zfeng kernel: #1 0xffffffff80b32961 at vpanic+0x131
Nov 23 17:40:14 zfeng kernel: #2 0xffffffff80b32823 at panic+0x43
Nov 23 17:40:14 zfeng kernel: #3 0xffffffff80b9861e at propagate_priority+0x29e
Nov 23 17:40:14 zfeng kernel: #4 0xffffffff80b99151 at turnstile_wait+0x301
Nov 23 17:40:14 zfeng kernel: #5 0xffffffff80b0ef05 at __mtx_lock_sleep+0x175
Nov 23 17:40:14 zfeng kernel: #6 0xffffffff80d93dd0 at
linuxkpi_ieee80211_find_sta+0xd0
Nov 23 17:40:14 zfeng kernel: #7 0xffffffff80d93e6f at
linuxkpi_ieee80211_find_sta_by_ifaddr+0x6f
Nov 23 17:40:14 zfeng kernel: #8 0xffffffff83abaadc at iwl_mvm_rx_mpdu_mq+0x41c
Nov 23 17:40:14 zfeng kernel: #9 0xffffffff83ae61a5 at iwl_pcie_rx_handle+0x485
Nov 23 17:40:14 zfeng kernel: #10 0xffffffff83ae5c00 at
iwl_pcie_napi_poll_msix+0x30
Nov 23 17:40:14 zfeng kernel: #11 0xfsleepinuxkpifffffff80da281f at
lkpi_napi_task+0xf
Nov 23 17:40:14 zfeng kernel: #12 0xffffffff80b950d2 at
taskqueue_run_locked+0x182
Nov 23 17:40:14 zfeng kernel: #13 0xffffffff80b96352 at
taskqueue_thread_loop+0xc2
Nov 23 17:40:14 zfeng kernel: #14 0xffffffff80aecd1f at fork_exit+0x7f
Nov 23 17:40:14 zfeng kernel: #15 0xffffffff80fd7aae at fork_trampoline+0xe
Nov 23 17:40:14 zfeng kernel: Uptime: 1h52m55s

-- 
You are receiving this mail because:
You are the assignee for the bug.