Subject: Re: process wedged in vnlock
To: Bill Studenmund <firstname.lastname@example.org>
From: Tom Spindler <email@example.com>
Date: 02/27/2007 17:25:11
> > db> t/a 0xceff11c0
> > trace: pid 116 lid 1 at 0xcd22e9fc
> > sleepq_switch(0,0,cd1b7c74,c0363964,0) at netbsd:sleepq_switch+0x53
> > ltsleep(cd1b7c74,14,c0363964,0,cd1b7c74) at netbsd:ltsleep+0x13b
> > acquire(0,40500,c019de46,0,74) at netbsd:acquire+0x104
> > _lockmgr(cd1b7c74,10002,cd1b7bec,c0386930,937) at netbsd:_lockmgr+0x9bb
> Ok, this looks like normal vnode lock aquisition.
> What we need to know is which process holds this vnode lock, and what it
> is sleeping on.
OK. I have ddb, I have gdb w/ coredumps, I have LOCKDEBUG; how do
I determine this?