From: Alistair John Strachan <alistair@devzero.co.uk>
To: linasvepstas@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: amd64 sata_nv (massive) memory corruption
Date: Fri, 1 Aug 2008 23:19:04 +0100 [thread overview]
Message-ID: <200808012319.05038.alistair@devzero.co.uk> (raw)
In-Reply-To: <3ae3aa420808011030weadc61fvf6f850f0a4cfcb3e@mail.gmail.com>
On Friday 01 August 2008 18:30:34 Linas Vepstas wrote:
> Hi,
>
> I'm seeing strong, easily reproducible (and silent) corruption on a
> sata-attached
> disk drive on an amd64 board. It might be the disk itself, but I
> doubt it; googling
> suggests that its somehow iommu-related but I cannot confirm this.
Nowhere do you explicitly say you have memtest86'ed the RAM. Checking 4GB of
RAM will take some time (probably several hours) but it will mostly eliminate
bad memory as the cause of the corruption.
IME these kinds of bugs are almost always bad RAM. Since the part of the RAM
that is bad may never be used by kernel code, you may experience no crashes.
This is especially true of machines with a lot of RAM. However since your
filesystem cache can easily consume all 4GB over time, you could see this kind
of corruption when copying files.
--
Cheers,
Alistair.
next prev parent reply other threads:[~2008-08-01 22:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 17:30 amd64 sata_nv (massive) memory corruption Linas Vepstas
2008-08-01 20:51 ` John Stoffel
2008-08-02 3:06 ` Linas Vepstas
2008-08-01 22:19 ` Alistair John Strachan [this message]
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=200808012319.05038.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=linasvepstas@gmail.com \
--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