Date: Fri, 6 Feb 2004 06:38:02 -0500 From: Chris BeHanna <chris@behanna.org> To: freebsd-current@freebsd.org Subject: Re: Processes blocked on getblk or ufs Message-ID: <200402060638.02548.chris@behanna.org> In-Reply-To: <EE3D3FBAFFCAED448C21C398FDAD91AC013BDEA8@EBE1.gc.nat> References: <EE3D3FBAFFCAED448C21C398FDAD91AC013BDEA8@EBE1.gc.nat>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 05 February 2004 15:58, Robin P. Blanchard wrote:
> > I have a machine sitting at the ddb prompt in exactly this
> > state. Anyone know how to dig something useful out of the
> > current state the buffer cache is in? I know how to find out
> > what vnodes are locked but don't know how to go from that to
> > see what underlying buffers are causing the problem.
> >
> > I should be able to cause a dump of the machine as well but
> > it has 2Gb of memory in it so transferring the dump to
> > someone other than me who could look at it might be painful...
>
> Well...I went ahead an induced a dump (where the 2650 has been wedged in
> "getblk" since last installworld). Anyone want to take a look at it. It's a
> 1024M dump compressed to 171M.
Since others are unlikely to have the exact same sources that you
have, it'd be best if you could do some preliminary poking yourself,
since your sources match your kernel.
If you know any C, printing the contents of variables referenced
on the line that triggered the crash would be helpful.
gdb -k /usr/obj/usr/src/sys/YOURKERNEL/kernel.debug /var/crash/vmcore.0
gdb> bt
gdb> frame frame-number-just-before-the-trap-code
gdb> p some-interesting-variable
--
Chris BeHanna
Software Engineer (Remove "bogus" before responding.)
chris@bogus.behanna.org
Turning coffee into software since 1990.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402060638.02548.chris>