Re: Kernel panic - never had one before, what do I do?
I just got a panic. As I have never had one before, I don't know what to do. It's on another system so I don't have to reboot immediately (that would solve the problem temporarily, wouldn't it?) if someone would give me some advice, I could try to help debug it; however, as I'm not a coder (not a real one anyway), I don't know how much help I would be. I've got a nasty one booting with today's current. Think I vaguely recall seeing it before, so sorry if this is known. I'm gathering this data using the pen 'n paper approach, so if its not exactly right, you knwo why: ad4 READ Command timeout tag=0 serv=0 -resetting ata2: resetting devices Fatal trap 12: page fault while in kernel mode fault virtual address: 0x0 fault code: supervisor read, page not present instr pointer: 0x8:0xC0160441[note this is a custom kernel] stack pointer: 0x10:0xd1d6fc84 frame pointer: 0x10:0xd1d6fc8c code segment: base 0x0 limit 0xf type 0x1b DPL 0, pres 1, defy2 1, gron 1 processor effage: interrupt enabled, rswen, IOPC=0 current process = 12 (swi7: tty:sio check) kernel: type 12 trap, code = 0 stopped at reinit_bus+0xb: movl[something i can't read] 0(%esi), %eaf db> trace[i saw someone else do this] reinit_bus(0,2,c11f0c00, d1d6fcbc, c0146462) at reinit_bus+0x0 atapicam_reinit_bus(c11f0c00, 1, c338da80, c3470800, c015732c) at atapi_cam_reinit_bus+0x13 ata_reinit(c11f0c00, 7, c338da0, d1d6fcf0, c024c071) at ata_reinit+[something - possibly 0x34c] [more stuff - losing the will to live at this stage] Hope that helps somebody, shame i can't read my own writing. Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic - never had one before, what do I do?
On Fri, Mar 28, 2003 at 12:54:16AM -0500, taxman wrote: > that gives an error that is similiar to: > WARNING: syntax error on file /boot/loader.conf > dumpdev=/dev/ad0s1b > ^ Hi Tim, Please do 'dumpdev="/dev/ad0s1b". The doube quotes is a must . Jiawei -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic - never had one before, what do I do?
On Wednesday 26 March 2003 07:54 pm, Greg 'groggy' Lehey wrote: > On Wednesday, 26 March 2003 at 13:35:28 +, Jason Morgan wrote: > > I just got a panic. As I have never had one before, I don't know what to > > do. It's on another system so I don't have to reboot immediately (that > > would solve the problem temporarily, wouldn't it?) if someone would give > > me some advice, I could try to help debug it; however, as I'm not a > > coder (not a real one anyway), I don't know how much help I would be. > > > > It's a 5.0-CURRENT system, just installed and built last week. It > > paniced right after doing a source update (not a build, just cvsup). > > The panic error is as follows: > > > > panic: mtx_lock() of spin mutex vnode interlock @ > > /usr/src/sys/kern/vfs_subr.c:3187 > > Take a look at http://www.lemis.com/texts/panic.txt or > http://www.lemis.com/texts/panic.pdf and tell me if that helps. This > will be going into the new edition of "The Complete FreeBSD" in a few > days time, so I'm interested in getting something which is helpful. Hi Greg, I've been looking at doing the same thing, learn how to capture a crash dump, and analyze it etc. I'm a definite newbie at that so I thought it would be a good test for the article. It's pretty readable, but I had a problem with enabling the crash dump as noted: To enable dumping, put something like this in /boot/loader.conf: dumpdev=/dev/ad0s1b that gives an error that is similiar to: WARNING: syntax error on file /boot/loader.conf dumpdev=/dev/ad0s1b ^ the same syntax in /etc/rc.conf worked fine, however. This was on 4.8 RC2, but the syntax error appeared on a recent -current too. Thanks, Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic - never had one before, what do I do?
On Thu, Mar 27, 2003 at 11:24:44AM +1030, Greg 'groggy' Lehey wrote: > On Wednesday, 26 March 2003 at 13:35:28 +, Jason Morgan wrote: > > I just got a panic. As I have never had one before, I don't know what to > > do. It's on another system so I don't have to reboot immediately (that > > would solve the problem temporarily, wouldn't it?) if someone would give > > me some advice, I could try to help debug it; however, as I'm not a > > coder (not a real one anyway), I don't know how much help I would be. > > > > It's a 5.0-CURRENT system, just installed and built last week. It > > paniced right after doing a source update (not a build, just cvsup). > > The panic error is as follows: > > > > panic: mtx_lock() of spin mutex vnode interlock @ > > /usr/src/sys/kern/vfs_subr.c:3187 > > Take a look at http://www.lemis.com/texts/panic.txt or > http://www.lemis.com/texts/panic.pdf and tell me if that helps. This > will be going into the new edition of "The Complete FreeBSD" in a few > days time, so I'm interested in getting something which is helpful. Thanks. It has been a lot of help and I do think it is of value. Heck, I may even get a copy of "The Complete FreeBSD". Thanks again. Jason > > Greg > -- > See complete headers for address and phone numbers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic - never had one before, what do I do?
On Wednesday, 26 March 2003 at 13:35:28 +, Jason Morgan wrote: > I just got a panic. As I have never had one before, I don't know what to > do. It's on another system so I don't have to reboot immediately (that > would solve the problem temporarily, wouldn't it?) if someone would give > me some advice, I could try to help debug it; however, as I'm not a > coder (not a real one anyway), I don't know how much help I would be. > > It's a 5.0-CURRENT system, just installed and built last week. It > paniced right after doing a source update (not a build, just cvsup). > The panic error is as follows: > > panic: mtx_lock() of spin mutex vnode interlock @ > /usr/src/sys/kern/vfs_subr.c:3187 Take a look at http://www.lemis.com/texts/panic.txt or http://www.lemis.com/texts/panic.pdf and tell me if that helps. This will be going into the new edition of "The Complete FreeBSD" in a few days time, so I'm interested in getting something which is helpful. Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic - never had one before, what do I do?
On Wed, Mar 26, 2003 at 07:49:40PM +0100, Simon L. Nielsen wrote: > On 2003.03.26 13:35:28 +, Jason Morgan wrote: > > > I just got a panic. As I have never had one before, I don't know what to > > do. It's on another system so I don't have to reboot immediately (that > Have a look at > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING > for information on how to get more information from a panic. OK, so I'll set up my system to capture the crash dump for next time, but is there anything I can do right now? I'm at the db> debugging prompt, but I have not been provided with a panic message as shown in the first example. Is there a command to get this output? Jason > > -- > Simon L. Nielsen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic - never had one before, what do I do?
On 2003.03.26 13:35:28 +, Jason Morgan wrote: > I just got a panic. As I have never had one before, I don't know what to > do. It's on another system so I don't have to reboot immediately (that Have a look at http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING for information on how to get more information from a panic. -- Simon L. Nielsen pgp0.pgp Description: PGP signature ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Kernel panic - never had one before, what do I do?
I just got a panic. As I have never had one before, I don't know what to do. It's on another system so I don't have to reboot immediately (that would solve the problem temporarily, wouldn't it?) if someone would give me some advice, I could try to help debug it; however, as I'm not a coder (not a real one anyway), I don't know how much help I would be. It's a 5.0-CURRENT system, just installed and built last week. It paniced right after doing a source update (not a build, just cvsup). The panic error is as follows: panic: mtx_lock() of spin mutex vnode interlock @ /usr/src/sys/kern/vfs_subr.c:3187 Thanks, Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
