From: David Raufeisen <david@fortyoz.org>
To: linux-kernel@vger.kernel.org
Subject: Uhhuh. NMI received for unknown reason 20. ?
Date: Sun, 12 May 2002 22:03:40 -0700 [thread overview]
Message-ID: <1021266220.3cdf492c48333@mail.fortyoz.org> (raw)
Hello,
I'm setting up a new server, it has a new Intel ServerWorks board with dual
1.266ghz P3 CPU's and 2gb ram.
I'm running into a few problems with it, crashing and strange error messages,
if anyone is familiar with these problems i'd appreciate a heads up on how to
handle them.
I currently have it running 2.4.19pre8, it would crash quite easily with 2.4.18
with redhat's kernel patches from their rawhide distribution while compiling
multiple kernels simultaneously. I will try to get a cable and capture the oops
with serial console.
Here is dmesg output..
http://fortyoz.org/files/misc/svwks-dmesg.txt
Something that worries me:
Uhhuh. NMI received for unknown reason 20.
Dazed and confused, but trying to continue
Do you have a strange power saving mode enabled?
In the bios it had generate NMI on SERR and generate NMI on PERR, i disabled
them but still get this message when doing intensive things (compiling kernels).
Does this message mean bad things are certain to come or can it be harmless?
I'm going to leave it compiling kernels overnight and see if it's dead in the
morning.
# cat /proc/interrupts
CPU0 CPU1
0: 115002 104624 IO-APIC-edge timer
1: 81 94 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
14: 4 0 IO-APIC-edge ide0
18: 296766 296544 IO-APIC-level eth0
21: 20983 20895 IO-APIC-level ide2, ide3
NMI: 1 0
LOC: 219526 219524
ERR: 0
MIS: 0
Also with regards to the promise controller, it should be running at ATA100 but
is only reported at ATA33, it has the proper cables and the drives and
controller card are certainly capable, any idea?
Thanks for any help.
--
David Raufeisen <david@fortyoz.org>
reply other threads:[~2002-05-13 5:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1021266220.3cdf492c48333@mail.fortyoz.org \
--to=david@fortyoz.org \
--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®