On Tue, 10 Sep 2002, Robert Watson wrote:

> ...  Also, last time I tried to use the ddb
> show lockedvnods command, I got the problem attached below due to locking
> issues, which makes it a lot harder to debug locking problems...
> Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
> [EMAIL PROTECTED]      Network Associates Laboratories
> db> show lockedvnods
> Locked vnodes
> panic: blockable sleep lock (sleep mutex) mountlist @
> ../../../kern/vfs_subr.c:2621
> Debugger("panic")

Try removing all the locking in the command.  ddb commands can't use locking.
I have printfs in _mtx_lock_flags(), _mtx_lock_spin_flags(),
_mtx_lock_sleep() and _mtx_lock_spin() to detect locking when ddb is active.

The error handling would be better if trap_fatal() were called before panic
panic(), like it is for null pointer panics.  ddb on i386's then notices
that it shot itself and longjmps to its entry point.  This handles things
like reading through garbage pointers OK, but not external state changes
like locking.  Maybe my printfs should be trap_fatals or or direct longjmps.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to