From: Dax Kelson <dax@gurulabs.com>
To: linux-kernel@vger.kernel.org
Cc: Jeff Garzik <jeff@garzik.org>
Subject: Warning - Maxtor SATA II and Nvidia nforce4
Date: Wed, 15 Mar 2006 15:31:27 -0700 [thread overview]
Message-ID: <1142461887.2521.44.camel@station14.example.com> (raw)
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.
After being suspected for over a year, it was acknowledged just in the
last few weeks, see:
http://maxtor.custhelp.com/cgi-bin/maxtor.cfg/php/enduser/std_adp.php?p_faqid=2685
(there is a list of affected HD model numbers and HD firmware versions)
If it is possible to determine the firmware version, maybe some printk
warnings could be generated.
Long version
=============
About a year ago I got a new home uber system all decked out.
AMDFX-55
Nforce4 SLI motherboard
2GB RAM
300GB Maxtor SATA II HDD x2 (model 6B300S with firmware BANC1B70)
Off and on I have experienced the following problems:
* kernel panics
* freezes
* insta-reboots
* on-board RAID (nforce fake raid) de-syncing
* LCD blinking on and off (most common symptom for me)
* segfaults and application crashes
The problems were not continuous and would seemingly erratically
appear.
My memory tested fine with memtest86+ over repeated tests the past 12
months. I RMA'd my video cards and got a new motherboard. I was
contemplating swapping my CPU when I finally did a Google search on
"Maxtor nforce4" and my eyes were opened. Pages and pages of posts in
hundreds of different forums.
Dax Kelson
next reply other threads:[~2006-03-15 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 22:31 Dax Kelson [this message]
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
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=1142461887.2521.44.camel@station14.example.com \
--to=dax@gurulabs.com \
--cc=jeff@garzik.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.