From: Krzysztof Halasa <khc@pm.waw.pl>
To: <linux-kernel@vger.kernel.org>
Cc: Greg Boyce <gboyce@rakis.net>
Subject: Re: Dazed and Confused
Date: 07 Dec 2002 00:33:45 +0100 [thread overview]
Message-ID: <m3znripvs6.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <Pine.LNX.4.42.0212061202230.7770-100000@egg>
Greg Boyce <gboyce@rakis.net> writes:
> Are the machines likely to give us problems with crashing and data
> corruption, or would it be safe to ignore the problem unless we started
> noticing odd behavior?
First of all, only RAM with parity bits (or ECC) can generate such NMI
(the motherboard must support this as well, of course).
Most motherboads can be configured in ECC mode, and they correct 1-bit
errors. 2-bit errors are reported and not corrected, but the probability
of such error is nearly zero in normal conditions (unless your hardware
is defective, of course).
CPU caches do ECC as well, and possibly can generate NMI requests. However,
they use static RAM (as opposed to dynamic) and bit errors should not
happen there.
--
Krzysztof Halasa
Network Administrator
next prev parent reply other threads:[~2002-12-07 13:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 14:55 Dazed and Confused Greg Boyce
2002-12-06 15:24 ` Richard B. Johnson
2002-12-06 16:05 ` Alan Cox
2002-12-06 16:47 ` Greg Boyce
2002-12-06 17:08 ` Greg Boyce
2002-12-06 22:25 ` Alan Cox
2002-12-06 23:33 ` Krzysztof Halasa [this message]
2002-12-08 1:36 ` Alan Cox
2002-12-09 19:19 ` H. Peter Anvin
2002-12-10 0:42 ` Bill Davidsen
2002-12-09 19:19 ` H. Peter Anvin
2002-12-08 11:59 ` Gilad Ben-Yossef
2002-12-08 15:22 ` Gregory Boyce
2002-12-08 22:55 ` Toon van der Pas
-- strict thread matches above, loose matches on Subject: below --
2002-07-08 11:44 Dazed and confused jbradford
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=m3znripvs6.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=gboyce@rakis.net \
--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