libata (pata_via) timeouts causing unusable device: the famous DRDY issue?
Hi,
since my upgrade to openSUSE 11.0, which comes with 2.6.25.4, soon
after I start using my DVD player, I get the following in the log:
May 23 21:34:04 stein klogd: ata1.00: exception Emask 0x0 SAct 0x0 SErr
0x0 action 0x2 frozen
May 23 21:34:04 stein klogd: ata1.00: cmd
a0/01:00:00:00:08/00:00:00:00:00/a0 tag 0 dma 2048 in
May 23 21:34:04 stein klogd: cdb 28 00 00 00 01 b3 00 00 01 00
00 00 00 00 00 00
May 23 21:34:04 stein klogd: res
40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
May 23 21:34:04 stein klogd: ata1.00: status: { DRDY }
May 23 21:34:04 stein klogd: ata1: soft resetting link
May 23 21:34:04 stein klogd: ata1.00: configured for UDMA/33
May 23 21:34:04 stein klogd: ata1: EH complete [...]
May 23 21:52:53 stein klogd: ata1.00: exception Emask 0x0 SAct 0x0 SErr
0x0 action 0x2 frozen
May 23 21:52:53 stein klogd: ata1.00: cmd
a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
May 23 21:52:53 stein klogd: cdb 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
May 23 21:52:53 stein klogd: res
40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
May 23 21:52:53 stein klogd: ata1.00: status: { DRDY }
May 23 21:52:53 stein klogd: ata1: soft resetting link
May 23 21:52:54 stein klogd: ata1.00: configured for PIO0
May 23 21:52:54 stein klogd: ata1: EH completeand this one repeats until I reboot and the drive becomes unusable. The process accessing the drive is stuck and not killable. I also cannot eject the drive.
The system is an ASUS A8V Deluxe, with the following controller:
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
The drive is a Lite-On/JLMS dvd reader on first channel as master:
ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15
ata1.00: ATAPI: JLMS XJ-HD163, GH5Y, max UDMA/33
It seems to be related to the drive as if I put a Plextor CDRW instead of it, I could not see the error.
Neverthless looks to be a regression as I could use this drive without any problem under openSUSE 10.3, with kernel 2.6.22.17 (and many earlier versions as I have this drive for years).
Google gave me lot of hits for similar problem, but no solution. :(
Any hint what I could do (including testing patches) is welcome.
Andras
Signature · 2 lines
Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org
Quoted 6 lines · Andras Mantia
Hi,
since my upgrade to openSUSE 11.0, which comes with 2.6.25.4, soon
after I start using my DVD player, I get the following in the log:May 23 21:34:04 stein klogd: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen May 23 21:34:04 stein klogd: ata1.00: cmd a0/01:00:00:00:08/00:00:00:00:00/a0 tag 0 dma 2048 in May 23 21:34:04 stein klogd: cdb 28 00 00 00 01 b3 00 00 01 00 00 00 00 00 00 00 May 23 21:34:04 stein klogd: res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout) May 23 21:34:04 stein klogd: ata1.00: status: { DRDY }
DRDY == device ready, and it occurs billions of times per day during normal use.
There is no "famous DRDY issue", you are simply seeing timeouts.
Have you tried all of: pci=nomsi, acpi=off, or noapic?
Jeff
Quoted 16 lines · Jeff Garzik
Quoted 5 lines · Andras Mantia
Hi,
since my upgrade to openSUSE 11.0, which comes with 2.6.25.4, soon
after I start using my DVD player, I get the following in the log:Quoted 9 lines
May 23 21:34:04 stein klogd: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen May 23 21:34:04 stein klogd: ata1.00: cmd a0/01:00:00:00:08/00:00:00:00:00/a0 tag 0 dma 2048 in May 23 21:34:04 stein klogd: cdb 28 00 00 00 01 b3 00 00 01 00 00 00 00 00 00 00 May 23 21:34:04 stein klogd: res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout) May 23 21:34:04 stein klogd: ata1.00: status: { DRDY }
Quoted 2 lines
DRDY == device ready, and it occurs billions of times per day during normal use.
That wouldn't be a problem if it would not block the drive completely and cause my load to go up to extreme values like 50 or so.
Quoted 1 line
There is no "famous DRDY issue", you are simply seeing timeouts.
Well, I found that many have this "error" and have real problems.
Quoted 2 lines
Have you tried all of: pci=nomsi, acpi=off, or noapic?
Not yet, I will try them (but as I said it worked fine before, without any such kernel options).
Andras
Signature · 2 lines
Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org
Quoted 1 line · Jeff Garzik
Have you tried all of: pci=nomsi, acpi=off, or noapic?
So far:
pci=nomsi does not help
pci=nomsi acpi=off noapic works
pci=nomsi noapic also works
I will try noapic only as well and report.
Andras
Signature · 2 lines
Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org
Quoted 10 lines · Andras Mantia
Quoted 1 line · Jeff Garzik
Have you tried all of: pci=nomsi, acpi=off, or noapic?
So far:
pci=nomsi does not help
pci=nomsi acpi=off noapic works
pci=nomsi noapic also worksI will try noapic only as well and report.
Generally you only want to use one of those...
Jeff
Quoted 4 lines · Jeff Garzik
Quoted 1 line
I will try noapic only as well and report.
Generally you only want to use one of those...
I don't know too much of the kernel's internals... Anyway, I tried and noapic only fixes the problem. It seems the issue is the same that was reported in another thread as well meantime.
Andras
Signature · 2 lines
Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org