Re: 14.1-RC1 panic: sleeping thread (tid 102234, pid 0) owns a non-sleepable lock
- In reply to: Dave Cottlehuber: "14.1-RC1 panic: sleeping thread (tid 102234, pid 0) owns a non-sleepable lock"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 30 May 2024 14:25:04 UTC
On Thu, 30 May 2024, Dave Cottlehuber wrote: Hi Dave, > Got 2 of these within a few minutes in quick succession: okay, that's the 3rd report of this in the last months now and seems to be a clean version of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277432 then without other prior effect (or did you have a FW crash or similar right before that which we don't see)? Note the fix for PR 275255 is NOT in 14 yet (and not in 14.1-R*). I am just checking as to my memory you have an 8xxx (if that's the same device)? You'll want to apply 5a4d24610fc6 as well and if it solves the other issues then that would very much help. I only got 1 feedback on that so far. (Sorry for mixing the two now) /bz > Unread portion of the kernel message buffer: > Sleeping thread (tid 102234, pid 0) owns a non-sleepable lock > KDB: stack backtrace of thread 102234: > #0 0xffffffff80b402ab at mi_switch+0xbb > #1 0xffffffff80b3fa28 at _sleep+0x1e8 > #2 0xffffffff80b96bc1 at taskqueue_thread_loop+0xb1 > #3 0xffffffff80aed57f at fork_exit+0x7f > #4 0xffffffff80fd822e at fork_trampoline+0xe > panic: sleeping thread > cpuid = 0 > time = 1714556112 > KDB: stack backtrace: > #0 0xffffffff80b8047d at kdb_backtrace+0x5d > #1 0xffffffff80b331a1 at vpanic+0x131 > #2 0xffffffff80b33063 at panic+0x43 > #3 0xffffffff80b98e9e at propagate_priority+0x29e > #4 0xffffffff80b999d1 at turnstile_wait+0x301 > #5 0xffffffff80b0f745 at __mtx_lock_sleep+0x175 > #6 0xffffffff80d94640 at linuxkpi_ieee80211_find_sta+0xd0 > #7 0xffffffff80d946df at linuxkpi_ieee80211_find_sta_by_ifaddr+0x6f > #8 0xffffffff83a8a456 at iwl_mvm_rx_rx_mpdu+0x1e6 > #9 0xffffffff83ab81a5 at iwl_pcie_rx_handle+0x485 > #10 0xffffffff83ab7a3d at iwl_pcie_napi_poll+0x2d > #11 0xffffffff80da308f at lkpi_napi_task+0xf > #12 0xffffffff80b95952 at taskqueue_run_locked+0x182 > #13 0xffffffff80b96bd2 at taskqueue_thread_loop+0xc2 > #14 0xffffffff80aed57f at fork_exit+0x7f > #15 0xffffffff80fd822e at fork_trampoline+0xe > > https://people.freebsd.org/~dch/tmp/panic.20240530-1053.txt has slightly more info, and /home/dch/tmp/vmcore.2.xz has even more. Thanks! I'll try o have a look at the core file unless yo uhave the full message buffer from it already extracted? -- Bjoern A. Zeeb r15:7