Hide Forgot
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.
May be related to: https://lkml.org/lkml/2011/2/16/106 [tip:perf/urgent] perf, x86: P4 PMU: Fix spurious NMI messages
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).
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).
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.