hard deadlock(?) on -current; some debugging info, need help

Peter Jeremy PeterJeremy at optushome.com.au
Thu May 26 12:12:22 PDT 2005


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


More information about the freebsd-current mailing list