linux-kernel - Re: [PATCH] ahci: disable FPDMA auto-activate optimization on NVIDIA AHCI

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: <4B772F74.1030509@garzik.org>
Date:	Sat, 13 Feb 2010 18:02:12 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Robert Hancock <hancockrwd@...il.com>
CC:	linux-kernel <linux-kernel@...r.kernel.org>,
	ide <linux-ide@...r.kernel.org>, Mike Cui <cuicui@...il.com>,
	Peer Chen <pchen@...dia.com>, Allen Martin <AMartin@...dia.com>
Subject: Re: [PATCH] ahci: disable FPDMA auto-activate optimization on NVIDIA
 	AHCI

On 02/13/2010 05:53 PM, Robert Hancock wrote:
> On Sat, Feb 13, 2010 at 4:46 PM, Jeff Garzik<jeff@...zik.org>  wrote:
>> On 01/26/2010 11:33 PM, Robert Hancock wrote:
>>>
>>> Mike Cui reported that his system with an NVIDIA MCP79 (aka MCP7A) chipset
>>> stopped working with 2.6.32. The problem appears to be that 2.6.32 now
>>> enables
>>> the FPDMA auto-activate optimization in the ahci driver. The drive works
>>> fine
>>> with this enabled on an Intel AHCI so this appears to be a chipset bug.
>>> Since MCP79 is a fairly recent NVIDIA chipset and we don't have any info
>>> on
>>> whether any other NVIDIA chipsets have this issue, disable FPDMA AA
>>> optimization
>>> on all NVIDIA AHCI controllers for now.
>>>
>>> Should address http://bugzilla.kernel.org/show_bug.cgi?id=14922
>>>
>>> Signed-off-by: Robert Hancock<hancockrwd@...il.com>
>>>
>>> ---
>>>
>>> Mike, can you test this out and make sure this resolves the problem for
>>> you?
>>
>> Sigh...   we never did hear back from Mike or NVIDIA on this one, did we?
>>   I've been watching for a response, and haven't seen one to date.
>
> No, I haven't seen a response. It's pretty apparent it should fix the
> problem based on earlier testing, but it would be nice to find out for
> sure which chipsets this affects.

Yep, that's my main concern...  being overly aggressive and zapping it 
on all NVIDIA chipsets, even future ones.

	Jeff




--
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/