Date: Wed, 2 Jul 2003 08:46:40 -0300 (ADT) From: "Marc G. Fournier" <scrappy@hub.org> To: David Schultz <das@FreeBSD.org> Cc: Ted Mittelstaedt <tedm@toybox.placo.com> Subject: Re: Okay, looks like I might have a *good* one here ... inode hang Message-ID: <20030702084558.J67063@hub.org> In-Reply-To: <20030702073306.GA3324@HAL9000.homeunix.com> References: <20030701155450.J67063@hub.org> <20030702073306.GA3324@HAL9000.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2 Jul 2003, David Schultz wrote:
> On Tue, Jul 01, 2003, Marc G. Fournier wrote:
> [...]
> > and I have a vmcore to work on here !! :)
>
> Yes, this does look promising. Can you look at
> *(struct lock *)0x8a4ef300 (the lock the second
> process is trying to acquire) also?
(kgdb) print *(struct lock *)0x8a4ef300
$2 = {lk_interlock = {lock_data = 0}, lk_flags = 2098240, lk_sharecount = 0, lk_waitcount = 2, lk_exclusivecount = 1, lk_prio = 8, lk_wmesg = 0x80263d4a "inode", lk_timo = 6,
lk_lockholder = 75285}
> It probably points back to the first process, but we might as well be
> sure. It might also be interesting to see the ndp arguments to the
> namei calls, but the problem can probably be tracked down without them.
How do I do this one?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030702084558.J67063>