* ATAPI question
@ 2009-02-27 23:50 Foster, Doug F
2009-02-28 3:08 ` Robert Hancock
0 siblings, 1 reply; 16+ messages in thread
From: Foster, Doug F @ 2009-02-27 23:50 UTC (permalink / raw)
To: linux-ide@vger.kernel.org; +Cc: Foster, Doug F
I'm looking at the following Bugzilla sighting: [Bug 429724] RHEL 5.4 periodic ATA error messages on Tolapai hardware.
I have reproduced the problem using these drives: Plextor models PX-712 and PX-716 and Lite On model SHD-16S1S.
It occurs in AHCI mode only, not legacy mode.
Although I am working on an EP80579, it probably occurs on any AHCI controller.
This is a snippet from dmesg:
Jan 27 13:02:52 localhost kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Jan 27 13:02:52 localhost kernel: ata2.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 8 in
Jan 27 13:02:52 localhost kernel: cdb 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 27 13:02:52 localhost kernel: res 40/00:03:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Jan 27 13:02:52 localhost kernel: ata2.00: status: { DRDY }
Jan 27 13:02:53 localhost kernel: ata2: soft resetting link
Jan 27 13:02:53 localhost kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 27 13:02:53 localhost kernel: ata2.00: configured for UDMA/25
Jan 27 13:02:53 localhost kernel: ata2: EH complete
Using a SATA analyzer, I find that on an INQUIRY (12h) ATAPI packet command, the device sets bit-6 (DRDY) and bit-4 (SERV) in the status register, and bits 0 (CoD) and 1 (IO) are set in the ATAPI Interrupt Reason Register (ATA Sector Count Register). After SERVICE is flagged by the ATAPI device (and not serviced), it doesn't respond properly from then on.
Sections 5.7, 5.7.1, and 5.17 (overlapped commands) in the ATA Packet Interface for CD-ROMs specification (ATAPI-SFF8020i.pdf) seem to apply. This functionality seems to be missing. I would like to get some guidance as to where this functionality should be added. I could either work with the appropriate maintainer on the details or take a crack at the code changes myself. It would be a good learning experience for me, but I would like to collaborate with the appropriate Linux expert.
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: ATAPI question
2009-02-27 23:50 ATAPI question Foster, Doug F
@ 2009-02-28 3:08 ` Robert Hancock
2009-03-01 12:51 ` Tejun Heo
0 siblings, 1 reply; 16+ messages in thread
From: Robert Hancock @ 2009-02-28 3:08 UTC (permalink / raw)
Cc: linux-ide@vger.kernel.org, Tejun Heo
Foster, Doug F wrote:
> I'm looking at the following Bugzilla sighting: [Bug 429724] RHEL 5.4 periodic ATA error messages on Tolapai hardware.
>
> I have reproduced the problem using these drives: Plextor models PX-712 and PX-716 and Lite On model SHD-16S1S.
> It occurs in AHCI mode only, not legacy mode.
> Although I am working on an EP80579, it probably occurs on any AHCI controller.
>
> This is a snippet from dmesg:
> Jan 27 13:02:52 localhost kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jan 27 13:02:52 localhost kernel: ata2.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 8 in
> Jan 27 13:02:52 localhost kernel: cdb 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Jan 27 13:02:52 localhost kernel: res 40/00:03:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
> Jan 27 13:02:52 localhost kernel: ata2.00: status: { DRDY }
> Jan 27 13:02:53 localhost kernel: ata2: soft resetting link
> Jan 27 13:02:53 localhost kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> Jan 27 13:02:53 localhost kernel: ata2.00: configured for UDMA/25
> Jan 27 13:02:53 localhost kernel: ata2: EH complete
>
> Using a SATA analyzer, I find that on an INQUIRY (12h) ATAPI packet command, the device sets bit-6 (DRDY) and bit-4 (SERV) in the status register, and bits 0 (CoD) and 1 (IO) are set in the ATAPI Interrupt Reason Register (ATA Sector Count Register). After SERVICE is flagged by the ATAPI device (and not serviced), it doesn't respond properly from then on.
Bit 4 isn't SERV in this context, it's DRQ. (It's only SERV when TCQ is
in use, which it isn't.) It looks like this is a READ CAPACITY command
that's being issued by PIO. DRQ means the device expects to transfer
data - either to receive the CDB or send the response. Presumably that
didn't happen for some reason. Are you sure about both the C/D and I/O
bits being 1? That would mean command transfer to the host, which
doesn't make any sense.
You're saying that DRQ never gets cleared after the INQUIRY command?
It's possible the device wanted to transfer more data than the PRD table
had room for. Not sure what AHCI ends up doing in this case. I'm CCing
Tejun who might know more..
>
> Sections 5.7, 5.7.1, and 5.17 (overlapped commands) in the ATA Packet Interface for CD-ROMs specification (ATAPI-SFF8020i.pdf) seem to apply. This functionality seems to be missing. I would like to get some guidance as to where this functionality should be added. I could either work with the appropriate maintainer on the details or take a crack at the code changes myself. It would be a good learning experience for me, but I would like to collaborate with the appropriate Linux expert.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: ATAPI question
2009-02-28 3:08 ` Robert Hancock
@ 2009-03-01 12:51 ` Tejun Heo
2009-03-02 15:58 ` Foster, Doug F
0 siblings, 1 reply; 16+ messages in thread
From: Tejun Heo @ 2009-03-01 12:51 UTC (permalink / raw)
To: Robert Hancock; +Cc: Foster, Doug F, linux-ide@vger.kernel.org
Hello,
Robert Hancock wrote:
>> Using a SATA analyzer, I find that on an INQUIRY (12h) ATAPI packet
>> command, the device sets bit-6 (DRDY) and bit-4 (SERV) in the status
>> register, and bits 0 (CoD) and 1 (IO) are set in the ATAPI Interrupt
>> Reason Register (ATA Sector Count Register). After SERVICE is flagged
>> by the ATAPI device (and not serviced), it doesn't respond properly
>> from then on.
>
> Bit 4 isn't SERV in this context, it's DRQ. (It's only SERV when TCQ is
> in use, which it isn't.) It looks like this is a READ CAPACITY command
> that's being issued by PIO. DRQ means the device expects to transfer
> data - either to receive the CDB or send the response. Presumably that
> didn't happen for some reason. Are you sure about both the C/D and I/O
> bits being 1? That would mean command transfer to the host, which
> doesn't make any sense.
>
> You're saying that DRQ never gets cleared after the INQUIRY command?
> It's possible the device wanted to transfer more data than the PRD table
> had room for. Not sure what AHCI ends up doing in this case. I'm CCing
> Tejun who might know more..
libata always prepares for extra space for draining so I doubt that.
Any chance you can post the traces?
--
tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: ATAPI question
2009-03-01 12:51 ` Tejun Heo
@ 2009-03-02 15:58 ` Foster, Doug F
2009-03-02 21:50 ` Foster, Doug F
2009-03-02 23:33 ` Robert Hancock
0 siblings, 2 replies; 16+ messages in thread
From: Foster, Doug F @ 2009-03-02 15:58 UTC (permalink / raw)
To: Tejun Heo, Robert Hancock; +Cc: linux-ide@vger.kernel.org, Foster, Doug F
Yes, I would be glad to post the traces. Is there a preferred location? Otherwise, I can just post them to an Intel FTP server for download.
-----Original Message-----
From: Tejun Heo [mailto:tj@kernel.org]
Sent: Sunday, March 01, 2009 5:52 AM
To: Robert Hancock
Cc: Foster, Doug F; linux-ide@vger.kernel.org
Subject: Re: ATAPI question
Hello,
Robert Hancock wrote:
>> Using a SATA analyzer, I find that on an INQUIRY (12h) ATAPI packet
>> command, the device sets bit-6 (DRDY) and bit-4 (SERV) in the status
>> register, and bits 0 (CoD) and 1 (IO) are set in the ATAPI Interrupt
>> Reason Register (ATA Sector Count Register). After SERVICE is flagged
>> by the ATAPI device (and not serviced), it doesn't respond properly
>> from then on.
>
> Bit 4 isn't SERV in this context, it's DRQ. (It's only SERV when TCQ is
> in use, which it isn't.) It looks like this is a READ CAPACITY command
> that's being issued by PIO. DRQ means the device expects to transfer
> data - either to receive the CDB or send the response. Presumably that
> didn't happen for some reason. Are you sure about both the C/D and I/O
> bits being 1? That would mean command transfer to the host, which
> doesn't make any sense.
>
> You're saying that DRQ never gets cleared after the INQUIRY command?
> It's possible the device wanted to transfer more data than the PRD table
> had room for. Not sure what AHCI ends up doing in this case. I'm CCing
> Tejun who might know more..
libata always prepares for extra space for draining so I doubt that.
Any chance you can post the traces?
--
tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: ATAPI question
2009-03-02 15:58 ` Foster, Doug F
@ 2009-03-02 21:50 ` Foster, Doug F
2009-03-03 0:35 ` Tejun Heo
2009-03-03 18:19 ` Foster, Doug F
2009-03-02 23:33 ` Robert Hancock
1 sibling, 2 replies; 16+ messages in thread
From: Foster, Doug F @ 2009-03-02 21:50 UTC (permalink / raw)
To: Tejun Heo, Robert Hancock; +Cc: linux-ide@vger.kernel.org, Foster, Doug F
-----Original Message-----
From: Foster, Doug F
Sent: Monday, March 02, 2009 8:58 AM
To: Tejun Heo; Robert Hancock
Cc: linux-ide@vger.kernel.org; Foster, Doug F
Subject: RE: ATAPI question
Yes, I would be glad to post the traces. Is there a preferred location? Otherwise, I can just post them to an Intel FTP server for download.
-----Original Message-----
From: Tejun Heo [mailto:tj@kernel.org]
Sent: Sunday, March 01, 2009 5:52 AM
To: Robert Hancock
Cc: Foster, Doug F; linux-ide@vger.kernel.org
Subject: Re: ATAPI question
Hello,
Robert Hancock wrote:
>> Using a SATA analyzer, I find that on an INQUIRY (12h) ATAPI packet
>> command, the device sets bit-6 (DRDY) and bit-4 (SERV) in the status
>> register, and bits 0 (CoD) and 1 (IO) are set in the ATAPI Interrupt
>> Reason Register (ATA Sector Count Register). After SERVICE is flagged
>> by the ATAPI device (and not serviced), it doesn't respond properly
>> from then on.
>
> Bit 4 isn't SERV in this context, it's DRQ. (It's only SERV when TCQ is
> in use, which it isn't.) It looks like this is a READ CAPACITY command
> that's being issued by PIO. DRQ means the device expects to transfer
> data - either to receive the CDB or send the response. Presumably that
> didn't happen for some reason. Are you sure about both the C/D and I/O
> bits being 1? That would mean command transfer to the host, which
> doesn't make any sense.
>
> You're saying that DRQ never gets cleared after the INQUIRY command?
> It's possible the device wanted to transfer more data than the PRD table
> had room for. Not sure what AHCI ends up doing in this case. I'm CCing
> Tejun who might know more..
libata always prepares for extra space for draining so I doubt that.
Any chance you can post the traces?
--
Tejun
+++++++++++++++++++++++++++++++++++++++++++++++++++
I am pasting a couple of traces in text form below:
File C:\Program Files\LeCroy\SASTracer\ATAPI_7_LiteOn.sas.
From Frame #0 to Frame #12756646.
Frame#
_______|_______________________________________________________________________I2
Frame 1921223(19.919 832 425) 1.5(G) D Start - Start( 6.588 µs)
_______| Unknown Sequence(247)
_______|_______________________________________________________________________I2
Frame 1921226(19.919 839 012) N(A) D Start - Start(177.500 ns)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________T2
Frame 1921227(19.919 839 190) N(A) D Start - Start(105.295 µs)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________I2
Frame 1921228(19.919 944 485) N(A) D Start - Start( 2.948 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________T2
Frame 1921229(19.919 947 432) N(A) D Start - Start( 2.735 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________I2
Frame 1921230(19.919 950 167) N(A) D Start - Start( 6.970 µs) COMWAKE
_______|_______________________________________________________________________T2
Frame 1921231(19.919 957 137) N(A) D Start - Start( 1.595 µs)
_______| UNDETERMINED OOB
_______|_______________________________________________________________________T2
Frame 1921232(19.919 958 732) N(A) D Start - Start(157.500 ns)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________I2
Frame 1921235(19.919 958 890) N(A) D Start - Start(108.988 µs)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________T2
Frame 1921244(19.920 067 877) 1.5(G) D Start - Start(25.000 ns) Unknown
_______|_______________________________________________________________________T2
Frame 1921245(19.920 067 902) N(A) D Start - Start(763.090 µs)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________I2
Frame 1921246(19.920 830 992) 1.5(G) D Start - Start( 7.655 µs)
_______| Unknown Sequence(287)
_______|_______________________________________________________________________I2
Frame 1921247(19.920 838 647) N(A) D Start - Start(7.500 ns)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________I2
Frame 1921248(19.920 838 655) N(A) D Start - Start( 3.580 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________T2
Frame 1921249(19.920 842 235) N(A) D Start - Start( 2.670 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________I2
Frame 1921250(19.920 844 905) N(A) D Start - Start( 6.978 µs)
_______| UNDETERMINED OOB
_______|_______________________________________________________________________T2
Frame 1921251(19.920 851 882) N(A) D Start - Start( 1.588 µs)
_______| UNDETERMINED OOB
_______|_______________________________________________________________________T2
Frame 1921252(19.920 853 470) N(A) D Start - Start(165.000 ns)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________I2
Frame 1921255(19.920 853 635) N(A) D Start - Start( 26.715 µs)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________T2
Transaction 0(19.920 880 350) 1.5(G) D Start - Start( 1.004 sec)
_______| SATA(SATA) FIS Type(Reg D->H) Port(0x0) Status(0x0)
_______|_______________________________________________________________________T2
Frame 2656911(20.925 193 352) N(A) D Start - Start( -1.002 µs)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________I2
Frame 2656916(20.925 192 350) 1.5(G) D Start - Start(800.000 ns)
_______| Unknown Sequence(30)
_______|_______________________________________________________________________I2
Frame 2656917(20.925 193 150) N(A) D Start - Start(247.500 ns)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________T2
Frame 2656918(20.925 193 397) 1.5(G) D Start - Start(27.500 ns) Unknown
_______|_______________________________________________________________________T2
Frame 2656919(20.925 193 425) N(A) D Start - Start( 9.998 ms)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________T2
Frame 2656920(20.935 191 875) N(A) D Start - Start( 3.823 ms)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________I2
Frame 2656921(20.939 014 400) N(A) D Start - Start( 2.940 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________T2
Frame 2656922(20.939 017 340) N(A) D Start - Start( 2.663 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________I2
Frame 2656923(20.939 020 002) N(A) D Start - Start( 6.985 µs) COMWAKE
_______|_______________________________________________________________________T2
Frame 2656924(20.939 026 987) N(A) D Start - Start( 1.350 µs) COMWAKE
_______|_______________________________________________________________________T2
Frame 2656925(20.939 028 337) N(A) D Start - Start(395.000 ns)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________I2
Frame 2656928(20.939 028 732) N(A) D Start - Start(108.995 µs)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________T2
Frame 2656937(20.939 137 727) N(A) D Start - Start(763.115 µs)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________I2
Frame 2656938(20.939 900 842) 1.5(G) D Start - Start( 7.652 µs)
_______| Unknown Sequence(287)
_______|_______________________________________________________________________I2
Frame 2656939(20.939 908 495) N(A) D Start - Start(-27.500 ns)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________I2
Frame 2656940(20.939 908 467) N(A) D Start - Start( 3.610 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________T2
Frame 2656941(20.939 912 077) N(A) D Start - Start( 2.678 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________I2
Frame 2656942(20.939 914 755) N(A) D Start - Start( 6.970 µs) COMWAKE
_______|_______________________________________________________________________T2
Frame 2656943(20.939 921 725) N(A) D Start - Start( 1.350 µs) COMWAKE
_______|_______________________________________________________________________T2
Frame 2656944(20.939 923 075) N(A) D Start - Start(402.500 ns)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________I2
Frame 2656947(20.939 923 477) N(A) D Start - Start( 26.375 µs)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________T2
Transaction 1(20.939 949 852) 1.5(G) D Start - Start(475.123 ms)
_______| SATA(SATA) FIS Type(Reg D->H) Port(0x0) Status(0x0)
_______|_______________________________________________________________________I2
Frame 2796226(21.415 072 487) 1.5(G) D Start - Start(749.090 ms)
_______| SATA RCV
_______|_______________________________________________________________________I2
ATA Command 0(22.164 162 437) 1.5(G) D Start - Start(309.000 ms) PROT(ND)
_______| Command(Software Reset) Port(0x0) IN DEV(0) SubCmd. Code(Nop) OUT
_______| DEV(0) BSY(0) DRDY(0) DF(0) na(0) DRQ(0) na(0) na(0) Metrics #Frms(3)
_______|_______________________________________________________________________I2
ATA Command 1(22.473 162 667) 1.5(G) D Start - Start( 16.427 ms) PROT(PI)
_______| Command(IDENTIFY PACKET DEVICE) Port(0x0) IN DEV(0) OUT DEV(0)
_______| BSY(0) DRDY(0) DF(0) na(0) DRQ(0) na(0) na(0)
_______| Data(
__ 000: C0 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 00 00 00 00 00 00 53 45
__ 048: 33 30 20 20 20 20 49 4C 45 54 4F 2D 20 4E 56 44 20 44 48 53 2D 44 36 31 31 53 20 53 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 00 00
__ 096: 00 00 00 0F 00 40 00 02 00 02 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 00 03 00 78 00 78 00 7F 01 78 00 00 00 00 00 00 00
__ 144: 00 00 78 00 09 00 00 00 02 06 00 00 68 00 40 00 78 00 00 00 10 02 00 50 00 40 00 00 00 00 00 40 3F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 192: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 240: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 288: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 336: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 384: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 432: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 A5 46)
_______| Metrics #Frms(3)
_______|_______________________________________________________________________I2
ATA Command 2(22.489 590 082) 1.5(G) D Start - Start( 6.194 ms) PROT(ND)
_______| Command(SET FEATURES) Port(0x0) IN DEV(0)
_______| SubCmd(Enable use of SATA feature) SubCmd Spec.(5) SubCmd Spec.(0)
_______| SubCmd Spec.(0) SubCmd Spec.(0) OUT DEV(0) na(0) na(1) na(0) na(1)
_______| na(0) na(0) na(0) Metrics #Frms(2)
_______|_______________________________________________________________________I2
ATA Command 3(22.495 783 670) 1.5(G) D Start - Start(151.372 ms) PROT(ND)
_______| Command(SET FEATURES) Port(0x0) IN DEV(0) SubCmd(Set transfer mode)
_______| SubCmd Spec.(69) SubCmd Spec.(0) SubCmd Spec.(0) SubCmd Spec.(0) OUT
_______| DEV(0) na(0) na(1) na(0) na(1) na(0) na(0) na(0) Metrics #Frms(2)
_______|_______________________________________________________________________I2
ATA Command 4(22.647 155 740) 1.5(G) D Start - Start( 16.425 ms) PROT(PI)
_______| Command(IDENTIFY PACKET DEVICE) Port(0x0) IN DEV(0) OUT DEV(0)
_______| BSY(0) DRDY(0) DF(0) na(0) DRQ(0) na(0) na(0)
_______| Data(
__ 000: C0 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 00 00 00 00 00 00 53 45
__ 048: 33 30 20 20 20 20 49 4C 45 54 4F 2D 20 4E 56 44 20 44 48 53 2D 44 36 31 31 53 20 53 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 00 00
__ 096: 00 00 00 0F 00 40 00 02 00 02 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 00 03 00 78 00 78 00 7F 01 78 00 00 00 00 00 00 00
__ 144: 00 00 78 00 09 00 00 00 02 06 00 00 68 00 60 00 78 00 00 00 10 02 00 50 00 40 00 00 00 00 00 40 3F 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 192: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 240: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 288: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 336: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 384: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 432: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 A5 06)
_______| Metrics #Frms(3)
_______|_______________________________________________________________________I2
ATA Command 5(22.663 580 270) 1.5(G) D Start - Start( 59.751 ms) PROT(ND)
_______| Command(SET FEATURES) Port(0x0) IN DEV(0)
_______| SubCmd(Enable use of SATA feature) SubCmd Spec.(5) SubCmd Spec.(0)
_______| SubCmd Spec.(0) SubCmd Spec.(0) OUT DEV(0) na(0) na(1) na(0) na(1)
_______| na(0) na(0) na(0) Metrics #Frms(2)
_______|_______________________________________________________________________I2
ATA Command 6(22.723 331 340) 1.5(G) D Start - Start(266.250 µs) PROT(PK)
_______| Command(PACKET) Port(0x0) IN DEV(0) Tag(0) Byte Count(24h) DMA(0)
_______| OVL(0) OUT DEV(0) Tag(0) BSY(0) DRDY(1) DMRD(0) SERV(1) DRQ(0) na(0)
_______| na(0) CHK(0) Byte Count(24h) REL(0) I/O(1) C/D(1) ATAPI
_______| ATAPI Command(INQUIRY) LUN(0) CmdDt(0) EVPD(0) Page/Operation Code(0h)
_______| Allocation Length(24h) Vendor Spec.(0h) NACA(0) Flag(0) Link(0)
_______| Data(
__ 00: 12 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00
__ 16: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 32: 00 00 00 00)
_______| Metrics #Frms(6)
_______|_______________________________________________________________________I2
ATA Command 7(22.723 597 590) 1.5(G) D Sta - Sta(0.000 ns) PROT(PK)
_______| Command(PACKET) Port(0x0) IN DEV(0) Tag(0) Byte Count(60h) DMA(1)
_______| OVL(0) OUT DEV(0) Tag(0) BSY(0) DRDY(1) DMRD(0) SERV(1) DRQ(0) na(0)
_______| na(0) CHK(0) Byte Count(60h) REL(0) I/O(1) C/D(1) ATAPI
_______| ATAPI Command(INQUIRY) LUN(0) CmdDt(0) EVPD(0) Page/Operation Code(0h)
_______| Allocation Length(60h) Vendor Spec.(0h) NACA(0) Flag(0) Link(0)
_______| Data(
__ 00: 12 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 32: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 64: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00)
_______| Metrics #Frms(5)
_______|_______________________________________________________________________
File C:\Program Files\LeCroy\SASTracer\ATAPI_8_Plextor.sas.
From Frame #0 to Frame #10302564.
Frame#
_______|_______________________________________________________________________I2
Frame 6850604(23.319 936 052) 1.5(G) D Start - Start( 1.120 µs)
_______| Unknown Sequence(42)
_______|_______________________________________________________________________I2
Frame 6850605(23.319 937 172) N(A) D Start - Start(103.570 µs)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________T2
Frame 6850622(23.320 040 742) N(A) D Start - Start(25.000 ns)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________T2
Frame 6850623(23.320 040 767) 1.5(G) D Start - Start( 1.853 µs)
_______| Unknown Sequence(128)
_______|_______________________________________________________________________I2
Frame 6850624(23.320 042 620) N(A) D Start - Start( 1.560 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________T2
Frame 6850625(23.320 044 180) N(A) D Start - Start( 4.237 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________I2
Frame 6850626(23.320 048 417) N(A) D Start - Start( 1.145 µs)
_______| UNDETERMINED OOB
_______|_______________________________________________________________________I2
Frame 6850627(23.320 049 562) N(A) D Start - Start(462.500 ns)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________T2
Frame 6850628(23.320 050 025) N(A) D Start - Start( 1.357 µs) COMWAKE
_______|_______________________________________________________________________T2
Frame 6850629(23.320 051 382) N(A) D Start - Start(633.730 µs)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________T2
Frame 6850640(23.320 685 112) 1.5(G) D Start - Start(238.757 µs)
_______| Unknown
_______|_______________________________________________________________________I2
Frame 6850641(23.320 923 870) 1.5(G) D Start - Start( 6.545 µs)
_______| Unknown Sequence(288)
_______|_______________________________________________________________________T2
Frame 6850642(23.320 930 415) 1.5(G) D Start - Start( 1.135 µs)
_______| Unknown Sequence(122)
_______|_______________________________________________________________________I2
Frame 6850643(23.320 931 550) N(A) D Start - Start(15.000 ns)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________I2
Frame 6850644(23.320 931 565) N(A) D Start - Start( 2.105 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________T2
Frame 6850645(23.320 933 670) N(A) D Start - Start(32.500 ns)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________T2
Frame 6850646(23.320 933 702) N(A) D Start - Start( 4.338 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________I2
Frame 6850647(23.320 938 040) N(A) D Start - Start( 1.298 µs) COMWAKE
_______|_______________________________________________________________________I2
Frame 6850648(23.320 939 337) N(A) D Start - Start(245.000 ns)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________T2
Frame 6850649(23.320 939 582) N(A) D Start - Start( 1.357 µs) COMWAKE
_______|_______________________________________________________________________T2
Frame 6850650(23.320 940 940) N(A) D Start - Start(524.515 µs)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________Idle Errors T2
Frame 6850651(23.321 465 455) 1.5(G)
_______| Packet Error(Disparity)-BAD D Start - Start(467.500 ns) Unknown
_______|_______________________________________________________________________Idle Errors I2
Frame 6850654(23.321 465 922) 1.5(G) D
_______| Start - Start(294.124 ms) Unknown(K28.5 D10.2 D21.5 D21.5)
_______|_______________________________________________________________________T2
Transaction 0(23.615 589 715) 1.5(G) D Start - Start(709.772 ms)
_______| SATA(SATA) FIS Type(Reg D->H) Port(0x0) Status(0x10)
_______|_______________________________________________________________________I2
Frame 7395818(24.325 362 022) 1.5(G) D Start - Start( 1.068 µs)
_______| Unknown Sequence(40)
_______|_______________________________________________________________________I2
Frame 7395819(24.325 363 090) N(A) D Start - Start( 10.139 ms)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________T2
Frame 7397306(24.335 502 367) N(A) D Start - Start(30.000 ns)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________T2
Frame 7397307(24.335 502 397) 1.5(G) D Start - Start( 1.813 µs)
_______| Unknown Sequence(68)
_______|_______________________________________________________________________T2
Frame 7397308(24.335 504 210) N(A) D Start - Start( 3.685 ms)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________I2
Frame 7397309(24.339 189 175) N(A) D Start - Start( 3.143 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________T2
Frame 7397310(24.339 192 317) N(A) D Start - Start( 2.685 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________I2
Frame 7397311(24.339 195 002) N(A) D Start - Start( 1.328 µs) COMWAKE
_______|_______________________________________________________________________I2
Frame 7397312(24.339 196 330) N(A) D Start - Start(275.000 ns)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________T2
Frame 7397313(24.339 196 605) N(A) D Start - Start( 1.343 µs) COMWAKE
_______|_______________________________________________________________________T2
Frame 7397314(24.339 197 947) N(A) D Start - Start(633.730 µs)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________T2
Frame 7397325(24.339 831 677) 1.5(G) D Start - Start(238.760 µs)
_______| Unknown
_______|_______________________________________________________________________I2
Frame 7397326(24.340 070 437) 1.5(G) D Start - Start( 6.550 µs)
_______| Unknown Sequence(287)
_______|_______________________________________________________________________T2
Frame 7397327(24.340 076 987) 1.5(G) D Start - Start( 1.103 µs)
_______| Unknown Sequence(122)
_______|_______________________________________________________________________I2
Frame 7397328(24.340 078 090) N(A) D Start - Start(7.500 ns)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________I2
Frame 7397329(24.340 078 097) N(A) D Start - Start( 2.143 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________T2
Frame 7397330(24.340 080 240) N(A) D Start - Start(-27.500 ns)
_______| ELECTRIC IDLE ON
_______|_______________________________________________________________________T2
Frame 7397331(24.340 080 212) N(A) D Start - Start( 4.348 µs)
_______| COMINIT/COMRESET
_______|_______________________________________________________________________I2
Frame 7397332(24.340 084 560) N(A) D Start - Start( 1.320 µs) COMWAKE
_______|_______________________________________________________________________I2
Frame 7397333(24.340 085 880) N(A) D Start - Start(287.500 ns)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________T2
Frame 7397334(24.340 086 167) N(A) D Start - Start( 1.320 µs) COMWAKE
_______|_______________________________________________________________________T2
Frame 7397335(24.340 087 487) N(A) D Start - Start(294.644 ms)
_______| ELECTRIC IDLE OFF
_______|_______________________________________________________________________T2
Transaction 1(24.634 731 872) 1.5(G) D Start - Start(180.509 ms)
_______| SATA(SATA) FIS Type(Reg D->H) Port(0x0) Status(0x10)
_______|_______________________________________________________________________I2
Frame 7579507(24.815 240 955) 1.5(G) D Start - Start(749.091 ms)
_______| SATA RCV
_______|_______________________________________________________________________I2
ATA Command 0(25.564 332 120) 1.5(G) D Start - Start(309.001 ms) PROT(ND)
_______| Command(Software Reset) Port(0x0) IN DEV(0) SubCmd. Code(Nop) OUT
_______| DEV(0) BSY(0) DRDY(0) DF(0) na(0) DRQ(0) na(0) na(0) Metrics #Frms(3)
_______|_______________________________________________________________________I2
ATA Command 1(25.873 333 157) 1.5(G) D Start - Start( 17.156 ms) PROT(PI)
_______| Command(IDENTIFY PACKET DEVICE) Port(0x0) IN DEV(0) OUT DEV(0)
_______| BSY(0) DRDY(0) DF(0) na(0) DRQ(0) na(0) na(0)
_______| Data(
__ 000: C0 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20 20 20 35 31 31 30 31 38 00 00 00 00 00 00 2E 31
__ 048: 31 31 20 20 20 20 4C 50 58 45 4F 54 20 52 56 44 52 44 20 20 50 20 2D 58 31 37 41 36 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 00 00
__ 096: 00 00 00 0F 00 40 00 00 00 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 04 03 00 78 00 78 00 78 00 78 00 00 00 00 00 00 00
__ 144: 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 78 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1F 00 00 00 00 00 00 00 00 00 01 41 00 00 00 00
__ 192: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 240: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 288: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 336: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 384: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 432: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00)
_______| Metrics #Frms(3)
_______|_______________________________________________________________________I2
ATA Command 2(25.890 489 085) 1.5(G) D Start - Start(155.836 ms) PROT(ND)
_______| Command(SET FEATURES) Port(0x0) IN DEV(0) SubCmd(Set transfer mode)
_______| SubCmd Spec.(68) SubCmd Spec.(0) SubCmd Spec.(0) SubCmd Spec.(0) OUT
_______| DEV(0) na(0) na(1) na(0) na(1) na(0) na(0) na(0) Metrics #Frms(2)
_______|_______________________________________________________________________I2
ATA Command 3(26.046 325 220) 1.5(G) D Start - Start( 85.768 ms) PROT(PI)
_______| Command(IDENTIFY PACKET DEVICE) Port(0x0) IN DEV(0) OUT DEV(0)
_______| BSY(0) DRDY(0) DF(0) na(0) DRQ(0) na(0) na(0)
_______| Data(
__ 000: C0 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20 20 20 35 31 31 30 31 38 00 00 00 00 00 00 2E 31
__ 048: 31 31 20 20 20 20 4C 50 58 45 4F 54 20 52 56 44 52 44 20 20 50 20 2D 58 31 37 41 36 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 00 00
__ 096: 00 00 00 0F 00 40 00 00 00 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 00 03 00 78 00 78 00 78 00 78 00 00 00 00 00 00 00
__ 144: 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 78 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1F 10 00 00 00 00 00 00 00 00 01 41 00 00 00 00
__ 192: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 240: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 288: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 336: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 384: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 432: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00)
_______| Metrics #Frms(3)
_______|_______________________________________________________________________I2
ATA Command 4(26.132 093 402) 1.5(G) D Start - Start( 1.437 sec)
_______| PROT(PK) Command(PACKET) Port(0x0) IN DEV(0) Tag(0) Byte Count(24h)
_______| DMA(0) OVL(0) OUT DEV(0) Tag(0) BSY(0) DRDY(1) DMRD(0) SERV(1) DRQ(0)
_______| na(0) na(0) CHK(0) Byte Count(0h) REL(0) I/O(1) C/D(1) ATAPI
_______| ATAPI Command(INQUIRY) LUN(0) CmdDt(0) EVPD(0) Page/Operation Code(0h)
_______| Allocation Length(24h) Vendor Spec.(0h) NACA(0) Flag(0) Link(0)
_______| Data(
__ 00: 12 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00
__ 16: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 32: 00 00 00 00)
_______| Metrics #Frms(6)
_______|_______________________________________________________________________I2
ATA Command 5(27.569 219 455) 1.5(G) D Sta - Sta(0.000 ns) PROT(PK)
_______| Command(PACKET) Port(0x0) IN DEV(0) Tag(0) Byte Count(60h) DMA(1)
_______| OVL(0) OUT DEV(0) Tag(0) BSY(0) DRDY(1) DMRD(0) SERV(1) DRQ(0) na(0)
_______| na(0) CHK(0) Byte Count(0h) REL(0) I/O(1) C/D(1) ATAPI
_______| ATAPI Command(INQUIRY) LUN(0) CmdDt(0) EVPD(0) Page/Operation Code(0h)
_______| Allocation Length(60h) Vendor Spec.(0h) NACA(0) Flag(0) Link(0)
_______| Data(
__ 00: 12 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 32: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
__ 64: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00)
_______| Metrics #Frms(5)
_______|_______________________________________________________________________
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: ATAPI question
2009-03-02 21:50 ` Foster, Doug F
@ 2009-03-03 0:35 ` Tejun Heo
2009-03-03 15:44 ` Foster, Doug F
2009-03-03 18:19 ` Foster, Doug F
1 sibling, 1 reply; 16+ messages in thread
From: Tejun Heo @ 2009-03-03 0:35 UTC (permalink / raw)
To: Foster, Doug F; +Cc: Robert Hancock, linux-ide@vger.kernel.org
Foster, Doug F wrote:
> Yes, I would be glad to post the traces. Is there a preferred
> location? Otherwise, I can just post them to an Intel FTP server
> for download.
Intel FTP sounds fine. It's the lecroy one, right?
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: ATAPI question
2009-03-03 0:35 ` Tejun Heo
@ 2009-03-03 15:44 ` Foster, Doug F
0 siblings, 0 replies; 16+ messages in thread
From: Foster, Doug F @ 2009-03-03 15:44 UTC (permalink / raw)
To: Tejun Heo; +Cc: Robert Hancock, linux-ide@vger.kernel.org, Foster, Doug F
I bottom posted a couple of text traces yesterday. If you have the LeCroy software, then I will post all of my traces for your convenience. I can convert to text and paste in email if that is better. Let me know what you would like.
-----Original Message-----
From: Tejun Heo [mailto:tj@kernel.org]
Sent: Monday, March 02, 2009 5:35 PM
To: Foster, Doug F
Cc: Robert Hancock; linux-ide@vger.kernel.org
Subject: Re: ATAPI question
Foster, Doug F wrote:
> Yes, I would be glad to post the traces. Is there a preferred
> location? Otherwise, I can just post them to an Intel FTP server
> for download.
Intel FTP sounds fine. It's the lecroy one, right?
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: ATAPI question
2009-03-02 21:50 ` Foster, Doug F
2009-03-03 0:35 ` Tejun Heo
@ 2009-03-03 18:19 ` Foster, Doug F
2009-03-04 1:44 ` Tejun Heo
2009-03-09 21:35 ` Foster, Doug F
1 sibling, 2 replies; 16+ messages in thread
From: Foster, Doug F @ 2009-03-03 18:19 UTC (permalink / raw)
To: Tejun Heo, Robert Hancock; +Cc: linux-ide@vger.kernel.org, Foster, Doug F
I posted several traces on an FTP server. To view them, you will need to download the LeCroy SASSuite software.
The FTP server is a blind site and the files will only remain there for 24-hours.
How to retrieve the files from the FTP server:
(My apologies for the Windows directions. Just do the equivalent in Linux.)
Open cmd.exe prompt
>ftp ftp.intel.com
User: anonymous
Password: <Enter anything here>
ftp>
ftp> binary
ftp> cd pub/outgoing
ftp> pwd
ftp> lcd c:\temp
ftp> get ATAPI_1_Plextor.sas
ftp> get ATAPI_3_Plextor.sas
ftp> get ATAPI_4_Plextor.sas
ftp> get ATAPI_5_LiteOn.sas
ftp> get ATAPI_6_LiteOn.sas
ftp> get ATAPI_7_LiteOn.sas
ftp> get ATAPI_8_Plextor.sas
ftp> quit
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: ATAPI question
2009-03-03 18:19 ` Foster, Doug F
@ 2009-03-04 1:44 ` Tejun Heo
2009-03-04 2:09 ` Robert Hancock
2009-03-04 15:44 ` Foster, Doug F
2009-03-09 21:35 ` Foster, Doug F
1 sibling, 2 replies; 16+ messages in thread
From: Tejun Heo @ 2009-03-04 1:44 UTC (permalink / raw)
To: Foster, Doug F; +Cc: Robert Hancock, linux-ide@vger.kernel.org
Hello, Foster.
Foster, Doug F wrote:
> I posted several traces on an FTP server. To view them, you will
> need to download the LeCroy SASSuite software.
>
> The FTP server is a blind site and the files will only remain there
> for 24-hours.
>
> How to retrieve the files from the FTP server:
> (My apologies for the Windows directions. Just do the equivalent in
> Linux.)
>
> Open cmd.exe prompt
>
>> ftp ftp.intel.com
> User: anonymous
> Password: <Enter anything here>
> ftp>
> ftp> binary
> ftp> cd pub/outgoing
> ftp> pwd
> ftp> lcd c:\temp
> ftp> get ATAPI_1_Plextor.sas
> ftp> get ATAPI_3_Plextor.sas
> ftp> get ATAPI_4_Plextor.sas
> ftp> get ATAPI_5_LiteOn.sas
> ftp> get ATAPI_6_LiteOn.sas
> ftp> get ATAPI_7_LiteOn.sas
> ftp> get ATAPI_8_Plextor.sas
> ftp> quit
I can't get them.
ftp> pwd
257 "/pub/outgoing" is current directory.
ftp> get ATAPI_1_Plextor.sas
local: ATAPI_1_Plextor.sas remote: ATAPI_1_Plextor.sas
229 Entering Extended Passive Mode (|||51535|)
And then nothing. Or do I have to use active mode? Any chance you
can put them somewhere more accessible? Preferably http?
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: ATAPI question
2009-03-04 1:44 ` Tejun Heo
@ 2009-03-04 2:09 ` Robert Hancock
2009-03-04 15:44 ` Foster, Doug F
1 sibling, 0 replies; 16+ messages in thread
From: Robert Hancock @ 2009-03-04 2:09 UTC (permalink / raw)
To: Tejun Heo; +Cc: Foster, Doug F, linux-ide@vger.kernel.org
On Tue, Mar 3, 2009 at 7:44 PM, Tejun Heo <tj@kernel.org> wrote:
> I can't get them.
>
> ftp> pwd
> 257 "/pub/outgoing" is current directory.
> ftp> get ATAPI_1_Plextor.sas
> local: ATAPI_1_Plextor.sas remote: ATAPI_1_Plextor.sas
> 229 Entering Extended Passive Mode (|||51535|)
>
> And then nothing. Or do I have to use active mode? Any chance you
> can put them somewhere more accessible? Preferably http?
It looked like it was working for me.. I'll see if I can get this
software set up and take a look if someone doesn't beat me to it.
^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: ATAPI question
2009-03-04 1:44 ` Tejun Heo
2009-03-04 2:09 ` Robert Hancock
@ 2009-03-04 15:44 ` Foster, Doug F
2009-03-04 16:03 ` Tejun Heo
1 sibling, 1 reply; 16+ messages in thread
From: Foster, Doug F @ 2009-03-04 15:44 UTC (permalink / raw)
To: Tejun Heo; +Cc: Robert Hancock, linux-ide@vger.kernel.org, Foster, Doug F
-----Original Message-----
From: Tejun Heo [mailto:tj@kernel.org]
Sent: Tuesday, March 03, 2009 6:45 PM
To: Foster, Doug F
Cc: Robert Hancock; linux-ide@vger.kernel.org
Subject: Re: ATAPI question
Hello, Foster.
Foster, Doug F wrote:
> I posted several traces on an FTP server. To view them, you will
> need to download the LeCroy SASSuite software.
>
> The FTP server is a blind site and the files will only remain there
> for 24-hours.
>
> How to retrieve the files from the FTP server:
> (My apologies for the Windows directions. Just do the equivalent in
> Linux.)
>
> Open cmd.exe prompt
>
>> ftp ftp.intel.com
> User: anonymous
> Password: <Enter anything here>
> ftp>
> ftp> binary
> ftp> cd pub/outgoing
> ftp> pwd
> ftp> lcd c:\temp
> ftp> get ATAPI_1_Plextor.sas
> ftp> get ATAPI_3_Plextor.sas
> ftp> get ATAPI_4_Plextor.sas
> ftp> get ATAPI_5_LiteOn.sas
> ftp> get ATAPI_6_LiteOn.sas
> ftp> get ATAPI_7_LiteOn.sas
> ftp> get ATAPI_8_Plextor.sas
> ftp> quit
I can't get them.
ftp> pwd
257 "/pub/outgoing" is current directory.
ftp> get ATAPI_1_Plextor.sas
local: ATAPI_1_Plextor.sas remote: ATAPI_1_Plextor.sas
229 Entering Extended Passive Mode (|||51535|)
And then nothing. Or do I have to use active mode? Any chance you
can put them somewhere more accessible? Preferably http?
Thanks.
--
Tejun
++++++++++++++++++++++
Tejun, I will find an alternate way to post later today. I just tested with a CentOS machine.
. . . .
ftp> get ATAPI_1_Plextor.sas
local: ATAPI_1_Plextor.sas remote: ATAPI_1_Plextor.sas
227 Enter Passive Mod(198,175,98,65,49,58)
150 Opening BINARY mode data connection for ATAPI_1_Plextor.sas (197520504 bytes
226 Tranfer complete.
197520504 bytes received in 1.2e+02 seconds (1.7e+03 Kbytes/s)
ftp>
Can you try again? Obviously, the files are big.
^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: ATAPI question
2009-03-03 18:19 ` Foster, Doug F
2009-03-04 1:44 ` Tejun Heo
@ 2009-03-09 21:35 ` Foster, Doug F
2009-03-11 9:31 ` Tejun Heo
1 sibling, 1 reply; 16+ messages in thread
From: Foster, Doug F @ 2009-03-09 21:35 UTC (permalink / raw)
To: Tejun Heo, Robert Hancock, linux-ide@vger.kernel.org; +Cc: Foster, Doug F
Did anyone get a chance to look at these traces?
Any thoughts on what the problem is?
Any guidance on experiments that I should try?
Is there anything else that I can provide to help?
-----Original Message-----
From: Foster, Doug F
Sent: Tuesday, March 03, 2009 11:20 AM
To: Tejun Heo; Robert Hancock
Cc: linux-ide@vger.kernel.org; Foster, Doug F
Subject: RE: ATAPI question
I posted several traces on an FTP server. To view them, you will need to download the LeCroy SASSuite software.
The FTP server is a blind site and the files will only remain there for 24-hours.
How to retrieve the files from the FTP server:
(My apologies for the Windows directions. Just do the equivalent in Linux.)
Open cmd.exe prompt
>ftp ftp.intel.com
User: anonymous
Password: <Enter anything here>
ftp>
ftp> binary
ftp> cd pub/outgoing
ftp> pwd
ftp> lcd c:\temp
ftp> get ATAPI_1_Plextor.sas
ftp> get ATAPI_3_Plextor.sas
ftp> get ATAPI_4_Plextor.sas
ftp> get ATAPI_5_LiteOn.sas
ftp> get ATAPI_6_LiteOn.sas
ftp> get ATAPI_7_LiteOn.sas
ftp> get ATAPI_8_Plextor.sas
ftp> quit
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: ATAPI question
2009-03-09 21:35 ` Foster, Doug F
@ 2009-03-11 9:31 ` Tejun Heo
2009-03-12 21:02 ` Foster, Doug F
0 siblings, 1 reply; 16+ messages in thread
From: Tejun Heo @ 2009-03-11 9:31 UTC (permalink / raw)
To: Foster, Doug F; +Cc: Robert Hancock, linux-ide@vger.kernel.org
Hello,
Foster, Doug F wrote:
> Did anyone get a chance to look at these traces?
> Any thoughts on what the problem is?
> Any guidance on experiments that I should try?
> Is there anything else that I can provide to help?
Yeap, I just did. I'm looking at ATAPI_7_LiteOn.sas. The offending
one is the one ending with the FIS 22.723 807 202, right?
On the bus level, everything seems fine. The host prepares for
96bytes transfer and device does it and successfully sends D2H Reg FIS
for command completion. The only thing I can think of is the draining
buffer confusing the controller somehow. If you make
libata-scsi.c::atapi_drain_needed() always return zero, does anything
change?
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: ATAPI question
2009-03-11 9:31 ` Tejun Heo
@ 2009-03-12 21:02 ` Foster, Doug F
0 siblings, 0 replies; 16+ messages in thread
From: Foster, Doug F @ 2009-03-12 21:02 UTC (permalink / raw)
To: Tejun Heo; +Cc: Robert Hancock, linux-ide@vger.kernel.org, Foster, Doug F
Tejun wrote:
Yeap, I just did. I'm looking at ATAPI_7_LiteOn.sas. The offending
one is the one ending with the FIS 22.723 807 202, right?
On the bus level, everything seems fine. The host prepares for
96bytes transfer and device does it and successfully sends D2H Reg FIS
for command completion. The only thing I can think of is the draining
buffer confusing the controller somehow. If you make
libata-scsi.c::atapi_drain_needed() always return zero, does anything
change?
++++++++++++++++++++
Tejun,
The problem occurs in 2.6.18.8 which doesn't have atapi_drain_needed() and in 2.6.28.7 which does. I had atapi_drain_needed() return zero on 2.6.28.7 with no change in behavior.
If you click the ATA button (ATA application layer) on the above trace and expand the IN and OUT boxes on transaction 22.723 597 590, you see the DRDY, SERV, I/O, C/D pattern that I described before. Does this pattern make sense in this context? Do you think that this pattern is of concern or should we be looking elsewhere for the problem?
Doug
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: ATAPI question
2009-03-02 15:58 ` Foster, Doug F
2009-03-02 21:50 ` Foster, Doug F
@ 2009-03-02 23:33 ` Robert Hancock
1 sibling, 0 replies; 16+ messages in thread
From: Robert Hancock @ 2009-03-02 23:33 UTC (permalink / raw)
To: Foster, Doug F; +Cc: Tejun Heo, linux-ide@vger.kernel.org
Foster, Doug F wrote:
> Yes, I would be glad to post the traces. Is there a preferred location? Otherwise, I can just post them to an Intel FTP server for download.
On an FTP would be usable, but if you can extract out key parts and post
them on the list, that might be better..
>
> -----Original Message-----
> From: Tejun Heo [mailto:tj@kernel.org]
> Sent: Sunday, March 01, 2009 5:52 AM
> To: Robert Hancock
> Cc: Foster, Doug F; linux-ide@vger.kernel.org
> Subject: Re: ATAPI question
>
> Hello,
>
> Robert Hancock wrote:
>>> Using a SATA analyzer, I find that on an INQUIRY (12h) ATAPI packet
>>> command, the device sets bit-6 (DRDY) and bit-4 (SERV) in the status
>>> register, and bits 0 (CoD) and 1 (IO) are set in the ATAPI Interrupt
>>> Reason Register (ATA Sector Count Register). After SERVICE is flagged
>>> by the ATAPI device (and not serviced), it doesn't respond properly
>>> from then on.
>> Bit 4 isn't SERV in this context, it's DRQ. (It's only SERV when TCQ is
>> in use, which it isn't.) It looks like this is a READ CAPACITY command
>> that's being issued by PIO. DRQ means the device expects to transfer
>> data - either to receive the CDB or send the response. Presumably that
>> didn't happen for some reason. Are you sure about both the C/D and I/O
>> bits being 1? That would mean command transfer to the host, which
>> doesn't make any sense.
>>
>> You're saying that DRQ never gets cleared after the INQUIRY command?
>> It's possible the device wanted to transfer more data than the PRD table
>> had room for. Not sure what AHCI ends up doing in this case. I'm CCing
>> Tejun who might know more..
>
> libata always prepares for extra space for draining so I doubt that.
> Any chance you can post the traces?
>
> --
> tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2009-03-12 21:02 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-27 23:50 ATAPI question Foster, Doug F
2009-02-28 3:08 ` Robert Hancock
2009-03-01 12:51 ` Tejun Heo
2009-03-02 15:58 ` Foster, Doug F
2009-03-02 21:50 ` Foster, Doug F
2009-03-03 0:35 ` Tejun Heo
2009-03-03 15:44 ` Foster, Doug F
2009-03-03 18:19 ` Foster, Doug F
2009-03-04 1:44 ` Tejun Heo
2009-03-04 2:09 ` Robert Hancock
2009-03-04 15:44 ` Foster, Doug F
2009-03-04 16:03 ` Tejun Heo
2009-03-09 21:35 ` Foster, Doug F
2009-03-11 9:31 ` Tejun Heo
2009-03-12 21:02 ` Foster, Doug F
2009-03-02 23:33 ` Robert Hancock
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).