Date: Fri, 21 May 1999 20:07:54 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: "David E. Cross" <crossd@cs.rpi.edu> Cc: freebsd-hackers@FreeBSD.ORG, schimken@cs.rpi.edu, crossd@cs.rpi.edu Subject: Re: Repeatable kernel panic for 3.2-RELEASE NFS server Message-ID: <199905220307.UAA69634@apollo.backplane.com> References: <199905180532.BAA72781@cs.rpi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
:First, I would like to take this opportunity the thank Matt Dillon for
:his excellent work with NFS/TCP. Wow, way to go :)
:
:Now on to the real problem :)
:
:One of our users way able to reliably crash an NFS server 3 times today.
:I have since copied his program and have reliably crashed a seperate and
:unloaded machine with the exact same panic, "lockmgr: locking against
:myself". I check the recent DG patches that went in after -RELEASE and they
:do not appear to affect this part of the code. I have a full debugging
:kernel compiled, yet when I issue a 'gdb -k kernel.0 vmcore.0' (where
:kernel.0 is either the debugging or strip-debug kernel), I receive
:an unresolved symbol error for "gd_curpcb", so I cannot provide additional
:information at this time.
:
:In the morning I will try to distill the code down to a more potent
:test-case.
:--
:David Cross | email: crossd@cs.rpi.edu
Another possibly re: debugging. If you compile up a kernel with
options DDB and options BREAK_TO_DEBUGGER, the kernel will break into
DDB when the panic occurs. You can then issue a 'trace' command to get
a backtrace.
This may be good enough to determine what the problem is because
the cause of a 'lockmgr: locking against myself' panic tends to be
entirely contained within the current stack trace.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905220307.UAA69634>