ATAPI devices in AHCI mode not working

ATAPI devices in AHCI mode not working

[Gaston, Jason D]

Hello,

On a Tolapai 2 port SATA controller, I am not able to mount ATAPI
drives.  The device shows up in /sys/block, but does not show up in
/proc/sxx. I am getting the following messages in dmesg.  ata1 is the
DVD drive.

Any ideas what the problem is?

Thanks,

Jason


...
libata version 3.00 loaded.
ahci 0000:00:1f.2: version 3.0
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA
mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf ilck stag pm led clo pio slum
part 
PCI: Setting latency timer of device 0000:00:1f.2 to 64
scsi0 : ahci
scsi1 : ahci
ata1: SATA max UDMA/133 abar m1024@0xd9101000 port 0xd9101100 irq 216
ata2: SATA max UDMA/133 abar m1024@0xd9101000 port 0xd9101180 irq 216
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATAPI: TSSTcorpCD/DVDW SH-S183L, SB01, max UDMA/33, ATAPI AN
ata1.00: applying bridge limits
ata1.00: configured for UDMA/33
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-7: WDC WD1600JS-61MHB1, 10.02E01, max UDMA/133
ata2.00: 312581808 sectors, multi 0: LBA48 
ata2.00: configured for UDMA/133
scsi 0:0:0:0: CD-ROM            TSSTcorp CD/DVDW SH-S183L SB01 PQ: 0
ANSI: 5
scsi 1:0:0:0: Direct-Access     ATA      WDC WD1600JS-61M 10.0 PQ: 0
ANSI: 5
sd 1:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 1:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
 sda: sda1 sda2
sd 1:0:0:0: [sda] Attached SCSI disk
sr 0:0:0:0: Attached scsi generic sg0 type 5
sd 1:0:0:0: Attached scsi generic sg1 type 0
ACPI: Processor [CPU1] (supports 8 throttling states)
BIOS EDD facility v0.16 2004-Jun-25, 6 devices found
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/33
ata1: EH complete
sr0: scsi3-mmc drive: 32x/40x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1: SATA link down (SStatus 11 SControl 300)
ata1: failed to recover some devices, retrying in 5 secs
ata1: hard resetting link
ata1: SATA link down (SStatus 0 SControl 300)
ata1: limiting SATA link speed to 1.5 Gbps
ata1.00: limiting speed to UDMA/33:PIO3
ata1: failed to recover some devices, retrying in 5 secs
ReiserFS: sda2: found reiserfs format "3.6" with standard journal
ReiserFS: sda2: using ordered data mode
ReiserFS: sda2: journal params: device sda2, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: sda2: checking transaction log (sda2)
ReiserFS: sda2: Using r5 hash to sort names
ata1: hard resetting link
ata1: SATA link down (SStatus 0 SControl 310)
ata1.00: disabled
ata1: EH complete
sr 0:0:0:0: rejecting I/O to offline device
sr 0:0:0:0: rejecting I/O to offline device
ata1.00: detaching (SCSI 0:0:0:0)
Adding 2104472k swap on
/dev/disk/by-id/scsi-SATA_WDC_WD1600JS-61_WD-WCANMC345198-part1.
Priority:-1 extents:1 across:2104472k
...

Re: ATAPI devices in AHCI mode not working

[Alan Cox]

> ata1.00: ATAPI: TSSTcorpCD/DVDW SH-S183L, SB01, max UDMA/33, ATAPI AN

Everyones favourite vendor right now

> ata1.00: applying bridge limits
> ata1.00: configured for UDMA/33

It seems to be seeing a SATA/PATA bridge here ? This is a PATA device on
a SATA bridge ? If not something is very very broken as we are seeing a
SATA cable type and a device not indentifying itself as SATA.

> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
>          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
> ata1.00: status: { DRDY }

We try and talk to it, it ends up stuck busy.

> ata1: soft resetting link
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/33
> ata1: EH complete

Kick it, back it comes
> sr0: scsi3-mmc drive: 32x/40x writer dvd-ram cd/rw xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.20
> sr 0:0:0:0: Attached scsi CD-ROM sr0

Fails again
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
>          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
> ata1.00: status: { DRDY }
> ata1: soft resetting link

Repeat

> ata1: SATA link down (SStatus 11 SControl 300)
> ata1: failed to recover some devices, retrying in 5 secs
> ata1: hard resetting link
> ata1: SATA link down (SStatus 0 SControl 300)
> ata1: limiting SATA link speed to 1.5 Gbps

Try again at 1.5Gbit

