Re: Intermittent -- yet regular -- v6.3 kernel panic
Ryan Coleman wrote: Kris Kennaway wrote: Bruce Cran wrote: On Fri, 13 Jun 2008 14:49:29 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? To be of any use we need a backtrace. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details. First you need to configure a dump device then when the system crashes a crash dump will be written to /var/crash by default. You then run kgdb on the file to get the backtrace. It's quite likely to be due to bad hardware though. Kris It's crashed twice and stalled on the dump. Any thoughts? Anyone? I'm going to have to disable the dump as I need the machine to come back up if possible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
On Sat, 14 Jun 2008 01:24:07 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Ryan Coleman wrote: Kris Kennaway wrote: Bruce Cran wrote: On Fri, 13 Jun 2008 14:49:29 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? To be of any use we need a backtrace. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details. First you need to configure a dump device then when the system crashes a crash dump will be written to /var/crash by default. You then run kgdb on the file to get the backtrace. It's quite likely to be due to bad hardware though. Kris It's crashed twice and stalled on the dump. Any thoughts? Anyone? I'm going to have to disable the dump as I need the machine to come back up if possible. Since it sounds like it's bad hardware, the dump isn't going to provide any useful information so you may as well disable it until you can swap out the RAM etc. -- Bruce Cran signature.asc Description: PGP signature
Intermittent -- yet regular -- v6.3 kernel panic
Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? Wednesday it was crashed by *pagedaemon* and about 15 hours earlier by *g_down*. This is the only record - thus far - to hit the syslog. Also it crashed twice today and has not recorded I have an 8x1TB RAID5 on a HighPoint Tech RocketRaid, the primary drive is a 1TB drive partitioned three times. / 30G, 4G swap and the rest is /usr. Please advise -- Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
It just happened again: Jun 13 14:32:21 UnixBox2 kernel: Jun 13 14:32:21 UnixBox2 kernel: Jun 13 14:32:21 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 13 14:32:21 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 13 14:32:21 UnixBox2 kernel: fault virtual address = 0x0 Jun 13 14:32:21 UnixBox2 kernel: fault code = supervisor read, page not present Jun 13 14:32:21 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 13 14:32:21 UnixBox2 kernel: stack pointer = 0x28:0xec0738e0 Jun 13 14:32:21 UnixBox2 kernel: frame pointer = 0x28:0xec0738e4 Jun 13 14:32:21 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 13 14:32:21 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 13 14:32:21 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 13 14:32:21 UnixBox2 kernel: current process= 1385 (cp) Jun 13 14:32:21 UnixBox2 kernel: trap number= 12 Jun 13 14:32:21 UnixBox2 kernel: panic: page fault Jun 13 14:32:21 UnixBox2 kernel: cpuid = 1 Jun 13 14:32:21 UnixBox2 kernel: Uptime: 4h54m13s Jun 13 14:32:21 UnixBox2 kernel: Cannot dump. No dump device defined. Ryan Coleman wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? Wednesday it was crashed by *pagedaemon* and about 15 hours earlier by *g_down*. This is the only record - thus far - to hit the syslog. Also it crashed twice today and has not recorded I have an 8x1TB RAID5 on a HighPoint Tech RocketRaid, the primary drive is a 1TB drive partitioned three times. / 30G, 4G swap and the rest is /usr. Please advise -- Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
I will attempt to do this and report back when it happens again. Bruce Cran wrote: On Fri, 13 Jun 2008 14:49:29 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? To be of any use we need a backtrace. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details. First you need to configure a dump device then when the system crashes a crash dump will be written to /var/crash by default. You then run kgdb on the file to get the backtrace. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
On Fri, 13 Jun 2008 14:49:29 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? To be of any use we need a backtrace. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details. First you need to configure a dump device then when the system crashes a crash dump will be written to /var/crash by default. You then run kgdb on the file to get the backtrace. -- Bruce Cran signature.asc Description: PGP signature
Re: Intermittent -- yet regular -- v6.3 kernel panic
Bruce Cran wrote: On Fri, 13 Jun 2008 14:49:29 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? To be of any use we need a backtrace. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details. First you need to configure a dump device then when the system crashes a crash dump will be written to /var/crash by default. You then run kgdb on the file to get the backtrace. It's quite likely to be due to bad hardware though. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
I'm sure. I could get different RAM this weekend, but that just makes me angry. I bought all the items from recommended lists on NewEgg two weeks ago. This is probably the 11th crash in 12 days. It's quite likely to be due to bad hardware though. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
[Don't top-post, please.] It's quite likely to be due to bad hardware though. Ryan Coleman [EMAIL PROTECTED] writes: I'm sure. I could get different RAM this weekend, but that just makes me angry. I bought all the items from recommended lists on NewEgg two weeks ago. This is probably the 11th crash in 12 days. Buying good hardware improves your odds a lot, but failures can still happen. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
Kris Kennaway wrote: Bruce Cran wrote: On Fri, 13 Jun 2008 14:49:29 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? To be of any use we need a backtrace. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details. First you need to configure a dump device then when the system crashes a crash dump will be written to /var/crash by default. You then run kgdb on the file to get the backtrace. It's quite likely to be due to bad hardware though. Kris It's crashed twice and stalled on the dump. Any thoughts? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
