ata panic

[Mike Tancsa]

At 01:37 AM 14/03/2006, Søren Schmidt wrote:
>Mike Tancsa wrote:
>>At 11:38 PM 13/03/2006, Mike Tancsa wrote:
>>>Hi,
>>>I was trying out a recent RELENG_6 on a VIA 
>>>mini ITX board with built in CF reader. If a 
>>>CF is present, the box panics at boot (tried 
>>>with 2 separate boards and different CFs just 
>>>in case it was hardware).  This is with a RELENG_6 from March 7th
>>>
>>>
>>>with the flash in I get a panic at bootup.
>>Just updated the source to the latest RELENG_6 
>>in case the changes fixed it, but no dice
>
>Hmm, thats not the intended behavior :)
>Thanks for the report, I'll look into this ASAP!

Thanks!  I also just confirmed a kernel from Feb 
1 boots up OK, but not with boot -v ??

eg here is a regular boot from the Feb 1 kernel

WARNING: WITNESS option enabled, expect reduced performance.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: VIA C3 Nehemiah+RNG+ACE (796.77-MHz 686-class CPU)
atapci0: <VIA 6420 SATA150 controller> port 
0xeb00-0xeb07,0xe000-0xe003,0xe100-0xe107,0xe200-0xe203,0xe300-0xe30f,0xd400-0xd4ff 
irq 10 at device 15.0 on pci0
ata2: <ATA channel 0> on atapci0
ata3: <ATA channel 1> on atapci0
atapci1: <VIA 8237 UDMA133 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe500-0xe50f at device 15.1 on pci0
ata0: <ATA channel 0> on atapci1
ata1: <ATA channel 1> on atapci1
Timecounters tick every 1.000 msec
Fast IPsec: Initialized Security Association Processing.
ad0: 38166MB <Seagate ST340014A 8.54> at ata0-master UDMA100
ad2: 244MB <SanDisk SDCFB-256 Rev 0.00> at ata1-master PIO4
Trying to mount root from ufs:/dev/ad0s1a

where as boot -v gives

ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire
ad0: setting PIO4 on 8237 chip
ad0: setting UDMA100 on 8237 chip
ad0: 38166MB <Seagate ST340014A 8.54> at ata0-master UDMA100
ad0: 78165360 sectors [77545C/16H/63S] 16 sectors/interrupt 1 depth queue
ata1-master: pio=PIO4 wdma=UNSUPPORTED udma=UNSUPPORTED cable=40 wire
ad2: setting PIO4 on 8237 chip
ad2: 244MB <SanDisk SDCFB-256 Rev 0.00> at ata1-master PIO4


Fatal trap 18: integer divide fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer     = 0x20:0xc06d7637
stack pointer           = 0x28:0xc0c20b64
frame pointer           = 0x28:0xc0c20bec
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         = 0 (swapper)
[thread pid 0 tid 0 ]
Stopped at      __qdivrem+0x3b: divl    %ecx,%eax
db>

db> bt
Tracing pid 0 tid 0 td 0xc078dac0
__qdivrem(7a2b0,0,0,0,0) at __qdivrem+0x3b
__udivdi3(7a2b0,0,0,0) at __udivdi3+0x16
ad_describe(c339f700,c339f700,c32df3a0,c33bd800,c31a3600) at ad_describe+0x1b3
ad_attach(c339f700) at ad_attach+0x1e7
device_attach(c339f700,c0c20d28,c339f700,0,c33bd800) at device_attach+0x58
device_probe_and_attach(c339f700) at device_probe_and_attach+0xe0
bus_generic_attach(c328b280,c328b280,ffffffff,2,c339f700) 
at bus_generic_attach+0x16
ata_identify(c328b280) at ata_identify+0x1c8
ata_boot_attach(0) at ata_boot_attach+0x3e
run_interrupt_driven_config_hooks(0,c1ec00,c1e000,0,c043b215) 
at run_interrupt_driven_config_hooks+0x18
mi_startup() at mi_startup+0x96
begin() at begin+0x2c
db>
Tracing pid 0 tid 0 td 0xc078dac0
__qdivrem(7a2b0,0,0,0,0) at __qdivrem+0x3b
__udivdi3(7a2b0,0,0,0) at __udivdi3+0x16
ad_describe(c339f700,c339f700,c32df3a0,c33bd800,c31a3600) at ad_describe+0x1b3
ad_attach(c339f700) at ad_attach+0x1e7
device_attach(c339f700,c0c20d28,c339f700,0,c33bd800) at device_attach+0x58
device_probe_and_attach(c339f700) at device_probe_and_attach+0xe0
bus_generic_attach(c328b280,c328b280,ffffffff,2,c339f700) 
at bus_generic_attach+0x16
ata_identify(c328b280) at ata_identify+0x1c8
ata_boot_attach(0) at ata_boot_attach+0x3e
run_interrupt_driven_config_hooks(0,c1ec00,c1e000,0,c043b215) 
at run_interrupt_driven_config_hooks+0x18
mi_startup() at mi_startup+0x96
begin() at begin+0x2c
db>