linux-kernel - Re: [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <FE56076A-03A5-429C-A9A0-BBF2CEAA5DA8@develooper.com>
Date:	Thu, 22 Feb 2007 16:21:41 -0800
From:	Ask Bjørn Hansen <ask@...elooper.com>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	Jeff Garzik <jeff@...zik.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-ide@...r.kernel.org, Andrew Morton <akpm@...l.org>,
	Tejun Heo <htejun@...il.com>,
	"Eric D. Mudama" <edmudama@...il.com>
Subject: Re: [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver


On Feb 22, 2007, at 4:18 PM, Robert Hancock wrote:

>> model and (partial) firmware revision of the drives:
>> Maxtor 7V300F0  VA11
>> Maxtor 7B300S0  BANC
>> Until I disabled NCQ I got gazillions of messages like the ones  
>> below and absymal performance.
>>   - ask
>> ata5: spurious interrupt (irq_stat 0x8 active_tag -84148995  
>> sactive 0xf)
>
> Sounds like those are some that we should be blacklisting as well,  
> unless Eric has a good reason why not (CCing). Can you provide the  
> full firmware revision strings from those drives, i.e. from "hdparm  
> -I"?

ATA device, with non-removable media
         Model Number:       Maxtor 7B300S0
         Firmware Revision:  BANC1B70

ATA device, with non-removable media
         Model Number:       Maxtor 7V300F0
         Firmware Revision:  VA111630


  - ask

-- 
http://develooper.com/ - http://askask.com/


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/