Date: Fri, 15 May 2009 08:15:19 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-stable@freebsd.org Cc: Martin <nakal@web.de> Subject: Re: kernel trap 12 with interrupts disabled [bge0 on 7.2R] Message-ID: <200905150815.19452.jhb@freebsd.org> In-Reply-To: <20090514191026.0a90dbfc@zelda.local> References: <1696198956@web.de> <200905140916.40594.jhb@freebsd.org> <20090514191026.0a90dbfc@zelda.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 14 May 2009 1:10:26 pm Martin wrote:
> Am Thu, 14 May 2009 09:16:40 -0400
> schrieb John Baldwin <jhb@freebsd.org>:
>
> > On Thursday 14 May 2009 7:47:23 am Martin Sugioarto wrote:
> > [...]
> > > kernel trap 12 with interrupts disabled
> > >
> > >
> > > Fatal trap 12: page fault while in kernel mode
> > > cpuid = 0; apic id = 0
> > > fault virtual address = 0x80000000000
> >
> > Given that that is a single bit set, it could possibly be due to bad
> > RAM.
>
> This is the second panic output that appeared on the screen. I could not
read
> the first lines of the first panic. The last ones looked similar
> (same trap/process etc).
>
> > Does your kernel have debug symbols?
>
> This is GENERIC kernel configuration. The kernel was totally frozen. I could
> not type anything. I just noticed, I've got a vmcore.0 of the crash.
>
> I can see some other panic output when loading the kernel in kgdb:
>
> Unread portion of the kernel message buffer:
>
>
> Fatal trap 9: general protection fault while in kernel mode
When I have seen this, it has often been due to a hardware failure such as bad
RAM.
> cpuid = 2; apic id = 02
> instruction pointer = 0x8:0xffffffff805bbc66
Can you do 'x/i 0xffffffff805bbc66'? Also, can you walk up the stack to the
frame for this panic ('frame 7') and do 'info registers'?
--
John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905150815.19452.jhb>