> ata1: hard resetting link
> ata1: SATA link down (SStatus 0 SControl 310)
> ata1.00: disabled
> ata1: EH complete

We give up on it.


First guess would be to replace the TSST drive with another vendors
device and see what occurs. If that does the same thing it eliminates
drive firmware.

If that doesn't help then need to know more about the bridge etc


Alan

RE: ATAPI devices in AHCI mode not working

[Gaston, Jason D]

>-----Original Message-----
>From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
>Sent: Monday, October 29, 2007 1:30 PM
>To: Gaston, Jason D
>Cc: linux-ide@vger.kernel.org
>Subject: Re: ATAPI devices in AHCI mode not working
>
>> ata1.00: ATAPI: TSSTcorpCD/DVDW SH-S183L, SB01, max UDMA/33, ATAPI AN
>
>Everyones favourite vendor right now
>
>> ata1.00: applying bridge limits
>> ata1.00: configured for UDMA/33
>
>It seems to be seeing a SATA/PATA bridge here ? This is a PATA device
on
>a SATA bridge ? If not something is very very broken as we are seeing a
>SATA cable type and a device not indentifying itself as SATA.
>
>> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
>> ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0
>>          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
>> ata1.00: status: { DRDY }
>
>We try and talk to it, it ends up stuck busy.
>
>> ata1: soft resetting link
>> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>> ata1.00: configured for UDMA/33
>> ata1: EH complete
>
>Kick it, back it comes
>> sr0: scsi3-mmc drive: 32x/40x writer dvd-ram cd/rw xa/form2 cdda tray
>> Uniform CD-ROM driver Revision: 3.20
>> sr 0:0:0:0: Attached scsi CD-ROM sr0
>
>Fails again
>> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
>> ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0
>>          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
>> ata1.00: status: { DRDY }
>> ata1: soft resetting link
>
>Repeat
>
>> ata1: SATA link down (SStatus 11 SControl 300)
>> ata1: failed to recover some devices, retrying in 5 secs
>> ata1: hard resetting link
>> ata1: SATA link down (SStatus 0 SControl 300)
>> ata1: limiting SATA link speed to 1.5 Gbps
>
>Try again at 1.5Gbit
>
>> ata1: hard resetting link
>> ata1: SATA link down (SStatus 0 SControl 310)
>> ata1.00: disabled
>> ata1: EH complete
>
>We give up on it.
>
>
>First guess would be to replace the TSST drive with another vendors
>device and see what occurs. If that does the same thing it eliminates
>drive firmware.
>
>If that doesn't help then need to know more about the bridge etc
>
>
>Alan

I have tried a Plextor and a couple of Lite-On DVD drives with the same
behavior.  Dmesg below for the Lite-On using the 2.6.24-rc1 kernel.  The
other weird thing, is that when the ATAPI drive is attached and I am
seeing this issue, USB also does not work (USB mice and flashdrives).
If I reboot with the ATAPI drive disconnected then the USB device work
fine.  What other information can I give you?

Thanks,

Jason

...
libata version 3.00 loaded.
ahci 0000:00:1f.2: version 3.0
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA
mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf ilck stag pm led clo pio slum
part 
PCI: Setting latency timer of device 0000:00:1f.2 to 64
scsi0 : ahci
scsi1 : ahci
ata1: SATA max UDMA/133 abar m1024@0xd9101000 port 0xd9101100 irq 216
ata2: SATA max UDMA/133 abar m1024@0xd9101000 port 0xd9101180 irq 216
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATAPI: ATAPI   DVD D  DH16D2S, EP52, max UDMA/100
ata1.00: configured for UDMA/100
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-7: WDC WD1600JS-61MHB1, 10.02E01, max UDMA/133
ata2.00: 312581808 sectors, multi 0: LBA48 
ata2.00: configured for UDMA/133
scsi 0:0:0:0: CD-ROM            ATAPI    DVD D  DH16D2S   EP52 PQ: 0
ANSI: 5
scsi 1:0:0:0: Direct-Access     ATA      WDC WD1600JS-61M 10.0 PQ: 0
ANSI: 5
sd 1:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 1:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
 sda: sda1 sda2
