ad_attach panic 6.0-RELEASE AMD64
Anish Mistry
mistry.7 at osu.edu
Sat Dec 10 14:50:51 PST 2005
On Friday 02 December 2005 08:08 pm, Anish Mistry wrote:
> I'm getting the following panic after I install 6.0-RELEASE. This
> doesn't occur if I install 5.4-STABLE-SNAP009.
> Fatal trap 18: integer divide fault while in kernel mode
> instruction pointer = 0x8:0xffffffff801a447f
> stack pointer = 0x10:0xffffffff80674ae0
> frame pointer = 0x10:0xffffffff80674be0
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 0 (swapper)
> [thread pid 0 tid 0 ]
> Stopped at ad_attach+0x3ef: divq %rsi,%eax
> db> bt
> Tracing pid 0 tid 0 td 0xffffffff805845e0
> ad_attach() at ad_attach+0x3ef
> device_attach() at device_attach+0x292
> bus_generic_attach() at bus_generic_attach+0x18
> ata_identify() at ata_identify+0xe6
> ata_boot_attach() at ata_boot_attach+0x50
> run_interrupt_driven_config_hooks() at
> run_interrupt_driven_config_hooks+0x2a
> mi_startup() at mi_startup+0xc9
> btext() at btext+0x2c
>
> http://am-productions.biz/docs/kev-amd64-pciconf.txt.gz
> http://am-productions.biz/docs/kev-acpidump.txt.gz
> http://am-productions.biz/docs/kev-dmesg.txt.gz
>
I worked around the problem by removing in "device ataraid" from my
kernel for 6.0. The ataraid is disabled in the bios, but I guess
something is buggy with the disabling.
--
Anish Mistry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20051210/7627bbe6/attachment.bin
More information about the freebsd-questions
mailing list