Jens Axboe wrote:
Robert Hancock wrote:..+ /* The following blacklist entries are taken from the Windows + driver .inf files for the Silicon Image 3124 and 3132. */ + { "Maxtor 7B250S0", "BANC1B70", ATA_HORKAGE_NONCQ, }, + { "HTS541060G9SA00", "MB3OC60D", ATA_HORKAGE_NONCQ, }, + { "HTS541080G9SA00", "MB4OC60D", ATA_HORKAGE_NONCQ, }, + { "HTS541010G9SA00", "MBZOC60D", ATA_HORKAGE_NONCQ, },Do we have information that these drives fail on non-SiI controllers? Sometimes the problem can be related to a single family of controllers.I don't know about the Hitachi's, but the Maxtor with that firmware is definitely broken. It _appeared_ to work if the depth was limited to 4, but I didn't test it long enough to be absolutely certain. So the safest is indeed to blacklist it.
Yes, broken on the Silicon Image controllers for sure. But what type of controller did you observe the failures on, Jens ? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver
- From: Robert Hancock <[email protected]>
- Re: [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver
- From: Jeff Garzik <[email protected]>
- Re: [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver
- From: Jens Axboe <[email protected]>
- [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver
- Prev by Date: Re: no backlight on radeon after recent kernel "upgrade"s
- Next by Date: Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3
- Previous by thread: Re: [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver
- Next by thread: Re: [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver
- Index(es):
 |