Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I'm seeing this with a -119.el6 based kernel. I'm working on git bisecting.
+++ This bug was initially created as a clone of Bug #674281 +++
Description of problem:
After upgrading my rawhide boxes to 2.6.38-rc kernels, dmesg is filled with following messages every few seconds"
[ 491.782610] Uhhuh. NMI received for unknown reason 31 on CPU 1.
[ 491.782617] Do you have a strange power saving mode enabled?
[ 491.782622] Dazed and confused, but trying to continue
[ 541.524621] Uhhuh. NMI received for unknown reason 21 on CPU 0.
Type 21 and 31 appear. It wasn't the case with .37 kernels on those machines.
Hardware is pretty standard Dell Optiplex GX620, with pentium 4 CPU.
Smolt profile of one machine is here:
http://smolts.org/show?uuid=pub_7d62f4b4-f2f3-4c70-9a04-0aca1f270345
The NMI messages dissapear after issuing "echo 0 > /proc/sys/kernel/nmi_watchdog" (as suggested by powertop).
Version-Release number of selected component (if applicable):
2.6.38-0.rc2.git7.1.fc15.x86_64
How reproducible:
Boot computer.
--- Additional comment from zdzichu on 2011-02-16 08:50:54 EST ---
May be related to: https://lkml.org/lkml/2011/2/16/106
[tip:perf/urgent] perf, x86: P4 PMU: Fix spurious NMI messages
--- Additional comment from updates on 2011-02-25 15:08:06 EST ---
Package kernel-2.6.38-0.rc6.git4.1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 updates-testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-2.6.38-0.rc6.git4.1.fc15'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/kernel-2.6.38-0.rc6.git4.1.fc15
then log in and leave karma (feedback).
--- Additional comment from updates on 2011-02-28 11:41:50 EST ---
Package kernel-2.6.38-0.rc6.git6.1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 updates-testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-2.6.38-0.rc6.git6.1.fc15'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/kernel-2.6.38-0.rc6.git6.1.fc15
then log in and leave karma (feedback).
--- Additional comment from updates on 2011-03-04 04:55:39 EST ---
kernel-2.6.38-0.rc6.git6.1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
I finished my git bisect and it ended here:
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[a83bd5ca7110d1739e6f268455369245216e6e21] [x86] perf: P4 PMU - Fix unflagged overflows handling
I was testing on a Dell PowerEdge 850 with a Intel(R) Celeron(R) CPU 2.53GHz.
Also find this problem with report unknown reason 00 in RHEL 6.1 guest with Kernel 2.6.32-118.el6, and the guest failed to boot up in our test:
2011-03-14 10:54:52: Uhhuh. NMI received for unknown reason 31 on CPU 0.
2011-03-14 10:54:52: Uhhuh. NMI received for unknown reason 00 on CPU 1.
2011-03-14 10:54:52: Do you have a strange power saving mode enabled?
2011-03-14 10:54:52: Dazed and confused, but trying to continue
2011-03-14 10:54:52: Uhhuh. NMI received for unknown reason 00 on CPU 1.
2011-03-14 10:54:52: Do you have a strange power saving mode enabled?
2011-03-14 10:54:52: Dazed and confused, but trying to continue
2011-03-14 10:54:52: Do you have a strange power saving mode enabled?
2011-03-14 10:54:52: Dazed and confused, but trying to continue
2011-03-14 10:54:52: Uhhuh. NMI received for unknown reason 21 on CPU 0.
2011-03-14 10:54:52: Do you have a strange power saving mode enabled?
2011-03-14 10:54:52: Dazed and confused, but trying to continue