Bug 246352 - Maxtor 6B200M0 can't do NCQ and should be blacklisted
Summary: Maxtor 6B200M0 can't do NCQ and should be blacklisted
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 7
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-30 21:00 UTC by David Juran
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version: kernel-2.6.22.1-41.fc7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-08-02 11:44:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Juran 2007-06-30 21:00:52 UTC
Description of problem:

As discussed in Bug 232811, around comment 25, the Maxtor 6B200M0 can't do NCQ
and needs to be blacklisted. I suggest the entry

{ "Maxtor 6B200M0",     NULL,           ATA_HORKAGE_NONCQ }

should be entered into ata_blacklist_entry ata_device_blacklist in
drivers/ata/libata-core.c

Version-Release number of selected component (if applicable):
kernel-2.6.21-1.3228.fc7

Comment 1 Chuck Ebbert 2007-07-02 22:31:56 UTC
Upstream kernel 2.6.22 has:

"Maxtor 6B200M0",	"BANC1B10"

Is this the correct entry for the drive?


Comment 2 Chuck Ebbert 2007-07-05 20:56:45 UTC
"Maxtor 6B200M0",	"BANC1B10" added to the next kernel.

Reporter still hasn't confirmed this is the exact drive, though.

Comment 3 David Juran 2007-07-06 09:52:49 UTC
Sorry for the delay, 

No, the revision that should be blacklisted is "BANC1BM0" so the correct line
will probably be 
{"Maxtor 6B200M0",      "BANC1BM0",     ATA_HORKAGE_NONCQ }

Comment 4 Chuck Ebbert 2007-07-06 18:46:37 UTC
Asked upstream if maybe all revisions of this drive should be blacklisted.


Comment 5 David Juran 2007-08-02 11:44:21 UTC
The Maxtor 6B200M0 BANC1BM0 has been blacklisted in kernel-2.6.22.1-41.fc7. 
Thanks (-:


Note You need to log in before you can comment on or make changes to this bug.