From: "Stuart MacDonald" <stuartm@connecttech.com>
To: 'Aaron Lehmann' <aaronl@vitelus.com>, 'Jim Paris' <jim@jtan.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: RE: Silent corruption on AMD64
Date: Mon, 2 Apr 2007 09:30:18 -0400 [thread overview]
Message-ID: <003c01c7752b$0e678fa0$294b82ce@stuartm> (raw)
In-Reply-To: <20070401043905.GV15189@vitelus.com>
From: On Behalf Of Aaron Lehmann
> I've been able to narrow it down to the Realtek Ethernet card. I can't
> reproduce the problem using onboard Ethernet, whereas the Realtek card
> causes trouble in any slot. However, I still don't know whether it's a
> hardware or software issue, or whether it's caused directly or
> indirectly by the Realtek card.
I had a similar issue recently:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=223216
I recommend trying Doug Ledford's memtest script:
http://people.redhat.com/dledford/memtest.html
It helped me prove the issue was the hardware and not something else.
..Stu
WARNING: multiple messages have this Message-ID (diff)
From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "'Aaron Lehmann'" <aaronl@vitelus.com>, "'Jim Paris'" <jim@jtan.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-ide@vger.kernel.org>
Subject: RE: Silent corruption on AMD64
Date: Mon, 2 Apr 2007 09:30:18 -0400 [thread overview]
Message-ID: <003c01c7752b$0e678fa0$294b82ce@stuartm> (raw)
In-Reply-To: <20070401043905.GV15189@vitelus.com>
From: On Behalf Of Aaron Lehmann
> I've been able to narrow it down to the Realtek Ethernet card. I can't
> reproduce the problem using onboard Ethernet, whereas the Realtek card
> causes trouble in any slot. However, I still don't know whether it's a
> hardware or software issue, or whether it's caused directly or
> indirectly by the Realtek card.
I had a similar issue recently:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=223216
I recommend trying Doug Ledford's memtest script:
http://people.redhat.com/dledford/memtest.html
It helped me prove the issue was the hardware and not something else.
..Stu
next prev parent reply other threads:[~2007-04-02 13:30 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
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 ` Stuart MacDonald [this message]
2007-04-02 13:30 ` Silent corruption on AMD64 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='003c01c7752b$0e678fa0$294b82ce@stuartm' \
--to=stuartm@connecttech.com \
--cc=aaronl@vitelus.com \
--cc=jim@jtan.com \
--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.