Re: NATA update

["Thomas E. Spanjaard" <tgen@xxxxxxxxxxxxx>]

YONETANI Tomokazu wrote:
> On Tue, Dec 05, 2006 at 11:29:44PM +0000, Thomas E. Spanjaard wrote:
> I got a panic:
>   panic: spin_lock: 0xc240ba6c, indefinite wait!
>
> and the backtrace:
>   exponential_backoff(c04eec44) at exponential_backoff+0xa2
>   spin_lock_wr_contested(c240ba6c,80000000) at spin_lock_wr_contested+0x74
>   ata_completed(c240ba20,0,c40dea8,c029f038,c028e420) at ata_completed+0xc53c
>   ata_queue_requst(c240ba20,c,0,cc40d488,cc40dea8) at ata_queue_requst+0x286
>   ata_contolcmd(cc40dea8) ata acd_attach+0xc1
>   device_prove_and_attach(cc40dea8) at device_prove_and_attach+0x15b
>   bus_generic_attach(cc40d488,cc40d488,ffffffff,ffffffff,0) at bus_generic_attach+0x14
>   ata_identify(cc40d488) at ata_identify+0x1bb
>   ata_boot_attach(0) at ata_boot_attach+0x2a
>   run_interrupt_driven_config_hooks(0,4ebc00,4f9000,0,c012b29c) at run_interrupt_driven_config_hooks+0x18
>   mi_startup(4eb000,ff800000,c02e02c0,c04ee9e0,c04ee9e0) at mi_startup+0x93
>   begin() at begin+0x43

Hmm, I think I'll have to repeat that here on the new dualcore I have now.

> Other interesting boot messages before the panic are:
>
> 		:
>   ad2: setting PIO4 on M5229 chip
>   ad2: setting UDMA100 on M5229 chip
>   ad2: 57241MB <Seagate ST306615A 3.33> at ata0-slave UDMA100
>   ad2: 117231408 sectors [116301C/16H/63S] 16 sectors/interrupt 1 depth queue
>   ata1-slave: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=80 wire
>   acd0: setting PIO4 on M5229 chip
> (several seconds here)
>   acd0: WARNING - DEVICE_RESET taskqueue timeout - completing request directly
>   spin_lock: 0xc240ba6c, indefinite wait!
>   spin_lock: 0xc240ba6c, indefinite wait!

I suspect I'm not dropping a lock somewhere; I'll investigate tomorrow.

> nata* drivers are compiled in an SMP kernel, running on Athlon64X2
> with ASRock 939Dual-SATA2 .  If I yank off the DVD-ROM drive from the
> system, it proceeds to mount root fs, then failed:
>
>   Mounting root from ufs:/dev/ad0s1h
>   no such device 'ad'

Not sure why this is happening; I use the same major as the old code, 
and afaict the same minors as well. It works when not doing a rootmount, 
I'll have to see what game the delayed attach intrhook is playing here.

> Although this mother board has a SATA port, the IDE drives are PATA one
> and connected to the PATA ports.  Another machine whose root fs is on
> a SCSI drive booted without a problem.

I'll try to reproduce everything tomorrow, I have some wine and BSG 3x10 
waiting for me :). Thanks for testing so far!

Cheers,
--
        Thomas E. Spanjaard
        tgen@netphreax.net

Attachment: signature.asc
Description: OpenPGP digital signature