sd 1:0:0:0: [sda] Attached SCSI disk
sr 0:0:0:0: Attached scsi generic sg0 type 5
sd 1:0:0:0: Attached scsi generic sg1 type 0
ACPI: Processor [CPU1] (supports 8 throttling states)
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/100
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/100
ata1: EH complete
ReiserFS: sda2: found reiserfs format "3.6" with standard journal
ReiserFS: sda2: using ordered data mode
ReiserFS: sda2: journal params: device sda2, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: sda2: checking transaction log (sda2)
ReiserFS: sda2: Using r5 hash to sort names
Adding 2104472k swap on
/dev/disk/by-id/scsi-SATA_WDC_WD1600JS-61_WD-WCANMC345198-part1.
Priority:-1 extents:1 across:2104472k
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/100
ata1: EH complete
ata1: limiting SATA link speed to 1.5 Gbps
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: port is slow to respond, please be patient (Status 0x80)
ata1: COMRESET failed (errno=-16)
ata1: hard resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/100
ata1: EH complete
loop: module loaded
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ip6_tables: (C) 2000-2006 Netfilter Core Team
ip_tables: (C) 2000-2006 Netfilter Core Team
input: Power Button (FF) as /class/input/input3
ACPI: Power Button (FF) [PWRF]
input: Sleep Button (CM) as /class/input/input4
ACPI: Sleep Button (CM) [SLPB]
input: Power Button (CM) as /class/input/input5
ACPI: Power Button (CM) [PWRB]
BIOS EDD facility v0.16 2004-Jun-25, 6 devices found
audit(1192800900.159:2): audit_pid=1702 old=0 by auid=4294967295
powernow: This module only works with AMD K7 CPUs
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd a0/01:00:00:80:00/00:00:00:00:00/a0 tag 0 cdb 0x5a data 128
in
         res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/100
ata1: EH complete
sr0: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0

Re: ATAPI devices in AHCI mode not working

[Alan Cox]

> ata1: SATA max UDMA/133 abar m1024@0xd9101000 port 0xd9101100 irq 216
> ata2: SATA max UDMA/133 abar m1024@0xd9101000 port 0xd9101180 irq 216
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: ATAPI: ATAPI   DVD D  DH16D2S, EP52, max UDMA/100
> ata1.00: configured for UDMA/100

Much better - no misdetected link type, no device claiming to be PATA
when its SATA.


Right that eliminates all the obvious goings on being caused by broken
devices which is a start. Doesn't shed any light on the rest of it. What
happens if you boot with irqpoll enabled ? (wondering if the timeouts are
ACPI or IRQ routing stuff)

RE: ATAPI devices in AHCI mode not working

[Gaston, Jason D]

>-----Original Message-----
>From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
>Sent: Monday, October 29, 2007 3:14 PM
>To: Gaston, Jason D
>Cc: linux-ide@vger.kernel.org
>Subject: Re: ATAPI devices in AHCI mode not working
>
>> ata1: SATA max UDMA/133 abar m1024@0xd9101000 port 0xd9101100 irq 216
>> ata2: SATA max UDMA/133 abar m1024@0xd9101000 port 0xd9101180 irq 216
>> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>> ata1.00: ATAPI: ATAPI   DVD D  DH16D2S, EP52, max UDMA/100
>> ata1.00: configured for UDMA/100
>
>Much better - no misdetected link type, no device claiming to be PATA
>when its SATA.
>
>
>Right that eliminates all the obvious goings on being caused by broken
>devices which is a start. Doesn't shed any light on the rest of it.
What
>happens if you boot with irqpoll enabled ? (wondering if the timeouts
are
>ACPI or IRQ routing stuff)

I rebuilt the kernel; the DVD and USB devices are functional now. I'm
not sure what the problem was before.  On a side note: In 2.6.24.rc1 the
DVD starts working right away, but on a SLES10_SP1 kernel, it takes some
time for it to step down to a PIO mode before the DVD can be mounted.
Oh well.

Thanks!

Jason

Re: ATAPI devices in AHCI mode not working

[Tejun Heo]

[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]

Gaston, Jason D wrote:
>> -----Original Message-----
>> From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
>> Sent: Monday, October 29, 2007 3:14 PM
>> To: Gaston, Jason D
>> Cc: linux-ide@vger.kernel.org
>> Subject: Re: ATAPI devices in AHCI mode not working
>>
>>> ata1: SATA max UDMA/133 abar m1024@0xd9101000 port 0xd9101100 irq 216
>>> ata2: SATA max UDMA/133 abar m1024@0xd9101000 port 0xd9101180 irq 216
>>> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>>> ata1.00: ATAPI: ATAPI   DVD D  DH16D2S, EP52, max UDMA/100
>>> ata1.00: configured for UDMA/100
>> Much better - no misdetected link type, no device claiming to be PATA
>> when its SATA.
>>
>>
>> Right that eliminates all the obvious goings on being caused by broken
>> devices which is a start. Doesn't shed any light on the rest of it.
> What
>> happens if you boot with irqpoll enabled ? (wondering if the timeouts
> are
>> ACPI or IRQ routing stuff)
> 
> I rebuilt the kernel; the DVD and USB devices are functional now. I'm
> not sure what the problem was before.  On a side note: In 2.6.24.rc1 the
> DVD starts working right away, but on a SLES10_SP1 kernel, it takes some
> time for it to step down to a PIO mode before the DVD can be mounted.
> Oh well.

