On Sun, 4 Jul 2004, Niklas Saers wrote: > I'm not an experienced kernel-debugger, and hitting Ctrl-Alt-Esc only > gives me a trace of the keyboard. If this is a good route to take, hints > to how to go about are most welcome. Sounds like a file system vnode lock deadlock. Try using the "show lockedvnodes" command to identify locked vnodes and processes holding them; then use the "trace <pid>" command to trace the processes in question to see where they blocked while holding vnode locks. It may be useful to build your kernel with "options DEBUG_LOCKS", which will provide additional information about vnode locking (at a performance hit) -- in particular, it will have each lock trace where the lock was last acquired. If you're running with WITNESS, you can use the WITNESS debugging features to identify other potential deadlocks. However, it sounds like this is a vnode deadlock, and vnodes use "lockmgr" for their higher level locking, and lockmgr isn't currently able to use WITNESS. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert_at_fledge.watson.org Principal Research Scientist, McAfee ResearchReceived on Sun Jul 04 2004 - 13:11:52 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:00 UTC