From: "Linas Vepstas" <linasvepstas@gmail.com>
To: "John Stoffel" <john@stoffel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: amd64 sata_nv (massive) memory corruption
Date: Fri, 1 Aug 2008 22:06:33 -0500 [thread overview]
Message-ID: <3ae3aa420808012006l6832f65cmb2e5a300d60cb708@mail.gmail.com> (raw)
In-Reply-To: <18579.30533.807970.739285@stoffel.org>
2008/8/1 John Stoffel <john@stoffel.org>:
> Linas> -- system is amd64 dual core, ASUS M2N-E mobo, 4GB RAM
> Linas> Northbridge is nVidia Corporation MCP55 Memory Controller
> Linas> (rev a3)
>
> Are you running the latest BIOS? As I recall, my motherboard is an
> M2N-SLI Deluxe, which is slightly different from yours.
Its recent. I bought the thing only some number of months ago.
The basic mobo design is 2-3 years old, though, its not bleeding edge,
it was meant to be a conservative, stable, functional choice.
I'd hope that they'd have things like this debugged by now. Sigh.
> Linas> Also of note:
> Linas> -- problem was observed earlier, when system had 3GB RAM in it.
>
> What did you do to upgrade to 4gb of ram? Just pull the second pair
> of 512mb DIMMs and put in fresh 1gb DIMMs? I've got a pair of 2gb
> DIMMs in my box. I suspect you are seeing memory problems of some
> sort.
No See other email. memtest86 passes fine, the system has been in
heavy use as a compute server on large datasets. No problems at all,
spotless record. I've beeb manipulating multi-gigabyte files just fine
on the IDE disk, without any corruption at all. I can move them
around on NFS, too. They only get corrupted in the SATA disk,
where its immediate and widespread, and takes less than a minute
to occur.
> Next, I'd upgraded the BIOS to the latest release, and then reset the
> BIOS to the factory default or safe settings to see if that helps.
I'll give tht a whirl. Bios settings are still at factory defaults, I had no
reason to mess with them.
--linas
next prev parent reply other threads:[~2008-08-02 3:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 17:30 Linas Vepstas
2008-08-01 20:51 ` John Stoffel
2008-08-02 3:06 ` Linas Vepstas [this message]
2008-08-01 22:19 ` Alistair John Strachan
2008-08-02 2:51 ` Linas Vepstas
2008-08-02 20:09 ` John Stoffel
2008-08-02 22:01 ` Linas Vepstas
2008-08-03 2:41 ` John Stoffel
2008-08-03 22:23 ` Linas Vepstas
2008-08-03 22:16 ` Alan Cox
2008-08-05 17:02 ` Linas Vepstas
2008-08-05 17:21 ` Alan Cox
2008-08-06 21:33 ` Linas Vepstas
2008-08-07 2:59 ` Martin K. Petersen
2008-08-07 4:32 ` Linas Vepstas
2008-08-07 16:42 ` Martin K. Petersen
2008-08-07 17:23 ` Linas Vepstas
2008-08-07 18:53 ` John Stoffel
2008-08-07 7:45 ` Pavel Machek
2008-08-02 21:55 ` Roger Heflin
[not found] <fa.qB5d+HsAJ6G05jNoeU8Q9GV6Dow@ifi.uio.no>
[not found] ` <fa.fxlDAHxOnGgcBiOH/EOauE67ZPc@ifi.uio.no>
[not found] ` <fa.1WYUmN6FHR5yW+sXoYRFN22Y8S8@ifi.uio.no>
[not found] ` <fa.LAUkvEUlYiF69V/F8F3wigxqH9w@ifi.uio.no>
[not found] ` <fa.mXeFXYNkfZfUYPQcGwzok0IOIfY@ifi.uio.no>
[not found] ` <fa.KjbvCGbUr2JeQTcwA1/sFGIIMik@ifi.uio.no>
2008-08-04 3:22 ` Robert Hancock
2008-08-05 5:29 ` Linas Vepstas
2008-08-05 6:36 ` Robert Hancock
2008-08-05 12:29 ` Alan Cox
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=3ae3aa420808012006l6832f65cmb2e5a300d60cb708@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=john@stoffel.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
all inboxes | Powered by JetHome®