Jeff Garzik wrote:
Robert Hancock wrote:
This adds some NCQ blacklist entries taken from the Silicon Image
3124/3132
Windows driver .inf files. There are some confirming reports of problems
with these drives under Linux (for example
http://lkml.org/lkml/2007/3/4/178)
so let's disable NCQ on these drives.
Signed-off-by: Robert Hancock <hancockr@xxxxxxx>
--- linux-2.6.21-rc5-git9/drivers/ata/libata-core.c 2007-04-02
21:03:29.000000000 -0600
+++ linux-2.6.21-rc5-git9edit/drivers/ata/libata-core.c 2007-04-02
21:26:23.000000000 -0600
@@ -3363,6 +3363,11 @@ static const struct ata_blacklist_entry {
"Maxtor 6L250S0", "BANC1G10", ATA_HORKAGE_NONCQ },
/* NCQ hard hangs device under heavier load, needs hard power
cycle */
{ "Maxtor 6B250S0", "BANC1B70", ATA_HORKAGE_NONCQ },
+ /* Blacklist entries taken from Silicon Image 3124/3132
+ Windows driver .inf file - also several Linux problem reports */
+ { "HTS541060G9SA00", "MB3OC60D", ATA_HORKAGE_NONCQ, },
+ { "HTS541080G9SA00", "MB4OC60D", ATA_HORKAGE_NONCQ, },
+ { "HTS541010G9SA00", "MBZOC60D", ATA_HORKAGE_NONCQ, },
The thread you link to seems like an irq problem, especially because it
worked in 2.6.20 and prior?
Jeff
According to this post:
http://lkml.org/lkml/2007/3/9/475
with 2.6.21-rc3, it started working after the kernel disabled NCQ
because of too many errors. That seems to point away from it being an
IRQ problem, as you'd expect it to not work at all. I don't expect the
interrupts would be handled any differently between NCQ and non-NCQ
commands. However, apparently disabling ACPI also prevents the problem,
which does seem a bit odd.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@xxxxxxxxxxxxx
Home Page: http://www.roberthancock.com/
-
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
