mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Prakash Punnoor <prakash@punnoor.de>
To: "Peer Chen" <pchen@nvidia.com>
Cc: "Robert Hancock" <hancockr@shaw.ca>,
	"kuan luo" <kuanluo@gmail.com>,
	linux-kernel@vger.kernel.org, jeff@garzik.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 18:09:00 +0200	[thread overview]
Message-ID: <200706271809.03814.prakash@punnoor.de> (raw)
In-Reply-To: <15F501D1A78BD343BE8F4D8DB854566B15830128@hkemmail01.nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]

Am Mittwoch 27 Juni 2007 schrieb Peer Chen:
> 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.

Out of interest I tested the patch again with my Maxtor drive I mentioned in 
the other thread. Ths time it got worse. I couldn't boot anymore, ie init 
starts some services and then dies at random places as if corrupt data was 
transfered. With the previous patch the system worked, except the port 
resets.

Anyway, I'll ask Maxtor or rather Seagate to fix their firmware pointing at 
your diagnosis.

bye,
-- 
(°=                 =°)
//\ Prakash Punnoor /\\
V_/                 \_V

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-06-27 16:09 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 ` Robert Hancock
2007-06-27  8:15   ` Peer Chen
2007-06-27  8:34     ` Jeff Garzik
2007-06-27 16:09     ` Prakash Punnoor [this message]
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=200706271809.03814.prakash@punnoor.de \
    --to=prakash@punnoor.de \
    --cc=akpm@linux-foundation.org \
    --cc=hancockr@shaw.ca \
    --cc=jeff@garzik.org \
    --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

all inboxes | Powered by JetHome®