From: Gregory Boyce <gboyce@rakis.net>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dazed and Confused
Date: 08 Dec 2002 10:22:38 -0500 [thread overview]
Message-ID: <1039360959.1153.10.camel@lapdog.badbelly.com> (raw)
In-Reply-To: <1039348787.15058.6.camel@klendathu.telaviv.sgi.com>
On Sun, 2002-12-08 at 06:59, Gilad Ben-Yossef wrote:
> On Fri, 2002-12-06 at 16:55, Greg Boyce wrote:
>
> > 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
>
> I have had the exact same error happen a while back on a 2.2.x kernel.
> It did not seem to hurt anything but it made the QA dept. go bonkers so
> I've spent some time chasing it down and found out what caused it back
> then - perhaps the same, or similar, applies to your setup as well:
>
> The machines in question were Intel ISP1100 1U servers and for various
> non important reasons I have built the kernel which they were running
> without APM support. Now these machines have 3 small non marked buttons
> on their front - one is the power button, one is the reset button and
> one was a suspend button.
>
> What I found out was that whenever anyone pressed the "suspend" button
> (usually because they meant to press the power or reset buttons and
> missed) the error in questions was logged. It seems that APM suspend is
> implemented (at least on those machines) as an NMI, and if you compiled
> the kernel sans APM support the NMI handling code simply did not grok
> that specific NMI and thus reported said error, which was otherwise
> harmless.
Most of these machines do have Intel motherboards. I don't recall
seeing suspend buttons, but I'll take a look. Thanks!
--
Greg
next prev parent reply other threads:[~2002-12-08 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 14:55 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
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 [this message]
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=1039360959.1153.10.camel@lapdog.badbelly.com \
--to=gboyce@rakis.net \
--cc=gilad@benyossef.com \
--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®