From: "Etienne Lorrain" <etienne_lorrain@yahoo.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] BadRAM for 2.5.73-mm2
Date: Wed, 2 Jul 2003 10:56:30 +0200 (CEST) [thread overview]
Message-ID: <20030702085630.55048.qmail@web11803.mail.yahoo.com> (raw)
Nowdays the biggest problem seems to be slightly incompatible timings
in between motherboard and physical RAM that hurts the most, not so
much non-working bits in RAM devices.
Is there someone who has a patch so that, in case of a kernel OOPS
(or maybe SIGSEGV / SIGILL outside kernel) is checking at least
the code page where IP register points to check if a bit has flipped?
Could be done by checking the page on the Hard Disk or by a CRC method.
Having a bad BIOS parameter so that _one_ bit changes randomly every
hours is not an easy thing to detect - a message on the screen would
be nice...
Etienne.
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
next reply other threads:[~2003-07-02 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 8:56 Etienne Lorrain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-02 3:33 [PATCH] BadRAM for 2.5.73-mm2 steven.newbury1
2003-07-02 6:23 ` Oleg Drokin
2003-07-02 3:18 Steven Newbury
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=20030702085630.55048.qmail@web11803.mail.yahoo.com \
--to=etienne_lorrain@yahoo.fr \
--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;
as well as URLs for NNTP newsgroup(s).