Description of problem: Some TEAC drives take a long time to return to non-Busy status following an IDENTIFY command (>=6ms), causing following messages to be logged: 08:20:36 hex kernel: hda: irq timeout: status=0xd0 { Busy } 08:20:36 hex kernel: hda: irq timeout: error=0x00 08:20:36 hex kernel: hda: ATAPI reset complete 08:20:36 hex kernel: VFS: busy inodes on changed media Version-Release number of selected component (if applicable): How reproducible: Infrequently but depends on drive/usage. Some users report the drives to be unusable while others see only infrequent failures. Steps to Reproduce: 1. cat /proc/ide/<drive>/identify Actual results: 22 failures in 60,000 accesses: kernel: hda: task_in_intr: status=0xd0 { Busy } kernel: hda: task_in_intr: error=0xd0LastFailedSense 0x0d Expected results: No error logged. Drive usable as normal. Additional info: Reported upstream as kernel bug 10887: http://bugzilla.kernel.org/show_bug.cgi?id=10887 And fixed in commit f54feafa6d47d0aa1a96adefdc763b708b02f94f: Author: Bartlomiej Zolnierkiewicz <bzolnier> Date: Fri Jun 20 20:53:33 2008 +0200 ide: increase timeout in wait_drive_not_busy() Some ATAPI devices take longer than the current max timeout value to become ready (i.e. TEAC DV-W28ECW takes 6 ms) so increase the timeout value to 10 ms. This fixes kernel.org bugzilla bug #10887: http://bugzilla.kernel.org/show_bug.cgi?id=10887 Reported-by: Masanari Iida <standby24x7> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier>
Created attachment 312253 [details] Patch increasing timeout in wait_drive_not_busy
This is also anecdotaly affecting drives from other vendors.
Related to bug 453808 for the same drive model: qc timeout probing TEAC DV-28E-V CD/DVD drive on SATA/PATA bridge
I'm happy with that proposed patch
Updating PM score.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Created attachment 336467 [details] RHEL4 fix for this issue
HP has begun some validation of the patch. Will post results shortly.
(In reply to comment #23) > HP has begun some validation of the patch. Will post results shortly. Are the test results available?
Here are our results for now. We are in the middle of the i686 testing. So far we have completed testing x86_64 bz kernel. Test was successful. None of the following messages were reported by "dmesg": 08:20:36 hex kernel: hda: irq timeout: status=0xd0 { Busy } 08:20:36 hex kernel: hda: irq timeout: error=0x00 08:20:36 hex kernel: hda: ATAPI reset complete 08:20:36 hex kernel: VFS: busy inodes on changed media Currently we are running the same test on i686 kernel. Test has successfully run for 30+ minutes and there are no "hda" related messages by "dmesg" so far.
The test on i686 bz kernel ran successfully for over an hour. "dmesg" did not report "had" timeout/error. Thank you, Sandy
Committed in 86.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
~~ Attention Partners! Snap 3 Released ~~ RHEL 4.8 Snapshot 3 has been released on partners.redhat.com. There should be a fix present that resolves this bug. If you encounter any issues, please set the bug back to the ASSIGNED state and describe the issues you encountered. If you have found a NEW bug, clone this bug and describe the issues you encountered. Further questions can be directed to your Red Hat Partner Manager. If you have VERIFIED the bug fix. Please select your PartnerID from the Verified field above. Please leave a comment with your test results details. Include which arches tested, package version and any applicable logs.
~~ Attention! Snap 4 Released ~~ RHEL 4.8 Snapshot 4 has been released on partners.redhat.com. There should be a fix present that resolves this bug. There's not much more time to test. Please report back results ASAP. If you encounter any issues, please set the bug back to the ASSIGNED state and describe the issues you encountered. If you have found a NEW bug, clone this bug and describe the issues you encountered. Further questions can be directed to your Red Hat Partner Manager. If you have VERIFIED the bug fix. Please select your PartnerID from the Verified field above. Please leave a comment with your test results details. Include which arches tested, package version and any applicable logs.
This patch has already had a fair amount of testing mileage both here and upstream. It'd still be nice to get it verified in 86.EL though.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-1024.html