Bug 8856
Summary: | (ata_piix PATA) ata3: port is slow to respond, please be patient (Status 0xd1) | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Maximo Monsalvo (maxnux) |
Component: | Serial ATA | Assignee: | Jeff Garzik (jgarzik) |
Status: | CLOSED OBSOLETE | ||
Severity: | high | CC: | alan, albertcc, chantra, martin, maxnux, ramadesikangr |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.21.5,2.6.22.1 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Maximo Monsalvo
2007-08-07 09:21:17 UTC
*** Bug 8857 has been marked as a duplicate of this bug. *** Does it still happen if you have a media in the drive? (In reply to comment #2) > Does it still happen if you have a media in the drive? > reading de bug http://bugzilla.kernel.org/show_bug.cgi?id=8316 i upgrade the dvdrw firmware from as05 to as99 ,but the error continues happening i put a CD in the drive and until the moment there was no the error (In reply to comment #3) > (In reply to comment #2) > > Does it still happen if you have a media in the drive? > > > reading de bug http://bugzilla.kernel.org/show_bug.cgi?id=8316 > i upgrade the dvdrw firmware from as05 to as99 ,but the error continues > happening > > i put a CD in the drive and until the moment there was no the error > leave to the PC all the morning caught without uses and if it gave the error one the same error ata3.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata3.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x1e data 0 res 40/00:02:00:08:00/00:00:00:00:00/b0 Emask 0x4 (timeout) ata3: port is slow to respond, please be patient (Status 0xd0) ata3: device not ready (errno=-16), forcing hardreset ata3: soft resetting port ata3.00: configured for UDMA/100 ata3.01: configured for UDMA/33 ata3: EH complete sd 2:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB) sd 2:0:0:0: [sda] Write Protect is off sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 2:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB) sd 2:0:0:0: [sda] Write Protect is off sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > ATAPI: TSSTcorpCD/DVDW TS-L632D, AS05, max UDMA/33
> ...
> i upgrade the dvdrw firmware from as05 to as99, but the error
> continues happening
Hi Maximo,
AS99 firmware was known to have the problem, too. Could you please try to crossflash the firmware of your TS-L632D to "SC03" or "SC04" version? Thanks.
(Be warned that you are at your own risk to crossflash the firmware of the drive.)
(In reply to comment #5) > > ATAPI: TSSTcorpCD/DVDW TS-L632D, AS05, max UDMA/33 > > ... > > i upgrade the dvdrw firmware from as05 to as99, but the error > > continues happening > > Hi Maximo, > > AS99 firmware was known to have the problem, too. Could you please try to > crossflash the firmware of your TS-L632D to "SC03" or "SC04" version? Thanks. > > (Be warned that you are at your own risk to crossflash the firmware of the > drive.) > Hi , thank for answer , and sorry my english ;) I try crossflash the TS-L632D-as99 version to sc04 version ,but sfdnwin says that this firmaware is not compatible with that dvdrw .ican't Either burn cds/dvd in linux,will it be for the same bug? > sfdnwin says that this firmaware is not compatible with that dvdrw ... Hi Maximo, It seems that you need to use "sfdnwin -nocheck" for crossflash. (adding Chantra to the cc list) There is a post by Chantra about the crossflash (https://lists.ubuntu.com/archives/kernel-bugs/2007-May/026957.html). Maybe Chantra can help on it. (In reply to comment #7) > > sfdnwin says that this firmaware is not compatible with that dvdrw ... > > Hi Maximo, > > It seems that you need to use "sfdnwin -nocheck" for crossflash. > > (adding Chantra to the cc list) > There is a post by Chantra about the crossflash > (https://lists.ubuntu.com/archives/kernel-bugs/2007-May/026957.html). > Maybe Chantra can help on it. > ok work and there was no problem until the moment, perishes to have solved the error very thanks Albert, so, there is no other way than cross-flashing the firmware to get it working? Even PIO doesn't work? > so, there is no other way than cross-flashing the firmware to get it > working? Even PIO doesn't work? It seems even PIO doesn't work. ======================================= In bug 8316, the TS-L632 still timesout with either "limit ATAPI DMA to R/W only" and (http://bugzilla.kernel.org/show_bug.cgi?id=8316#c44) "limit ATAPI DMA to multiple of 16 bytes" (http://bugzilla.kernel.org/show_bug.cgi?id=8316#c87) Chantra got timeout on TEST UNIT READY, which is ATAPI_NODATA. Laurent got timeout on the following command, which is ATAPI PIO: Jun 29 14:14:57 gemini kernel: [ 853.662718] CDB (1:0,0,0) 25 00 00 00 00 00 00 00 00 Jun 29 14:14:57 gemini kernel: [ 853.669337] ata1: protocol 5 task_state 1 (dev_stat 0x58) Jun 29 14:14:57 gemini kernel: [ 853.670130] ata1: protocol 5 task_state 2 Jun 29 14:14:57 gemini kernel: [ 853.670137] ata1: protocol 5 task_state 2 (dev_stat 0x51) Jun 29 14:14:57 gemini kernel: [ 853.670140] ata1: protocol 5 task_state 3 (dev_stat 0x51) Jun 29 14:14:57 gemini kernel: [ 853.670143] ata1: protocol 5 task_state 4 (dev_stat 0x51) Jun 29 14:14:58 gemini kernel: [ 854.452888] ata1: protocol 5 task_state 1 Jun 29 14:14:59 gemini kernel: [ 854.822040] ata1: protocol 5 task_state 1 ... <snip> ... Jun 29 14:15:26 gemini kernel: [ 877.084255] ata1: protocol 5 task_state 1 Jun 29 14:15:26 gemini kernel: [ 877.084580] ata1: protocol 5 task_state 1 Jun 29 14:15:26 gemini kernel: [ 877.596827] ata1: protocol 5 task_state 1 Jun 29 14:15:27 gemini kernel: [ 878.087649] ata1: protocol 5 task_state 1 Jun 29 14:15:27 gemini kernel: [ 878.535855] ata1.00: qc timeout (cmd 0xa0) Also from bug 8316, for the same READ_TOC (0x43) command, sometimes the drive did it well for many comands, but somehow failed later. It seems somehow the continuous polling of "hald-addon-storage" on the TS-L632D plus the specific sequence of command sent by sr.c/cdrom.c make the firmware unresponsive. For the real root cause, maybe only the TSST firmware guys knows... Thanks for the explanation. I guess all we can do is documenting this in linux-ata.org, probably under a new section, say, "known hardware compatibility issues". Can you make a html page on this subject including explanation and solution (cross-flashing) and send it to Jeff? If you're too busy, just write me a mail with pointers, I'll compile the page. Thanks. > Can you make a html page on this subject including explanation
> and solution (cross-flashing) and send it to Jeff?
Ok, will do. It seems many users of TS-L632D got this problem. Hopefully they can google and find the workaround solution from linux-ata.org next time.
|