From: Dax Kelson <dax@gurulabs.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
Date: Thu, 14 Dec 2006 16:39:36 -0700 [thread overview]
Message-ID: <1166139576.3307.20.camel@mentorng.gurulabs.com> (raw)
In-Reply-To: <4570CF26.8070800@scientia.net>
On Sat, 2006-12-02 at 01:56 +0100, Christoph Anton Mitterer wrote:
> Hi.
>
> Perhaps some of you have read my older two threads:
> http://marc.theaimsgroup.com/?t=116312440000001&r=1&w=2 and the even
> older http://marc.theaimsgroup.com/?t=116291314500001&r=1&w=2
>
> The issue was basically the following:
> I found a severe bug mainly by fortune because it occurs very rarely.
> My test looks like the following: I have about 30GB of testing data on
> my harddisk,... I repeat verifying sha512 sums on these files and check
> if errors occur.
> One test pass verifies the 30GB 50 times,... about one to four
> differences are found in each pass.
This sounds very similar to a corruption issue I was experiencing on my
nforce4 based system. After replacing most of my hardware to no avail, I
discovered that if increased the voltage for my RAM chips the corruption
went away. Note that I was not overclocking at all.
Worth a try.
Dax Kelson
next prev parent reply other threads:[~2006-12-15 0:12 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 0:56 Christoph Anton Mitterer
2006-12-02 1:15 ` Erik Andersen
2006-12-02 1:28 ` Christoph Anton Mitterer
2006-12-02 5:17 ` Chris Wedgwood
2006-12-02 12:10 ` Christoph Anton Mitterer
[not found] ` <20061202111644.GF9995@vianova.fi>
2006-12-08 2:16 ` Christoph Anton Mitterer
2006-12-02 11:00 ` Karsten Weiss
2006-12-02 11:37 ` Alan
2006-12-02 11:39 ` Christoph Anton Mitterer
2006-12-13 18:52 ` Christoph Anton Mitterer
2006-12-13 19:56 ` Karsten Weiss
2006-12-13 20:11 ` Christoph Anton Mitterer
2006-12-14 9:34 ` Chris Wedgwood
2007-01-15 22:26 ` Christoph Anton Mitterer
2006-12-03 1:17 ` data corruption with nvidia chipsets and IDE/SATA drives Kurtis D. Rader
2006-12-03 3:35 ` Kurtis D. Rader
2006-12-03 14:17 ` Steffen Moser
2006-12-04 1:58 ` data corruption with nvidia nForce 4 " Kurtis D. Rader
2006-12-04 12:47 ` Alan
2006-12-05 6:00 ` data corruption with nvidia " Kurtis D. Rader
2006-12-06 11:11 ` Christian
2006-12-06 21:25 ` Chris Wedgwood
2006-12-14 23:39 ` Dax Kelson [this message]
[not found] <Pine.LNX.4.64.0612021202000.2981@addx.localnet>
2006-12-11 9:24 ` data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?! Karsten Weiss
2006-12-13 19:18 ` Christoph Anton Mitterer
2006-12-13 19:53 ` Chris Wedgwood
2006-12-13 20:34 ` Karsten Weiss
2006-12-14 9:22 ` Muli Ben-Yehuda
2006-12-23 2:04 ` Christoph Anton Mitterer
2006-12-23 2:56 ` John A Chaves
2006-12-23 3:26 ` Christoph Anton Mitterer
2006-12-13 19:20 ` Christoph Anton Mitterer
2006-12-13 19:54 ` Chris Wedgwood
2006-12-13 19:57 ` Christoph Anton Mitterer
2006-12-13 22:39 ` Lennart Sorensen
2006-12-13 23:00 ` Christoph Anton Mitterer
2006-12-13 19:53 ` Erik Andersen
2006-12-13 19:59 ` Karsten Weiss
2006-12-13 20:02 ` Christoph Anton Mitterer
2006-12-13 20:29 ` Erik Andersen
2006-12-13 20:32 ` Christoph Anton Mitterer
2006-12-13 23:33 ` Christoph Anton Mitterer
2006-12-14 9:24 ` Muli Ben-Yehuda
2006-12-14 19:23 ` Christoph Anton Mitterer
2006-12-14 9:23 ` Muli Ben-Yehuda
2006-12-14 9:52 ` Erik Andersen
2006-12-14 9:56 ` Muli Ben-Yehuda
2007-01-03 15:02 ` Christoph Anton Mitterer
2007-01-04 13:04 ` Christoph Anton Mitterer
2006-12-15 15:57 Paul Slootman
[not found] <fa.E9jVXDLMKzMZNCbslzUxjMhsInE@ifi.uio.no>
2007-01-03 23:41 ` Robert Hancock
2007-01-15 22:56 ` Christoph Anton Mitterer
2007-01-15 23:05 ` Christoph Anton Mitterer
2007-01-16 0:23 ` Robert Hancock
2007-01-16 13:54 ` Christoph Anton Mitterer
2007-01-16 14:26 ` Robert Hancock
2007-03-22 12:32 ` Christoph Anton Mitterer
2007-03-22 14:48 Dan Halbert
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=1166139576.3307.20.camel@mentorng.gurulabs.com \
--to=dax@gurulabs.com \
--cc=calestyo@scientia.net \
--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
all inboxes | Powered by JetHome®