From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: nmi errors?
Date: Thu, 4 Sep 2003 08:18:46 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0309040809570.2955@chaos> (raw)
In-Reply-To: <20030903213417.GT7353@rdlg.net>
On Wed, 3 Sep 2003, Robert L. Harris wrote:
>
>
> We ran "memtest" on the machine over the weekend and it completed 3
> times without any problems. Know a better or different test?
>
>
Write 0x80 out port 0x70, and hope nobody accesses the RTC. This
will (should) disable the NMI line. Then see if the error messages
go away. If they do, it's a real NMI and you really do have bad
RAM somewhere. If they don't, your motherboard is getting glitched
either by bad design or something plugged into a slot that doesn't
have the correct timing specs.
If everything works, in spite of the NMI, just comment out the
kernel printk() and cross your fingers.
> Thus spake Richard B. Johnson (root@chaos.analogic.com):
>
> > On Wed, 3 Sep 2003, Robert L. Harris wrote:
> >
> > >
> > >
> > > Can anyone tell me what this is?
> > >
> > > 16:00:09 mailserver kernel: Uhhuh. NMI received for unknown reason 31.
> > > 16:00:09 mailserver kernel: Dazed and confused, but trying to continue
> > > 16:00:09 mailserver kernel: Do you have a strange power saving mode enabled?
> > > 16:00:34 mailserver kernel: Uhhuh. NMI received for unknown reason 21.
> > > 16:00:34 mailserver kernel: Dazed and confused, but trying to continue
> > >
> > > A coworker put a script on a server which loads up quite afew arrays
> > > with pre-set values and then compares the values against arrays. As soon as he
> > > kicked off the script I got alot of these in my log files. Not much longer and the
> > > machine crashed hard.
> > >
> >
> > Possible bad RAM.
> >
> > Cheers,
> > Dick Johnson
> > Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
> > Note 96.31% of all statistics are fiction.
> >
>
> :wq!
> ---------------------------------------------------------------------------
> Robert L. Harris | GPG Key ID: E344DA3B
> @ x-hkp://pgp.mit.edu
> DISCLAIMER:
> These are MY OPINIONS ALONE. I speak for no-one else.
>
> Life is not a destination, it's a journey.
> Microsoft produces 15 car pileups on the highway.
> Don't stop traffic to stand and gawk at the tragedy.
>
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-09-04 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 21:20 nmi errors? Robert L. Harris
2003-09-03 21:25 ` Richard B. Johnson
2003-09-03 21:34 ` Robert L. Harris
2003-09-04 12:18 ` Richard B. Johnson [this message]
2003-09-04 15:11 ` Martin Schlemmer
2003-09-04 15:25 ` Robert L. Harris
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.53.0309040809570.2955@chaos \
--to=root@chaos.analogic.com \
--cc=Robert.L.Harris@rdlg.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;
as well as URLs for NNTP newsgroup(s).