Synopsis: wapbl lockdebug panic during tcpdump run
State-Changed-From-To: open->feedback
State-Changed-By: [email protected]
State-Changed-When: Thu, 20 Aug 2026 03:45:17 +0000
State-Changed-Why:
Is this still reproducible?
In 11, and moreso in HEAD, we have much better diagnostics for this
class of lockup. If you could test with a current kernel, and you
can get a core dump, you may be able to:
(a) find who's hogging the kernel lock just from dmesg,
(b) use `show all locks' to see who's waiting for what lock, with or
without LOCKDEBUG, and
(c) use `mach cpu N' and `bt' to get a stack trace on cpuN (requires
a newer crash(8) binary) from the core dump
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.