Bug 464039

+++ This bug was initially created as a clone of Bug #456078 +++

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>

--- Additional comment from bmr on 2008-07-21 08:37:59 EDT ---

This is also anecdotaly affecting drives from other vendors.


--- Additional comment from bmr on 2008-07-21 08:38:49 EDT ---

Related to bug 453808 for the same drive model:

qc timeout probing TEAC DV-28E-V CD/DVD drive on SATA/PATA bridge

--- Additional comment from bmr on 2008-07-21 13:25:35 EDT ---

Increasing sev/prio on these bugs as we're starting to see a lot of reports from
customers hitting this.


--- Additional comment from alan on 2008-07-23 15:44:40 EDT ---

I'm happy with that proposed patch 


--

I'm just going to re-diff this patch for the current EL5 code base and attach it to this bugzilla.

I don't believe this will make it for 5.3 so will propose for 5.4