From: Brad Campbell <brad@wasp.net.au>
To: William Knop <wknop@andrew.cmu.edu>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: libata badness
Date: Tue, 05 Oct 2004 08:49:37 +0400 [thread overview]
Message-ID: <416227E1.8020306@wasp.net.au> (raw)
In-Reply-To: <Pine.LNX.4.60-041.0410042301510.22333@unix47.andrew.cmu.edu>
William Knop wrote:
>
>> This code starts:
>>
>> 0: 8b 55 04 mov 0x4(%ebp),%edx
>> 3: 83 c1 08 add $0x8,%ecx
>>
>> and as %ebp is 01000000, this oopses.
>> It looks very much like a single-bit memory error (as has already been
>> suggested as a possibility).
>
>
> Oh my. So, I ran memcheck again for a few hours, and it checked out
> fine. Just in case, though, I bought a replacement stick of ram. Well,
> the oopses went away, so it must have been the ram.
For future reference, I have had errors show up after 24-36 hours of memtest86. I usually find that
if it passes 48 hours of testing then things are looking pretty reliable. A couple of hours is
usually too small a sample to rely on.
Brad
next prev parent reply other threads:[~2004-10-05 4:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 12:12 libata badness William Knop
2004-10-04 13:59 ` Jon Lewis
2004-10-04 15:50 ` William Knop
2004-10-04 16:06 ` Mark Lord
2004-10-04 16:24 ` William Knop
2004-10-04 16:30 ` Jeff Garzik
2004-10-04 16:09 ` Jon Lewis
2004-10-04 16:34 ` William Knop
2004-10-04 16:30 ` Jeff Garzik
2004-10-04 16:55 ` William Knop
2004-10-04 17:42 ` William Knop
2004-10-04 17:50 ` Jim Paris
2004-10-04 18:03 ` William Knop
2004-10-04 18:01 ` Jeff Garzik
2004-10-04 22:47 ` Neil Brown
2004-10-05 3:11 ` William Knop
2004-10-05 4:49 ` Brad Campbell [this message]
2004-10-05 5:27 ` Norman Schmidt
-- strict thread matches above, loose matches on Subject: below --
2008-07-31 18:53 Kumar Gala
2008-07-31 19:02 ` Ben Dooks
2008-07-31 19:02 ` Ben Dooks
2008-07-31 20:24 ` Kumar Gala
2008-07-31 20:24 ` Kumar Gala
2008-07-31 20:37 ` Scott Wood
2008-07-31 20:37 ` Scott Wood
2008-07-31 21:04 ` Anton Vorontsov
2008-07-31 21:04 ` Anton Vorontsov
2008-07-31 21:58 ` Kumar Gala
2008-07-31 21:58 ` Kumar Gala
2008-08-01 10:43 ` Ben Dooks
2008-08-01 10:43 ` Ben Dooks
2008-08-01 12:46 ` Kumar Gala
2008-08-01 12:46 ` Kumar Gala
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=416227E1.8020306@wasp.net.au \
--to=brad@wasp.net.au \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=wknop@andrew.cmu.edu \
/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.