linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Dax Kelson <dax@gurulabs.com>
Cc: linux-kernel@vger.kernel.org,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Warning - Maxtor SATA II and Nvidia nforce4
Date: Wed, 15 Mar 2006 17:47:10 -0500	[thread overview]
Message-ID: <4418996E.6010808@garzik.org> (raw)
In-Reply-To: <1142461887.2521.44.camel@station14.example.com>


Ah, I see this made it to LKML :)

Dax Kelson wrote:
> Short version
> ==============
> Nvidia Nforce4 chipset with Maxtor SATA II drives with certain firmware
> revisions cause data corruption and system instability when under
> moderate to heavy I/O load.

I'm a bit suspicious of this.

Looking at the link, there are three problem areas and two problem blame 
targets implied:

	Data corruption	-> blame nvidia driver
	NCQ		-> blame nvidia driver
	Detection	-> blame maxtor firmware

The first one likely applies to the Windows driver not Linux's sata_nv, 
and thus irrelevant here.  The second one OBVIOUSLY applies only to 
Windows, since sata_nv (and libata itself) don't yet enable NCQ.  The 
third one could potentially apply to Linux.  Lastly, your mention of 
"nforce fake raid" almost certainly indicates Windows or proprietary 
drivers.

Therefore, I ask:
* are you reporting a only drive detection problem?
* why are you reporting unrelated Windows problems to a Linux list?
* if you are indeed reporting a problem on Linux, where is the kernel 
and driver version info, as requested in REPORTING-BUGS?
* and can you provide such info *and reproduce the problems* without 
proprietary drivers loaded?

Your email is just a list of highly general symptoms.  Your link seems 
to indicate two NV driver bugs on Windows, and a Maxtor firmware upgrade 
for undescribed detection problems.

My recommended action for users is:
1) Avoid Windows.
2) Don't panic.

	Jeff



       reply	other threads:[~2006-03-15 22:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1142461887.2521.44.camel@station14.example.com>
2006-03-15 22:47 ` Jeff Garzik [this message]
2006-03-15 23:23   ` Warning - Maxtor SATA II and Nvidia nforce4 Dax Kelson
2006-03-16  6:30   ` Sander

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=4418996E.6010808@garzik.org \
    --to=jeff@garzik.org \
    --cc=dax@gurulabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).