From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET
Description of problem:
I installed succesfully an IBM Xseries 336 Server. But the server
freeze frequently and I have to power it off. The screen goes black
and it appears with : See the system error log. Re-booting due to
unexpected NMI at 0000:0000.
The server is in a rack and is connected to a Think vision Monitor
(6636-AB1). It is connected to a monitor switch (32P1635).
Please Help !!!!
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Turn on the server
2.Wait some time (30 min- 1hour)
3.See the screen going black wit the reboot message and hang there.
Please provide more useful info. At the least, we will need
panic and/or oops data from the console (for which you might
need to attach a serial console line).
Well, by now I can tell you that we are running 2.4.21-20.ELsmp
kernel (RHES AS3 U3) and all the machines are freezing every day. The
last that you can see in the screen is "Re-booting due to
unexpected NMI at 0000:0000". I was looking for help and found some
similar problems with this kernel.Do you have some other newer and
fully tested kernels ??
I'll get the data from the console.
Tks in advance.
This same problem is happening on our system xSeries 336 + (
2.4.21-27.0.2-ELsmp ) too.
Doing a cscope search on the kernel sources, and the doing a
"strings <kernel> | grep NMI" on both vmlinux-2.4.21-20.ELsmp and
vmlinux-2.4.21-27.0.2.ELsmp, this message does not appear to be
coming from the kernel:
Re-booting due to unexpected NMI at 0000:0000
Is this message being generated by the BIOS? And what does the
message requesting "See the system error log" actually refer to?
I'm seeing this problem on a dual Xeon IBM x346 (model 8840). There
is no kernel oops, and after the BIOS goes through checking memory,
initing the two Broadcom ethernets and getting a "Status=OK" from the
ServeRAID-7k, I get the message "Unexpected NMI at 000:0000". I don't
think the kernel booted yet - there were no messages from GRUB. In my
case it feels like a hardware to problem to me. Whether the kernel is
creating inauspicious circumstances is anyone's guess.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.