From: Aaron Lehmann <aaronl@vitelus.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Silent corruption on AMD64
Date: Sat, 31 Mar 2007 20:20:42 -0700 [thread overview]
Message-ID: <20070401032042.GU15189@vitelus.com> (raw)
In-Reply-To: <20070331195236.7c818ed5.akpm@linux-foundation.org>
On Sat, Mar 31, 2007 at 07:52:36PM -0700, Andrew Morton wrote:
> Are you able to provide us with some before-and-after data so we
> can see this corruption.
>
> See, if it's dropped-bits or shifted-data or eight-byte-aligned
> kernel addresses or whatever, that helps us generate theories..
Sure.
I created a large file containing the repeating ASCII string "abcdefgh",
and subjected it to the corruption I described earlier. The correct
hex sequence is:
61 62 63 64 65 66 67 68
Here were some of the permutations that I found in corrupted copies:
61 62 63 64 92 57 5C 0A
61 62 63 64 A2 2D E1 C7
61 62 63 64 11 38 0E B6
61 62 63 64 57 B1 EE 1F
61 62 63 64 E0 3D 10 21
61 62 63 64 97 E1 C0 F5
I did not observe any errors other than replacements of four-byte
blocks. These errors always started at addresses in the file that had
a remainder of 12 modulo 16 (i.e. the hex addresses always ended in
'C'). There was an average about one error per 300MB.
next prev parent reply other threads:[~2007-04-01 3:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 1:27 Silent corruption on AMD64 Aaron Lehmann
2007-04-01 2:52 ` Andrew Morton
2007-04-01 3:20 ` Aaron Lehmann [this message]
2007-04-01 3:03 ` Jim Paris
2007-04-01 4:39 ` Aaron Lehmann
2007-04-01 13:58 ` Andi Kleen
2007-04-02 17:46 ` NIC data corruption Rick Jones
2007-04-02 18:07 ` Andi Kleen
2007-04-04 5:00 ` Herbert Xu
2007-04-04 18:45 ` Silent corruption with r8169 Francois Romieu
2007-04-04 20:06 ` Aaron Lehmann
2007-04-04 20:45 ` Francois Romieu
2007-04-05 11:41 ` Andi Kleen
2007-04-02 13:30 ` Silent corruption on AMD64 Stuart MacDonald
2007-04-02 13:30 ` Stuart MacDonald
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=20070401032042.GU15189@vitelus.com \
--to=aaronl@vitelus.com \
--cc=akpm@linux-foundation.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 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.