Created attachment 26203 [details] Full dmesg output Recently installed RHEL 6.0 beta, which uses kernel 2.6.32-19.el6.x86_64, on a box in our test lab. With ACPI enabled, the box would hard hang at random points during the install. With ACPI disabled the box works fine, but is showing the errors in the dmesg output (thus this bug report). This box had Fedora 11 x86_64 loaded (variations of kernel 2.6.29 and 2.6.30) and running ok on it for months without a need to disable ACPI. RHEL 6 beta dmesg errors below, and full message will be attached as an attachment. ***************************************************************** CPU0: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz stepping 05 Booting Node 0, Processors #1 Uhhuh. NMI received for unknown reason 2d on CPU 0. Do you have a strange power saving mode enabled? Dazed and confused, but trying to continue Uhhuh. NMI received for unknown reason 00 on CPU 1. Do you have a strange power saving mode enabled? Dazed and confused, but trying to continue CPU 1 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8 #2 Uhhuh. NMI received for unknown reason 00 on CPU 2. Do you have a strange power saving mode enabled? Dazed and confused, but trying to continue CPU 2 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8 #3 Ok. Uhhuh. NMI received for unknown reason 00 on CPU 3. Do you have a strange power saving mode enabled? Dazed and confused, but trying to continue CPU 3 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8 Skipped synchronization checks as TSC is reliable. Brought up 4 CPUs Total of 4 processors activated (21395.31 BogoMIPS). Testing NMI watchdog ... WARNING: CPU#0: NMI appears to be stuck (225->225)! Please report this to bugzilla.kernel.org, and attach the output of the 'dmesg' command. WARNING: CPU#1: NMI appears to be stuck (2->2)! Please report this to bugzilla.kernel.org, and attach the output of the 'dmesg' command. WARNING: CPU#2: NMI appears to be stuck (1->1)! Please report this to bugzilla.kernel.org, and attach the output of the 'dmesg' command. WARNING: CPU#3: NMI appears to be stuck (1->1)! Please report this to bugzilla.kernel.org, and attach the output of the 'dmesg' command. *****************************************************************
please build the latest upstream kernel to see if the problem still exists. If yes, then this is a kernel bug that we should take care of. If not, I'm afraid you need to report this issue the the Redhat as this sound like a problem that exists in distro kernel only.
ping...
Sorry Zhang, please close this bug. I don't have the time to spend on this to the necessary depth atm. :(
okay, bug closed