2.6.24-rc1, sata_sil: access to SH-S183A broken again?
Hi Tejun,
Is it possible that the DMA workaround for sata_sil and the Samsung SH-S183A DVD writer was lost for 2.6.24-rc1? I found this in syslog:
Oct 28 11:29:08 pluto kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Oct 28 11:29:08 pluto kernel: ata4.00: cmd a0/01:00:00:10:00/00:00:00:00:00/a0 tag 0 cdb 0xa4 data 16 in
Oct 28 11:29:08 pluto kernel: res 40/00:02:00:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Oct 28 11:29:08 pluto kernel: ata4.00: status: { DRDY }
Oct 28 11:29:08 pluto kernel: ata4: soft resetting link
Oct 28 11:29:13 pluto kernel: ata4: port is slow to respond, please be patient (Status 0xf8)
Oct 28 11:29:18 pluto kernel: ata4: SRST failed (errno=-16)
Oct 28 11:29:18 pluto kernel: ata4: hard resetting link
Oct 28 11:29:19 pluto kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Oct 28 11:29:19 pluto kernel: ata4.00: configured for UDMA/33
Oct 28 11:29:19 pluto kernel: ata4: EH complete
Oct 28 11:29:26 pluto kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Oct 28 11:29:26 pluto kernel: ata4.00: cmd a0/01:00:00:10:00/00:00:00:00:00/a0 tag 0 cdb 0xa4 data 16 in
Oct 28 11:29:26 pluto kernel: res 40/00:02:00:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Oct 28 11:29:26 pluto kernel: ata4.00: status: { DRDY }
Oct 28 11:29:27 pluto kernel: ata4: soft resetting link
Oct 28 11:29:32 pluto kernel: ata4: port is slow to respond, please be patient (Status 0xf8)
Oct 28 11:29:37 pluto kernel: ata4: SRST failed (errno=-16)
Oct 28 11:29:37 pluto kernel: ata4: hard resetting link
Oct 28 11:29:37 pluto kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Oct 28 11:29:38 pluto kernel: ata4.00: configured for UDMA/33
Oct 28 11:29:38 pluto kernel: ata4: EH complete
Oct 28 11:29:38 pluto kernel: sr0: disc change detected.Its difficult to reproduce, though.
Regards
Harri
Quoted 4 lines · Harri
Hi Tejun,
Is it possible that the DMA workaround for
sata_siland the Samsung SH-S183A DVD writer was lost for 2.6.24-rc1? I found
No, I don't think we ever had workaround for sata_sil + SH-S183A combination. Do you have any specific patch/commit in mind?
Quoted 1 line
this in syslog:
[--snip--]
Quoted 18 lines
Oct 28 11:29:26 pluto kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr
0x0 action 0x2 frozen
Oct 28 11:29:26 pluto kernel: ata4.00: cmd
a0/01:00:00:10:00/00:00:00:00:00/a0 tag 0 cdb 0xa4 data 16 in
Oct 28 11:29:26 pluto kernel: res
40/00:02:00:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Oct 28 11:29:26 pluto kernel: ata4.00: status: { DRDY }
Oct 28 11:29:27 pluto kernel: ata4: soft resetting link
Oct 28 11:29:32 pluto kernel: ata4: port is slow to respond, please be
patient (Status 0xf8)
Oct 28 11:29:37 pluto kernel: ata4: SRST failed (errno=-16)
Oct 28 11:29:37 pluto kernel: ata4: hard resetting link
Oct 28 11:29:37 pluto kernel: ata4: SATA link up 1.5 Gbps (SStatus 113
SControl 310)
Oct 28 11:29:38 pluto kernel: ata4.00: configured for UDMA/33
Oct 28 11:29:38 pluto kernel: ata4: EH complete
Oct 28 11:29:38 pluto kernel: sr0: disc change detected.Quoted 1 line
Its difficult to reproduce, though.
The failing command is REPORT_KEY. What were you doing when you saw this error?
Not being reproducible indicates that it's unlikely to be a DMA issue and more likely a temporary glitch in media recognition.
Thanks.
Signature · 1 line
tejun
Sorry, seems that this wasn't send to the mailing list. See private reply.
Regards
Harri
========================================================================
Quoted 39 lines · Tejun Heo
Quoted 4 lines · Harri
Hi Tejun,
Is it possible that the DMA workaround for
sata_siland the Samsung SH-S183A DVD writer was lost for 2.6.24-rc1? I foundNo, I don't think we ever had workaround for
sata_sil+ SH-S183A combination. Do you have any specific patch/commit in mind?Quoted 1 line
this in syslog:
[--snip--]
Quoted 18 lines
Oct 28 11:29:26 pluto kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Oct 28 11:29:26 pluto kernel: ata4.00: cmd a0/01:00:00:10:00/00:00:00:00:00/a0 tag 0 cdb 0xa4 data 16 in Oct 28 11:29:26 pluto kernel: res 40/00:02:00:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout) Oct 28 11:29:26 pluto kernel: ata4.00: status: { DRDY } Oct 28 11:29:27 pluto kernel: ata4: soft resetting link Oct 28 11:29:32 pluto kernel: ata4: port is slow to respond, please be patient (Status 0xf8) Oct 28 11:29:37 pluto kernel: ata4: SRST failed (errno=-16) Oct 28 11:29:37 pluto kernel: ata4: hard resetting link Oct 28 11:29:37 pluto kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 28 11:29:38 pluto kernel: ata4.00: configured for UDMA/33 Oct 28 11:29:38 pluto kernel: ata4: EH complete Oct 28 11:29:38 pluto kernel: sr0: disc change detected.Quoted 1 line
Its difficult to reproduce, though.
The failing command is
REPORT_KEY. What were you doing when you saw this error?Not being reproducible indicates that it's unlikely to be a DMA issue and more likely a temporary glitch in media recognition.
Thanks.
Hello,
Quoted 2 lines · Harri
Sorry, seems that this wasn't send to the mailing list. See private reply.
OIC, now I remember.
Quoted 29 lines
Quoted 29 lines
Quoted 4 lines · Harri
Hi Tejun,
Is it possible that the DMA workaround for
sata_siland the Samsung SH-S183A DVD writer was lost for 2.6.24-rc1? I foundNo, I don't think we ever had workaround for
sata_sil+ SH-S183A combination. Do you have any specific patch/commit in mind?Quoted 1 line
this in syslog:
[--snip--]
Quoted 18 lines
Oct 28 11:29:26 pluto kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Oct 28 11:29:26 pluto kernel: ata4.00: cmd a0/01:00:00:10:00/00:00:00:00:00/a0 tag 0 cdb 0xa4 data 16 in Oct 28 11:29:26 pluto kernel: res 40/00:02:00:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout) Oct 28 11:29:26 pluto kernel: ata4.00: status: { DRDY } Oct 28 11:29:27 pluto kernel: ata4: soft resetting link Oct 28 11:29:32 pluto kernel: ata4: port is slow to respond, please be patient (Status 0xf8) Oct 28 11:29:37 pluto kernel: ata4: SRST failed (errno=-16) Oct 28 11:29:37 pluto kernel: ata4: hard resetting link Oct 28 11:29:37 pluto kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 28 11:29:38 pluto kernel: ata4.00: configured for UDMA/33 Oct 28 11:29:38 pluto kernel: ata4: EH complete Oct 28 11:29:38 pluto kernel: sr0: disc change detected.
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
Its difficult to reproduce, though.
The failing command is
REPORT_KEY. What were you doing when you saw this error?
Were you able to reproduce it? If it actually is the same problem (ATAPI DMA timing out on data transfers of certain size), it should be reproducible when you repeat the same thing.
(Cc'ing Alan) Alan, this was one of those weird ATAPI DMA cases which were fixed by transfer size alignment check in check_atapi_dma(). The controller is sata_sil, so I don't think it was a controller problem.
Thanks.
Signature · 1 line
tejun
Hi Tejun,
Quoted 5 lines · Tejun Heo
Were you able to reproduce it? If it actually is the same problem (ATAPI DMA timing out on data transfers of certain size), it should be reproducible when you repeat the same thing.
I tried several times this morning, but I couldn't reproduce it. Maybe its really the hardware. I would suggest to put it on hold.
Thanx anyway
Harri