Re: Crash Report

On Fri, Jan 15, 2010 at 6:10 PM, Simon Baker <[email protected]> wrote:
> Hi Guys,
>
> No idea if this is of any interest, but I had a m0n0wall spontaneously
> reboot this afternoon.
>
> Here's the relevant bit from dmesg:
>
> Jan 15 15:39:12 section9 kernel: Fatal trap 12: page fault while in kernel
> mode
> Jan 15 15:39:12 section9 kernel: fault virtual address  = 0x15211cf8
> Jan 15 15:39:12 section9 kernel: fault code             = supervisor read,
> page not present
> Jan 15 15:39:12 section9 kernel: instruction pointer    = 0x20:0xc06bebe4
> Jan 15 15:39:12 section9 kernel: stack pointer          = 0x28:0xccdf8c44
> Jan 15 15:39:12 section9 kernel: frame pointer          = 0x28:0xccdf8c48
> Jan 15 15:39:12 section9 kernel: code segment           = base 0x0, limit
> 0xfffff, type 0x1b
> Jan 15 15:39:12 section9 kernel: = DPL 0, pres 1, def32 1, gran 1
> Jan 15 15:39:12 section9 kernel: processor eflags       = interrupt enabled,
> resume, IOPL = 0
> Jan 15 15:39:12 section9 kernel: current process                = 16 (swi5:
> +)
> Jan 15 15:39:12 section9 kernel: trap number            = 12
> Jan 15 15:39:12 section9 kernel: panic: page fault
> Jan 15 15:39:12 section9 kernel: Uptime: 5d23h15m27s
> Jan 15 15:39:12 section9 kernel: Cannot dump. No dump device defined.
> Jan 15 15:39:12 section9 kernel: Automatic reboot in 15 seconds - press a
> key on the console to abort
>
> Any ideas people?
>
> Regards,
>
> Simon.
>


Generic pc hardware?
Bad ram module?