Re: [Bug #14922] 2.6.32 seemed to have broken nVidia MCP7A sata controller

[Robert Hancock <hancockrwd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

On Tue, Dec 29, 2009 at 9:28 AM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.31 and 2.6.32.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32.  Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=14922
> Subject         : 2.6.32 seemed to have broken nVidia MCP7A sata controller
> Submitter       : Mike Cui <cuicui-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date            : 2009-12-19 6:13 (11 days old)
> References      : http://marc.info/?l=linux-ide&m=126120323407742&w=4
> Handled-By      : Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
>                  Robert Hancock <hancockrwd@gmail.com>

Yes, FPDMA auto-activate optimization was introduced for AHCI in
2.6.32 and it appears it doesn't work quite right with either the
reporter's AHCI controller or their drive. I believe they were going
to try the drive with an Intel controller to see if it worked there.

It would be useful if we could get other success/failure reports with
either the particular drive, WDC WD800ADFS-75SLR2 (or at least other
WD Raptor ADFS-series) on other AHCI controllers, or other drives
which have AA support on the MCP7A chipset. One of the two needs
blacklisting for AA support. I'm leaning towards the controller since
other WD drives with AA support work fine on Intel AHCI.