Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 176264

Summary: x366 NMI error logged in infinite loop - [crm#769552] Possible regression U7 beta
Product: Red Hat Enterprise Linux 3 Reporter: Issue Tracker <tao>
Component: kernelAssignee: Ernie Petrides <petrides>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.7CC: bmaly, jparadis, krzeszut, lwang, peterm, petrides, syeghiay, tao
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: ia32e   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2006-0144 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-15 16:57:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 168426    
Attachments:
Description Flags
dmi decode output
none
Screenshot of the NMI issue on a x366. none

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:

nmi_watchdog=0

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.

http://rhn.redhat.com/errata/RHSA-2006-0144.html