DragonFly bugs List (threaded) for 2009-06
DragonFly BSD
DragonFly bugs List (threaded) for 2009-06
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: ahci: attachment to atapi device


From: Francois Tigeot <ftigeot@xxxxxxxxxxxx>
Date: Mon, 15 Jun 2009 23:06:13 +0200

On Mon, Jun 15, 2009 at 09:31:09AM -0700, Matthew Dillon wrote:
> 
> :    I'm not sure what is going on there but get the latest git and try
> :    again.  It will be less verbose and shouldn't try to double-ident
> :    ahci0.0.  I'm hoping that is the cause of the forever-repeating
> :    timeouts.

I just booted a fresh kernel. cd0 still attachs to ahci:

ahci0.0: Found DISK "WDC WD4000YS-01MPB1 09.02E09" serial=" WD-WCANU2073446"
ahci0.0: tags=32/32 satacap=0706 satafea=0044 NCQ=YES capacity=381554.08MB
ahci0.1: Found ATAPI "ASUS    DRW-1814BLT 1.04    " serial="                 "
ahci0.1: tags=0/32 satacap=602 satafea=0028 NCQ=NO capacity=0.00MB
ahci0.2: No device detected
ahci0.3: Found disk "WDC WD5002ABYS-01B1B0 02.03B02" serial=" WD-WCASY3848290"
ahci0.3: tags=32/32 satacap0506 satafea=0044 NCQ=YES capacity=476940.02MB"
[...]
mountroot> ufs:da0s1a
Mounting root from ufs:da0s1a
cd0 at ahci0 bus 1 target 0 lun 0
cd0: <ASUS DRW-1814BLT 1.04> Removable CD-ROM SCSI-0 device
cd0: 150.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed
ahci0.0: CMD TIMEOUT state=5 slot=22
        cmd-reg 0x4d617<HPcP,CR,FR,FRE,POD,SUD,ST>
        sactive=004000000 active=00000000 expired=00000000
           sact=000000000     ci=00000000
ahci0.0: disk_rw: timeout

[timeout loop]


I then tried again after unpluging the burner:

atapci0: <Intel ICH7 UDMA100 controller> port 0x30b0-0x30bf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 10 at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
match generic sata
match generic sata
ahci0: <AHCI-PCI-SATA> port 0x30a0-0x30af,0x30e0-0x30e3,0x30c0-0x30c7,0x30e4-0x30e7,0x30c8-0x30cf mem 0xd2204000-0xd22043ff irq 9 at device 31.2 on pci0
match generic sata
ahci0: AHCI 1.1 capabilities 0xc320ff03<S64A,NCQ,SAL,SCLO,PMD,SSC,PSC>, 4 ports, 32 tags/port, gen 1 (1.5Gbps) and 2 (3Gbps)
ahci0.1: No device detected
ahci0: Found DISK "WDC WD4000YS-01MPB1 09.02E09" serial="     WD-WCANU2073446"
ahci0.0: tags=32/32 satacap=0706 satafea=0044 NCQ=YES capacity=381554.08MB
ahci0.1: Found ATAPI "ASUS    DRW-1814BLT 1.04    " serial="                 "
ahci0.1: tags=0/32 satacap=602 satafea=0028 NCQ=NO capacity=0.00MB
ahci0.2: No device detected
ahci0.3: Found disk "WDC WD5002ABYS-01B1B0 02.03B02" serial=" WD-WCASY3848290"
ahci0.3: tags=32/32 satacap0506 satafea=0044 NCQ=YES capacity=476940.02MB"
[...]
da0 at ahci0 bus 0 target 0 lun 0
da0: <SATA WDC WD4000YS-01M 09.0> Fixed Direct Access SCSI-4 device
da0: 300.000MB/s transfers
da0: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C)
da1 at ahci0 bus 3 target 0 lun 0
da1: <SATA WDC WD5002ABYS-0 02.0> Fixed Direct Access SCSI-4 device
da1: 300.000MB/s transfers
da1: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C)
[...]
mountroot> ufs:da0s1a
Mounting root from ufs:da0s1a
cd0 at ahci0 bus 1 target 0 lun 0
cd0: <ASUS DRW-1814BLT 1.04> Removable CD-ROM SCSI-0 device
cd0: 150.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray
closed
ahci0.0: CMD TIMEOUT state=5 slot=22
        cmd-reg 0x4d617<HPcP,CR,FR,FRE,POD,SUD,ST>
        sactive=004000000 active=00000000 expired=00000000
           sact=000000000     ci=00000000
ahci0.0: disk_rw: timeout

The CMD TIMEOUT lines repeat a few times, the "slot=" part going from 22 to 26

It ends with these two lines:
da0: reading primary partition table: error accessing offset 000000000000 for 512
Root mount failed: 5


>     I'm going to assume those last two tags=/f86= where actually from
>     the other disk and you mis-typed them.

It's quite possible. As you guessed, the entire dmesg was hand-typed.

>     If that's the case it might be an issue of the drive or the controller
>     not being able to support SATA-300.  It may help if you post what the
>     NATA driver reports for those attachments (set hint.ahic.disabled from
>     the boot loader).

Here you go:

atapci0: <Intel ICH7 UDMA100 controller> port 0x30b0-0x30bf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 10 at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
atapci1: <Intel AHCI controller> port 0x30a0-0x30af,0x30e0-0x30e3,0x30c0-0x30c7,0x30e4-0x30e7,0x30c8-0x30cf mem 0xd2204000-0xd22043ff irq 9 at device 31.2 on pci0
atapci1: AHCI Version 01.10 controller with 4 ports detected
ata2: <ATA channel 0> on atapci1
intr 9 at 40001/40000 hz, livelocked limit engaged!
ad4: 381554MB <WDC WD4000YS-01MPB1 09.02E09> at ata2-master SATA300
ata3: <ATA channel 1> on atapci1
ata4: <ATA channel 2> on atapci1
ata5: <ATA channel 3> on atapci1
ad10: 476940MB <WDC WD5002ABYS-01B1B0 02.03B02> at ata5-master SATA300

[...]

Mounting root from ufs:/dev/ad4s1a

-- 
Francois Tigeot



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]