linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: Dax Kelson <dax@gurulabs.com>,
	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: Thu, 16 Mar 2006 07:30:24 +0100	[thread overview]
Message-ID: <20060316063024.GB8825@favonius> (raw)
In-Reply-To: <4418996E.6010808@garzik.org>

Jeff Garzik wrote (ao):
> Ah, I see this made it to LKML :)

I'm not the OP. The Maxtor notice is a few months old already.

> 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.

Last december I requested new firmware for my drives. Maxtor called me
and asked if I did have any problems. I did not, but just wanted to fix
the problem before I would notice any.

The Maxtor guy then told me that harddisk firmware upgrades are best not
to be done if not needed, and asked what operating system I run (answer:
Linux). He said that the problems only exists with Windows, and that
Linux should be ok.

In fact, I have yet to see a problem with my sata Maxtor disks connected
to the onboard nForce4 controller. This supports Jeff Garziks story.

I do notice that the nForce4 controller most of the times fails to
detect some of the drives (seems random) on a reboot. A powerdown and
fresh boot lets the controller detect all disks again.

	Sander

-- 
Humilis IT Services and Solutions
http://www.humilis.net

      parent reply	other threads:[~2006-03-16  6:30 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 ` Warning - Maxtor SATA II and Nvidia nforce4 Jeff Garzik
2006-03-15 23:23   ` Dax Kelson
2006-03-16  6:30   ` Sander [this message]

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=20060316063024.GB8825@favonius \
    --to=sander@humilis.net \
    --cc=dax@gurulabs.com \
    --cc=jeff@garzik.org \
    --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).