Okay, looks like I might have a *good* one here ... inode hang

Marc G. Fournier scrappy at hub.org
Wed Jul 2 04:46:46 PDT 2003


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?



More information about the freebsd-stable mailing list