From: Mike Fedyk <mfedyk@matchmail.com>
To: Disconnect <lkml@sigkill.net>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Oops with 2.4.23
Date: Mon, 22 Dec 2003 10:50:07 -0800 [thread overview]
Message-ID: <20031222185007.GQ6438@matchmail.com> (raw)
In-Reply-To: <1072118172.7007.32.camel@slappy>
On Mon, Dec 22, 2003 at 01:36:12PM -0500, Disconnect wrote:
> Evidently many people can look at an oops or crash path and be 90%
> certain its bad/misperforming memory. (How they do this I don't
> know..) I've noticed that 'check your ram' is not always given as the
> answer, but it seems that most of the time when it is given its also
> correct.
Single bit changes on high bits (especially when they're not used in any bit
tests), are usually suspect from what I see on the list...
next prev parent reply other threads:[~2003-12-22 18:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 8:56 Oops with 2.4.23 Arnaud Fontaine
2003-12-18 11:47 ` Marcelo Tosatti
2003-12-18 13:06 ` Arnaud Fontaine
2003-12-18 19:08 ` Mike Fedyk
2003-12-19 12:26 ` Arnaud Fontaine
2003-12-19 22:44 ` Arnaud Fontaine
2003-12-19 23:35 ` Maciej Zenczykowski
2003-12-19 23:55 ` Mike Fedyk
2003-12-22 10:07 ` Marc Bevand
2003-12-22 16:37 ` Disconnect
2003-12-21 7:54 ` Arnaud Fontaine
[not found] ` <Pine.LNX.4.58L.0312211238420.6632@logos.cnet>
2003-12-21 15:49 ` Arnaud Fontaine
2003-12-22 2:17 ` Barry K. Nathan
2003-12-22 17:05 ` Chris Frey
2003-12-22 18:36 ` Disconnect
2003-12-22 18:50 ` Mike Fedyk [this message]
2003-12-22 21:37 ` Barry K. Nathan
2003-12-23 14:13 ` Jesper Juhl
-- strict thread matches above, loose matches on Subject: below --
2003-12-19 16:09 Xose Vazquez Perez
2003-12-22 18:06 Xose Vazquez Perez
2003-12-22 18:44 ` Mike Fedyk
2003-12-22 18:53 ` Xose Vazquez Perez
2003-12-23 15:07 ` Arnaud Fontaine
2003-12-23 20:21 ` Xose Vazquez Perez
2003-12-28 14:00 ` Arnaud Fontaine
2003-12-28 21:49 ` James Bourne
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=20031222185007.GQ6438@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@sigkill.net \
/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.