DMA Timeouts with 3112 SATA Controller (status == 0x21)
"Me too" - when I enable DMA it's not long before the system stops responding altogether. Without DMA, I get a data read rate of about 800KBps.
But also, I have two identical drives attached - hda and hde (both ST380023AS). Even if I don't turn on DMA, if I am using both fairly intensively at the same time (at least that's the only thing I can identify as an apparent common difference), one will (on random occasions) start returning errors for every access. If this happens to be the drive that the operating system is installed on, the result is somewhat fatal. If it's the other drive I can continue, but any attempt to access it fails. There are some syslog entries that appear to relate to this:
Apr 11 07:42:49 milat kernel: hde: status timeout: status=0xd0 { Busy }
Apr 11 07:42:49 milat kernel:
Apr 11 07:42:49 milat kernel: ide2: reset phy, status=0x00000113, siimage_reset
Apr 11 07:42:49 milat kernel: hde: no DRQ after issuing WRITE
Apr 11 07:43:19 milat kernel: ide2: reset timed-out, status=0xd8
Apr 11 07:43:20 milat kernel: hde: status timeout: status=0xd8 { Busy }
Apr 11 07:43:20 milat kernel:
Apr 11 07:43:20 milat kernel: ide2: reset phy, status=0x00000113, siimage_reset
Apr 11 07:43:20 milat kernel: hde: drive not ready for command
Apr 11 07:43:51 milat kernel: t: I/O error, dev 21:02 (hde), sector 6183724
Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), sector 6183726
Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), sector 6183728
Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), sector 6183730
Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), sector 6183732...
Gurr!!!!!!!
These drives were not to make it to market in the commom purchase marketspace!
This is not a fun one to fix!
This is all I can say for now :-(
Quoted 29 lines · Troy Rollo
"Me too" - when I enable DMA it's not long before the system stops responding altogether. Without DMA, I get a data read rate of about 800KBps.
But also, I have two identical drives attached - hda and hde (both ST380023AS). Even if I don't turn on DMA, if I am using both fairly intensively at the same time (at least that's the only thing I can identify as an apparent common difference), one will (on random occasions) start returning errors for every access. If this happens to be the drive that the operating system is installed on, the result is somewhat fatal. If it's the other drive I can continue, but any attempt to access it fails. There are some syslog entries that appear to relate to this:
Apr 11 07:42:49 milat kernel: hde: status timeout: status=0xd0 { Busy } Apr 11 07:42:49 milat kernel: Apr 11 07:42:49 milat kernel: ide2: reset phy, status=0x00000113, siimage_reset Apr 11 07:42:49 milat kernel: hde: no DRQ after issuing WRITE Apr 11 07:43:19 milat kernel: ide2: reset timed-out, status=0xd8 Apr 11 07:43:20 milat kernel: hde: status timeout: status=0xd8 { Busy } Apr 11 07:43:20 milat kernel: Apr 11 07:43:20 milat kernel: ide2: reset phy, status=0x00000113, siimage_reset Apr 11 07:43:20 milat kernel: hde: drive not ready for command Apr 11 07:43:51 milat kernel: t: I/O error, dev 21:02 (hde), sector 6183724 Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), sector 6183726 Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), sector 6183728 Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), sector 6183730 Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde),
Quoted 9 lines
sector 6183732
...-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Andre Hedrick
LAD Storage Consulting Group
Quoted 4 lines · Andre Hedrick
Gurr!!!!!!!
These drives were not to make it to market in the commom purchase marketspace!
Do you mean to say that the problem lies in the Seagate drives, not in the SiI 3112 controller and/or its driver code?
I'm seeing SATA as a common component on quite a few motherboards, and am definitely seeing SATA drives in the retail channel. In my experience, all of these pieces work flawlessly under Win2k and XP... would love for them to do the same under Linux.
Quoted 3 lines
This is not a fun one to fix!
This is all I can say for now :-(
Why no fun? Why can't you say more? We would really appreciate more specifics when you can. If the problem lies with Seagate, I'd be happy to press the issue with them.
--Josh