Re: Repeatable kernel panic for 3.2-RELEASE NFS server
I have tried gdb from 3.2-BETA, 3.2-RELEASE, and 3.2-STABLE, as well as the gdb that was built from the exact same CVS checkout as the kernel owas from, they all give the same error. -- David Cross | email: cro...@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 Some of the gdb source files were incorrectly tagged for 3.2 branch, I'll fix it. -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Repeatable kernel panic for 3.2-RELEASE NFS server
Is there anything I can do on my end (we have a complete CVS repository, synced every 4 hours. I would like to use the *exact* same gdb that we compiled the world from if possible, I am affraid of using a more recent gdb will result in not being able to read the core (I am unable to use a 3.1-STABLE gdb to read the core from a 3.2-STABLE system). -- David Cross | email: cro...@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 majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Repeatable kernel panic for 3.2-RELEASE NFS server
Is there anything I can do on my end (we have a complete CVS repository, synced every 4 hours. I would like to use the *exact* same gdb that we compiled the world from if possible, I am affraid of using a more recent gdb will result in not being able to read the core (I am unable to use a 3.1-STABLE gdb to read the core from a 3.2-STABLE system). -- David Cross | email: cro...@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 I just backed out changes I made that shouldn't be in the 3.x branch, you may cvsup again. If you can't wait, you may back out the changes yourself, they are -j1.16 -j1.15 /usr/src/gnu/usr.bin/binutils/gdb/i386/kvm-fbsd.c, -j1.20 -j1.19 /usr/src/gnu/usr.bin/binutils/gdb/i386/freebsd-nat.c (cvs update -j doesn't seem to work, I had to get the diff and patch myself). -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Repeatable kernel panic for 3.2-RELEASE NFS server
On Fri, 21 May 1999, Matthew Dillon wrote: : entirely contained within the current stack trace. :All my kernels are now DDB kernels :) But since I do almost all of :my work remotely they are DDB_UNATTENDED, and the machine I am panic-ing :is not on the serial console server (sorry). I do have another question :about DDB, I unstalled -STABLE as of today (from releng3.fre...) and I :compiled the kernel with DDB, and DDB_UNATTENDED per usual. Now when I :C-A-E to get into the debugger and type 'panic' it drops me at another :debugging prompt. If I type panic from that I get the real thing, any ideas? : :My next email will hopefully have the stack trace for this panic. :-- :David Cross | email: cro...@cs.rpi.edu Panic has a counter. The first time it is called it tries to drop into the debugger. The second time it is called it reboots the machine for real. When you control-alt-escape, you have not yet called panic for the first time, so when you panic manually from the DDB prompt it drops you into the debugger again. Second time's the charm! Since the debugger repeats the previous command if you just hit return, I've gotten used to simply typing 'panic returnreturnreturnreturn...' I use that too :-). For the alpha, I put in a 'halt' command (also linked to remote-gdb's kill operation) which drops the machine back to the firmware which is handy if you don't care about buffers not being synced. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Repeatable kernel panic for 3.2-RELEASE NFS server
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 Are you sure this is NFS related? I can certainly reliably reproduce that and other panics (reported in kern/11629, includes a fix). Ok, well, it just happened again. I am certain that NFS is tripping this, as it is the only access to the box in question (yes, the panic may be elsewhere, but it comes through the NFS subsystem). After I received your email I applied the pathc and attempted my situation again. *wham*. It would be really good to get a stack trace from these crashes, but I cannot due to the error mentioned before: gdb -k kernel.1 vmcore.1 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd... (no debugging symbols found)... IdlePTD 2998272 kernel symbol `gd_curpcb' not found. (kgdb) Any ideas? -- David Cross | email: cro...@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 majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Repeatable kernel panic for 3.2-RELEASE NFS server
gdb -k kernel.1 vmcore.1 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd... (no debugging symbols found)... IdlePTD 2998272 kernel symbol `gd_curpcb' not found. (kgdb) Any ideas? You need to use gdb comes with 3.2-RELEASE. -- David Cross | email: cro...@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 -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Repeatable kernel panic for 3.2-RELEASE NFS server
gdb -k kernel.1 vmcore.1 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd... (no debugging symbols found)... IdlePTD 2998272 kernel symbol `gd_curpcb' not found. (kgdb) Any ideas? You need to use gdb comes with 3.2-RELEASE. I have tried gdb from 3.2-BETA, 3.2-RELEASE, and 3.2-STABLE, as well as the gdb that was built from the exact same CVS checkout as the kernel owas from, they all give the same error. -- David Cross | email: cro...@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 majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Repeatable kernel panic for 3.2-RELEASE NFS server
: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: cro...@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 dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Repeatable kernel panic for 3.2-RELEASE NFS server
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. All my kernels are now DDB kernels :) But since I do almost all of my work remotely they are DDB_UNATTENDED, and the machine I am panic-ing is not on the serial console server (sorry). I do have another question about DDB, I unstalled -STABLE as of today (from releng3.fre...) and I compiled the kernel with DDB, and DDB_UNATTENDED per usual. Now when I C-A-E to get into the debugger and type 'panic' it drops me at another debugging prompt. If I type panic from that I get the real thing, any ideas? My next email will hopefully have the stack trace for this panic. -- David Cross | email: cro...@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 majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Repeatable kernel panic for 3.2-RELEASE NFS server
: entirely contained within the current stack trace. :All my kernels are now DDB kernels :) But since I do almost all of :my work remotely they are DDB_UNATTENDED, and the machine I am panic-ing :is not on the serial console server (sorry). I do have another question :about DDB, I unstalled -STABLE as of today (from releng3.fre...) and I :compiled the kernel with DDB, and DDB_UNATTENDED per usual. Now when I :C-A-E to get into the debugger and type 'panic' it drops me at another :debugging prompt. If I type panic from that I get the real thing, any ideas? : :My next email will hopefully have the stack trace for this panic. :-- :David Cross | email: cro...@cs.rpi.edu Panic has a counter. The first time it is called it tries to drop into the debugger. The second time it is called it reboots the machine for real. When you control-alt-escape, you have not yet called panic for the first time, so when you panic manually from the DDB prompt it drops you into the debugger again. Second time's the charm! Since the debugger repeats the previous command if you just hit return, I've gotten used to simply typing 'panic returnreturnreturnreturn...' -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Repeatable kernel panic for 3.2-RELEASE NFS server
cro...@cs.rpi.edu (David E. Cross) writes: 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 Are you sure this is NFS related? I can certainly reliably reproduce that and other panics (reported in kern/11629, includes a fix). To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Repeatable kernel panic for 3.2-RELEASE NFS server
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: cro...@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 majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
