From: Jeff Garzik <jeff@garzik.org>
To: Peer Chen <pchen@nvidia.com>
Cc: Robert Hancock <hancockr@shaw.ca>, kuan luo <kuanluo@gmail.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Kuan Luo <kluo@nvidia.com>
Subject: Re: [PATCH] ata: Add the SW NCQ support to sata_nv for MCP51/MCP55/MCP61
Date: Wed, 27 Jun 2007 04:34:37 -0400 [thread overview]
Message-ID: <4682211D.4040808@garzik.org> (raw)
In-Reply-To: <15F501D1A78BD343BE8F4D8DB854566B15830128@hkemmail01.nvidia.com>
Peer Chen wrote:
> We did the many test with the new version driver and didn't encounter
> that problem, but in certain cases, DMASETUP command packets from drive
> to the controller are corrupted, and the controller issues an R_ERR to
> the drive. Drives that comply with SATA spec will re-transmit the
> corrupted packet and normal operation continues. However, some Maxtor
> NCQ drives do not re-transmit the DMASETUP command packet, resulting in
> software timeout for this command. So if you are using the Maxtor HD and
> meet this problem,please don't enable the NCQ function.
Users should not be expected to know those details, nor be forced to
suffer discovering this in the field (over and over again for each
customer).
We have a list of problem devices ata_device_blacklist[] in
drivers/ata/libata-core.c that should be modified to note each drive
where NCQ should never be used.
Jeff
next prev parent reply other threads:[~2007-06-27 8:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.5TBvnXzjCgAIfcuKOLBWeXi+y5I@ifi.uio.no>
2007-06-27 5:06 ` [PATCH] ata: Add the SW NCQ support to sata_nv for MCP51/MCP55/MCP61 Robert Hancock
2007-06-27 8:15 ` Peer Chen
2007-06-27 8:34 ` Jeff Garzik [this message]
2007-06-27 16:09 ` Prakash Punnoor
2007-07-06 8:31 kuan luo
2007-07-07 7:33 ` Zoltan Boszormenyi
2007-07-09 2:48 ` Peer Chen
2007-07-09 16:28 ` Prakash Punnoor
-- strict thread matches above, loose matches on Subject: below --
2007-06-27 10:51 Zoltan Boszormenyi
2007-07-03 22:31 ` Zoltan Boszormenyi
2007-07-05 18:53 ` Bill Davidsen
2007-06-27 3:04 kuan luo
2007-06-27 5:26 ` Andrew Morton
2007-06-27 9:09 ` Kuan Luo
2007-06-27 9:21 ` Andrew Morton
2007-06-27 10:17 ` Kuan Luo
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=4682211D.4040808@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=hancockr@shaw.ca \
--cc=kluo@nvidia.com \
--cc=kuanluo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pchen@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox