Date: Fri, 27 May 2005 05:12:17 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Ted Faber <faber@isi.edu> Cc: freebsd-current@freebsd.org Subject: Re: hard deadlock(?) on -current; some debugging info, need help Message-ID: <20050526191217.GA17267@cirb503493.alcatel.com.au> In-Reply-To: <20050526160846.GA6851@pun.isi.edu> References: <20050526001806.GA1008@pun.isi.edu> <20050526080928.GE12640@cirb503493.alcatel.com.au> <20050526160846.GA6851@pun.isi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2005-May-26 09:08:46 -0700, Ted Faber wrote: >On Thu, May 26, 2005 at 06:09:28PM +1000, Peter Jeremy wrote: >> Nothing is waiting on physical I/O, but there are lots of locked vnodes. >> I notice there's a sh(? - pid 10715) blocked on nfsreq. Can you reproduce >> the problem without the NFS mounted filesystems? > >I have a laptop on the same network that uses NFS much less aggressively >and it has never locked up. I understand that's anecdotal. It's pretty >hard to reconfigure the desktop into a position where I get work done >and don't use NFS here. OK. I have no reason to believe the problem is in NFS, it was just a "reduce the number of possibilities" type suggestion. >I've let it sit a few minutes. I'll try it again next lockup, just in >case. I've just typed "panic" from the debugger. If there's a better >way, please let me know. You could try "call doadump". -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050526191217.GA17267>