Date: Tue, 18 May 1999 01:32:31 -0400 From: "David E. Cross" <crossd@cs.rpi.edu> To: freebsd-hackers@freebsd.org Cc: schimken@cs.rpi.edu, crossd@cs.rpi.edu Subject: Repeatable kernel panic for 3.2-RELEASE NFS server Message-ID: <199905180532.BAA72781@cs.rpi.edu>
next 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 Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD 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?199905180532.BAA72781>