Date: Sun, 8 Oct 2006 18:32:52 +0200 From: Stefan Bethke <stb@lassitu.de> To: Benjamin Lutz <mail@maxlor.com> Cc: freebsd-stable@freebsd.org Subject: Re: Kernel panic on boot (how to debug?) Message-ID: <9BFB7742-7064-49DB-BD1A-45512CF37F06@lassitu.de> In-Reply-To: <200609212301.24257.mail@maxlor.com> References: <200609192217.44712.mail@maxlor.com> <200609212301.24257.mail@maxlor.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 21.09.2006 um 23:01 schrieb Benjamin Lutz: > By sheer luck I figured out how to get into DDB though :), so I can > now > provide a backtrace. > > Fatal trap 18: integer divide fault while in kernel mode ... > --- trap 0x12, rip = 0xffffffff801c02d5, rsp = > 0xffffffff80864a80, rbp = > 0xffffffff80864ad0 --- > ata_raid_promise_read_meta() at ata_raid_promise_read_meta+0x95 > ata_raid_read_metadata() at ata_raid_read_metadata+0x2f4 Reading through ata_raid_promise_read_meta(), it's not clear to me how that trap would get triggered, but you might want to boot verbose to see how far into ata_raid_promise_read_meta() it gets. It seems to me that there is something on your disk that almost looks like a RAID metadata sector, and the driver getting confused by it. Also, try not compiling ataraid into the kernel to see if that avoids the trap. HTH, Stefan -- Stefan Bethke <stb@lassitu.de> Fon +49 170 346 0140
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9BFB7742-7064-49DB-BD1A-45512CF37F06>