Intermittent -- yet regular -- v6.3 kernel panic

[Ryan Coleman]

Kris Kennaway wrote:
> Bruce Cran wrote:
>> On Fri, 13 Jun 2008 14:49:29 -0500
>> Ryan Coleman <ryan.coleman at cwis.biz> 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 0xfffff, 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?