From: Greg Boyce <gboyce@rakis.net>
To: linux-kernel@vger.kernel.org
Subject: Dazed and Confused
Date: Fri, 6 Dec 2002 09:55:36 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.42.0212060948250.7121-100000@egg> (raw)
Folks,
I have an issue that I've been trying to track down for some time, and I
was hoping that someone might be able to provide me with a definitive
awnser.
I work in a company with a large number of Linux machine deployed all
around the country, and in some of the machines we've been seeing the
following error:
Uhhuh. NMI received. Dazed and confused, but trying to continue
You probably have a hardware problem with your RAM chips
Now, from what I've read about this error, it is caused by the memory
detecting a parity error in the actual RAM chips, and reporting it to the
OS. However, some of the people within the company who handle the
replacement of hardware are convinced that it might be something simpler
in some of the cases. Perhaps the RAM chip isn't fully seated, or the
machine just needs a reboot.
Due to the number of machines and their locations, running memtest86 on
them isn't exactly feasible.
Is there anything besides failing hardware that could be the cause of this
error? Also, how serious is this error? Some of the machines reporting
this error have had problems with programs crashing, while others seem to
run fine.
Any input or resources you could point me at would be appreciated.
Greg Boyce
next reply other threads:[~2002-12-06 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 14:55 Greg Boyce [this message]
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
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=Pine.LNX.4.42.0212060948250.7121-100000@egg \
--to=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
all inboxes | Powered by JetHome®