Bug 176264 - x366 NMI error logged in infinite loop - [crm#769552] Possible regression U7 beta
Summary: x366 NMI error logged in infinite loop - [crm#769552] Possible regression U7 ...
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 3.7
Hardware: ia32e Linux
Target Milestone: ---
Assignee: Ernie Petrides
QA Contact: Brian Brock
Keywords: Regression
Depends On:
Blocks: 168426
TreeView+ depends on / blocked
Reported: 2005-12-20 18:05 UTC by Issue Tracker
Modified: 2007-11-30 22:07 UTC (History)
8 users (show)

Fixed In Version: RHSA-2006-0144
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-15 16:57:43 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
dmi decode output (23.35 KB, text/plain)
2006-01-17 18:46 UTC, Brian Maly
no flags Details
Screenshot of the NMI issue on a x366. (159.10 KB, image/jpeg)
2006-01-24 18:52 UTC, Konrad Rzeszutek
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2006:0144 qe-ready SHIPPED_LIVE Moderate: Updated kernel packages available for Red Hat Enterprise Linux 3 Update 7 2006-03-15 05:00:00 UTC

Description Issue Tracker 2005-12-20 18:05:31 UTC
Escalated to Bugzilla from IssueTracker

Comment 2 Ernie Petrides 2005-12-20 20:40:31 UTC
Please assign the hardware "arch" field appropriately for an IBM x336.

Thanks in advance.  -ernie

Comment 3 Jim Paradis 2005-12-20 20:56:20 UTC
x336 is an EM64T system.  Arch set accordingly.

Comment 7 Ernie Petrides 2006-01-16 22:28:00 UTC
We have not been able to reproduce this at Red Hat.  PeterM updated
IT 85103 to request more information.  At this point, no further
progress can be made on this bugzilla.

I recommend that this be removed from the RHEL3 U7 MustFix list.

Comment 8 Brian Maly 2006-01-16 22:46:34 UTC
we dont support SAS on the 366 thus no way to install RHEL3

Comment 9 Brian Maly 2006-01-17 18:46:35 UTC
Created attachment 123318 [details]
dmi decode output

seems like perhaps a BIOS bug? can we confirm the system that exibits this
problem is running an older BIOS?

Comment 14 Konrad Rzeszutek 2006-01-24 18:51:24 UTC
FYI: The problem appears during installation, even before anaconda starts
detecting hard-drives (btw, Adaptec does have the SAS driver for RHEL3 U7 - I
can provide the image file). 

The lab machine in Westford has the latest BIOS and still exhibits this problem.
To reproduce this issue, bootup from RHEL3 U7, type:

linux dd acpi=noirq

And see it halt before anaconda with bunch of "Uhuh. Unknown NMI interrupts."

Comment 15 Konrad Rzeszutek 2006-01-24 18:52:23 UTC
Created attachment 123628 [details]
Screenshot of the NMI issue on a x366.

Comment 20 Brian Maly 2006-01-31 21:53:02 UTC
can IBM try booting with this command line option at boot:


does it solve the problem?

Comment 21 Ernie Petrides 2006-02-01 21:31:42 UTC
Besides finding out whether nmi_watchdog=0 works around this problem,
I'd also like to know why acpi=noirq is being used (and what exactly
it does).  Please provide the requested info in this bugzilla.

Thanks in advance.

Comment 22 Brian Maly 2006-02-01 21:33:50 UTC
IBM reports that nmi_watchdog=0 solves this problem.

acpi=noirq should actually be acpi=no_irq. the NMI error doesnt show up until
this boot option is used. its unclear to me what this boot option does though.

Comment 23 Ernie Petrides 2006-02-03 00:37:38 UTC
Relinking IT 85103 to this bug.

Comment 24 Ernie Petrides 2006-02-03 00:46:29 UTC
Also linking IT 85781 to this bug.

Comment 25 Ernie Petrides 2006-02-03 03:08:46 UTC
A fix for this problem has just been committed to the RHEL3 U7
patch pool this evening (in kernel version 2.4.21-40.EL).

Comment 29 Red Hat Bugzilla 2006-03-15 16:57:43 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.