Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Jun 2006 19:47:32 +0100 (BST)
From:      Robert Watson <rwatson@FreeBSD.org>
To:        Lars Engels <lars.engels@0x20.net>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Kernel Panic
Message-ID:  <20060612194541.L34121@fledge.watson.org>
In-Reply-To: <20060612182404.GC46563@e.0x20.net>
References:  <20060612182404.GC46563@e.0x20.net>

next in thread | previous in thread | raw e-mail | index | archive | help

On Mon, 12 Jun 2006, Lars Engels wrote:

> During the last weeks I am getting sporadic kernel panics. It seems that 
> they only occur when I am using X. I didn't get any when I was on the 
> console.
>
> I attached the kgdb output and can give additional information when it's 
> needed.
>
> Thanks in advance,

Lars,

It looks like there is a problem with the stack trace from kgdb.  Is there any 
chance your kernel and kernel.debug are out of sync?

> Fatal trap 18: integer divide fault while in kernel mode
> instruction pointer     = 0x20:0xc0a480a9
> stack pointer           = 0x28:0xe39e9b00
> frame pointer           = 0x28:0xe39e9b44
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, def32 1, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 8029 (sysctl)
> trap number             = 18
> panic: integer divide fault
> Uptime: 3m13s
> Physical memory: 1006 MB

Does this box have a serial port?  If so, you might want to try setting up a 
serial console for it with a null modem cable to an adjacent box.  DDB may be 
able to get a more reliable stack trace than the kernel dump.  Looks like a 
bug in some or another sysctl handler -- a stack trace from DDB may be 
sufficient to debug it without a working core.

Robert N M Watson
Computer Laboratory
Universty of Cambridge



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060612194541.L34121>