Escalated to Bugzilla from IssueTracker
Please assign the hardware "arch" field appropriately for an IBM x336.
Thanks in advance. -ernie
x336 is an EM64T system. Arch set accordingly.
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.
we dont support SAS on the 366 thus no way to install RHEL3
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?
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."
Created attachment 123628 [details]
Screenshot of the NMI issue on a x366.
can IBM try booting with this command line option at boot:
does it solve the problem?
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.
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.
Relinking IT 85103 to this bug.
Also linking IT 85781 to this bug.
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).
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.