On 10/26/2009 10:20 AM, Philippe De Muyter wrote:
Hi,
I just encountered a problem with write-access to a batch of CF cards
(KINGSTON TECHNOLOGY 4GB COMPACT FLASH CF/4GB
3.3V/5V 9904321 - 006.AOOLF 4449081 - 1219643 X001 ASSY IN TAIWAN (c) 2008)
connected to a PC-CARD / PCMCIA interface, with the following error messages :
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE
After testing with different bigger values for the WAIT_DRQ timeout value,
the problem disappeared. I had success with WAIT_DRQ = 500ms, then with
WAIT_DRQ = 300ms. I then tested with WAIT_DRQ = 200ms, but the problem
reappeared. So I kept the 300ms value.
Signed-off-by: Philippe De Muyter<phdm@xxxxxxxxx>
diff -r a145344bb228 include/linux/ide.h
--- a/include/linux/ide.h Thu Oct 22 08:28:28 2009 +0900
+++ b/include/linux/ide.h Mon Oct 26 16:51:23 2009 +0100
@@ -125,8 +125,8 @@
* Timeouts for various operations:
*/
enum {
- /* spec allows up to 20ms */
- WAIT_DRQ = HZ / 10, /* 100ms */
+ /* spec allows up to 20ms, but some CF cards need more than 200ms */
+ WAIT_DRQ = 3 * HZ / 10, /* 300ms */
/* some laptops are very slow */
WAIT_READY = 5 * HZ, /* 5s */
/* should be less than 3ms (?), if all ATAPI CD is closed at boot */
This has come up before:
http://marc.info/?l=linux-ide&m=123064513313466&w=2
I think this timeout should not even exist. libata has no such timeout
(only the overall command completion timeout), and I can't find any
reference in current ATA specs to the device being required to raise DRQ
in any particular amount of time.
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