Yeah, there has been quite some update in libata between SLES10_SP1 and
2.6.24-rc1.  The controller being ahci, I wonder whether this is caused
by the different in check_atapi_dma().

1. Does other optical drives have the same problem?  If not, please post
the result of "hdparm -I /dev/sr0" with the problematic one attached.

2. If you apply the attached patch to 2.6.24-rc1, does it behave the
same as the SLES10SP1 kernel?

-- 
tejun

[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 529 bytes --]

diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 8ee56e5..5d9b193 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -4491,11 +4491,13 @@ int ata_check_atapi_dma(struct ata_queued_cmd *qc)
 {
 	struct ata_port *ap = qc->ap;
 
+#if 0
 	/* Don't allow DMA if it isn't multiple of 16 bytes.  Quite a
 	 * few ATAPI devices choke on such DMA requests.
 	 */
 	if (unlikely(qc->nbytes & 15))
 		return 1;
+#endif
 
 	if (ap->ops->check_atapi_dma)
 		return ap->ops->check_atapi_dma(qc);

RE: ATAPI devices in AHCI mode not working

[Gaston, Jason D]

>-----Original Message-----
>From: linux-ide-owner@vger.kernel.org [mailto:linux-ide-
>owner@vger.kernel.org] On Behalf Of Tejun Heo
>Sent: Wednesday, October 31, 2007 1:07 AM
>To: Gaston, Jason D
>Cc: Alan Cox; linux-ide@vger.kernel.org
>Subject: Re: ATAPI devices in AHCI mode not working
>
>Gaston, Jason D wrote:
>>> -----Original Message-----
>>> From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
>>> Sent: Monday, October 29, 2007 3:14 PM
>>> To: Gaston, Jason D
>>> Cc: linux-ide@vger.kernel.org
>>> Subject: Re: ATAPI devices in AHCI mode not working
>>>
>>>> ata1: SATA max UDMA/133 abar m1024@0xd9101000 port 0xd9101100 irq
216
>>>> ata2: SATA max UDMA/133 abar m1024@0xd9101000 port 0xd9101180 irq
216
>>>> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>>>> ata1.00: ATAPI: ATAPI   DVD D  DH16D2S, EP52, max UDMA/100
>>>> ata1.00: configured for UDMA/100
>>> Much better - no misdetected link type, no device claiming to be
PATA
>>> when its SATA.
>>>
>>>
>>> Right that eliminates all the obvious goings on being caused by
broken
>>> devices which is a start. Doesn't shed any light on the rest of it.
>> What
>>> happens if you boot with irqpoll enabled ? (wondering if the
timeouts
>> are
>>> ACPI or IRQ routing stuff)
>>
>> I rebuilt the kernel; the DVD and USB devices are functional now. I'm
>> not sure what the problem was before.  On a side note: In 2.6.24.rc1
the
>> DVD starts working right away, but on a SLES10_SP1 kernel, it takes
some
>> time for it to step down to a PIO mode before the DVD can be mounted.
>> Oh well.
>
>Yeah, there has been quite some update in libata between SLES10_SP1 and
>2.6.24-rc1.  The controller being ahci, I wonder whether this is caused
>by the different in check_atapi_dma().
>
>1. Does other optical drives have the same problem?  If not, please
post
>the result of "hdparm -I /dev/sr0" with the problematic one attached.
>
>2. If you apply the attached patch to 2.6.24-rc1, does it behave the
>same as the SLES10SP1 kernel?
>
>--
>Tejun

All of the ATAPI drives seem to have the issue of taking a while to slow
down and start working.  I will try the patch and see what happens.  I
will also get the hdparm info from all of the drives I am using to see
if something stands out.

Thanks,

Jason
 

RE: ATAPI devices in AHCI mode not working

[Gaston, Jason D]

[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]

>>Yeah, there has been quite some update in libata between SLES10_SP1
and
>>2.6.24-rc1.  The controller being ahci, I wonder whether this is
caused
>>by the different in check_atapi_dma().
>>
>>1. Does other optical drives have the same problem?  If not, please
>post
>>the result of "hdparm -I /dev/sr0" with the problematic one attached.
>>
>>2. If you apply the attached patch to 2.6.24-rc1, does it behave the
>>same as the SLES10SP1 kernel?
>>
>>--
>>Tejun
>
>All of the ATAPI drives seem to have the issue of taking a while to
slow
>down and start working.  I will try the patch and see what happens.  I
>will also get the hdparm info from all of the drives I am using to see
>if something stands out.
>
>Thanks,
>
>Jason

Tejun,

Attached are the hdparm -I /dev/cdrom results for the three other drives
I am using.  These do not include the original drive that had the major
issues on, TSSTcorpCD/DVDW SH-S183L.

Applying the patch to the 2.6.24-rc kernel did not cause the same
behavior, which I am seeing with older kernels.  Instead, everything
seemed to be fine until I tried to automount the drive, which said that
there was no media.  I was however, able to manually mount the drive.

Thanks,

Jason


[-- Attachment #2: hdparm_cdrom --]
[-- Type: application/octet-stream, Size: 2266 bytes --]


/dev/cdrom:

ATAPI CD-ROM, with removable media
	Model Number:       ATAPI   DVD D  DH16D2S                  
	Serial Number:      
	Firmware Revision:  EP52    
Standards:
	Used: ATAPI for CD-ROMs, SFF-8020i, r2.5
	Supported: CD-ROM ATAPI-3 -4 -5 -6 
Configuration:
	DRQ response: 50us.
	Packet size: 12 bytes
Capabilities:
	LBA, IORDY(can be disabled)
	DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 
	     Cycle time: min=120ns recommended=120ns
	PIO: pio0 pio1 pio2 pio3 pio4 
	     Cycle time: no flow control=383ns  IORDY flow control=120ns
Commands/features:
	Enabled	Supported:
	    	PACKET command feature set
	    	DEVICE_RESET command
	   *	Mandatory FLUSH_CACHE
	   *	SATA-I signaling speed (1.5Gb/s)
	   *	Software settings preservation

/dev/cdrom:

ATAPI CD-ROM, with removable media
	Model Number:       LITE-ON DVDRW LH-20A1S                  
	Serial Number:      
	Firmware Revision:  9L08    
Standards:
	Used: ATAPI for CD-ROMs, SFF-8020i, r2.5
	Supported: CD-ROM ATAPI-2 
Configuration:
	DRQ response: 50us.
	Packet size: 12 bytes
Capabilities:
	LBA, IORDY(can be disabled)
	DMA: *sdma0 *sdma1 *sdma2 sdma3 sdma4 sdma7 mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 (?)
	     Cycle time: min=120ns recommended=120ns
	PIO: pio0 pio1 pio2 pio3 pio4 
	     Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
	Enabled	Supported:
	   *	PACKET command feature set
	   *	DEVICE_RESET command
	   *	Mandatory FLUSH_CACHE
	   *	SATA-I signaling speed (1.5Gb/s)
	   *	Host-initiated interface power management
	   *	Phy event counters
	    	Device-initiated interface power management
	   *	unknown 78[5]
	   *	Software settings preservation

/dev/cdrom:

ATAPI CD-ROM, with removable media
	Model Number:       PLEXTOR DVDR   PX-716A                  
	Serial Number:      171956
	Firmware Revision:  1.08    
Standards:
	Likely used CD-ROM ATAPI-1
Configuration:
	DRQ response: 50us.
	Packet size: 12 bytes
Capabilities:
	LBA, IORDY(can be disabled)
	DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 *udma3 udma4 
	     Cycle time: min=120ns recommended=120ns
	PIO: pio0 pio1 pio2 pio3 pio4 
	     Cycle time: no flow control=120ns  IORDY flow control=120ns
HW reset results:
	CBLID- below Vih
	Device num = 0

Re: ATAPI devices in AHCI mode not working

[Tejun Heo]

Hello,

Gaston, Jason D wrote:
> Attached are the hdparm -I /dev/cdrom results for the three other drives
> I am using.  These do not include the original drive that had the major
> issues on, TSSTcorpCD/DVDW SH-S183L.
> 
> Applying the patch to the 2.6.24-rc kernel did not cause the same
> behavior, which I am seeing with older kernels.  Instead, everything
> seemed to be fine until I tried to automount the drive, which said that
> there was no media.  I was however, able to manually mount the drive.

Thanks.  Yeah, libata in SLE10SP1 can be considered ancient considering
the speed libata code has been evolving.  Please file a bug report in
bugzilla.novell.com and assign it to teheo@novell.com.  Eeeek... /me
hates vendor kernels.  :-)

Thanks.

-- 
tejun