All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Mike Cui <cuicui@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.32 seemed to have broken nVidia MCP7A sata controller
Date: Sat, 19 Dec 2009 17:55:18 -0500	[thread overview]
Message-ID: <4B2D59D6.30008@garzik.org> (raw)
In-Reply-To: <7c8826910912191437k4e1d93bap12874a6d6e0046d3@mail.gmail.com>

On 12/19/2009 05:37 PM, Mike Cui wrote:
> Thanks, changing that one line fixed it. I can try to find an intel
> motherboard sometime next week to see if it's the drive or the
> controller.
>
> On Sat, Dec 19, 2009 at 10:35 AM, Robert Hancock<hancockrwd@gmail.com>  wrote:
>> Mike, can you try and revert that patch, or else just change this line in
>> drivers/ata/ahci.c:
>>
>>                 pi.flags |= ATA_FLAG_NCQ | ATA_FLAG_FPDMA_AA;
>>
>> to
>>
>>                 pi.flags |= ATA_FLAG_NCQ;
>>
>> and rebuild and see if it works better?


Thanks for that confirmation.  And yeah, it would definitely help if we 
can narrow that down to either the drive or the controller.

	Jeff




  reply	other threads:[~2009-12-19 22:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19  6:13 2.6.32 seemed to have broken nVidia MCP7A sata controller Mike Cui
2009-12-19  7:29 ` Jeff Garzik
2009-12-19 18:35   ` Robert Hancock
2009-12-19 22:37     ` Mike Cui
2009-12-19 22:55       ` Jeff Garzik [this message]
2009-12-27 21:52       ` Robert Hancock
2010-01-21 23:48         ` Mike Cui
2010-01-22  0:36           ` Robert Hancock
2010-01-26  9:43             ` Mike Cui

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B2D59D6.30008@garzik.org \
    --to=jeff@garzik.org \
    --cc=cuicui@gmail.com \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.