Re: recurring kernel panic
On Nov 9, 2007 12:46 PM, Rob [EMAIL PROTECTED] wrote: Kelly Martin wrote: I'm getting daily kernel panics. The server was running fine for about a month, the only changes I've made recently have been to update all my ports. It's running on older i386 hardware, no special devices Like the others said -- I'd seriously suspect hardware problems. Memory is a good place to start. Try MemTest: http://www.memtest86.com/ Thanks to everyone for the help. It was indeed a hardware failure, a power supply issue. With so many people using, looking at or working on the FreeBSD kernel, I knew it had to be something other than just my applications causing a kernel panic. thanks, kelly ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
recurring kernel panic
I'm getting daily kernel panics. The server was running fine for about a month, the only changes I've made recently have been to update all my ports. It's running on older i386 hardware, no special devices attached. Here's the console message I'm getting (copied by hand): - Fatal trap 30: reserved (unknown) fault while in kernel mode cupid = 0; apic id = 00 instruction pointer = 0x20:0xc0b41129 stack pointer = 0x28:0xd0225cd8 frame pointer= 0x28:0xd0225cd8 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 10 (idle: cpu0) trap number = 30 panic: reserved (unknown) fault cupid = 0 Uptime 19h28m38s Cannot dump. No dump device defined. Automatic reboot in 15 seconds – press a key on the console to abort Rebooting… Keyboard reset did not work, attempting CPU shutdown - A few questions to help diagnose: (1) how do I use my hard disk as a dump device for these kernel panics? (2) why does the keyboard reset not work, leaving the panic'ed machine hanging indefinitely? (I've tried two different PS/2 keyboards... no luck) (3) any other information I can provide, such as ports I have installed? I am running FreeBSD my.server.com 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 (with all security patches except FreeBSD-SA-07:03.ipv6) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recurring kernel panic
Kelly Martin wrote: I'm getting daily kernel panics. The server was running fine for about a month, the only changes I've made recently have been to update all my ports. It's running on older i386 hardware, no special devices attached. Here's the console message I'm getting (copied by hand): - Fatal trap 30: reserved (unknown) fault while in kernel mode cupid = 0; apic id = 00 instruction pointer = 0x20:0xc0b41129 stack pointer = 0x28:0xd0225cd8 frame pointer= 0x28:0xd0225cd8 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 10 (idle: cpu0) trap number = 30 panic: reserved (unknown) fault cupid = 0 Uptime 19h28m38s Cannot dump. No dump device defined. Automatic reboot in 15 seconds – press a key on the console to abort Rebooting… Keyboard reset did not work, attempting CPU shutdown - This looks pretty suspicious to me, I'd guess your hardware has failed. A few questions to help diagnose: (1) how do I use my hard disk as a dump device for these kernel panics? (2) why does the keyboard reset not work, leaving the panic'ed machine hanging indefinitely? (I've tried two different PS/2 keyboards... no luck) (3) any other information I can provide, such as ports I have installed? http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recurring kernel panic
On Nov 9, 2007 10:41 AM, Kris Kennaway [EMAIL PROTECTED] wrote: This looks pretty suspicious to me, I'd guess your hardware has failed. This same hardware has run OpenBSD for years. Not sure how to track down a hardware failure, unfortunately. http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Thanks, I've setup a dump directory now for the next kernel panic... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recurring kernel panic
Kelly Martin wrote: On Nov 9, 2007 10:41 AM, Kris Kennaway [EMAIL PROTECTED] wrote: This looks pretty suspicious to me, I'd guess your hardware has failed. This same hardware has run OpenBSD for years. Not really relevant. When something makes the transition from working to broken there will be a first time when it fails. No-one wants to believe it is happening to them, but hardware fails *all the time*. Not sure how to track down a hardware failure, unfortunately. There is plenty of documentation online about this (also hundreds of discussions in the archives), but it basically involves making use of the modularity of your PC to swap out components and attempt to isolate the fault. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recurring kernel panic
Kelly Martin wrote: I'm getting daily kernel panics. The server was running fine for about a month, the only changes I've made recently have been to update all my ports. It's running on older i386 hardware, no special devices Like the others said -- I'd seriously suspect hardware problems. Memory is a good place to start. Try MemTest: http://www.memtest86.com/ -Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
