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.
Created attachment 486086[details]
cpuinfo file from bigi system
Description of problem:
The bigi testbed which runs SPECsfs NFS worload is receiving messages of the form ...
Message from syslogd@bigi at Mar 16 17:17:21 ...
kernel:Uhhuh. NMI received for unknown reason 31 on CPU 0.
Message from syslogd@bigi at Mar 16 17:17:21 ...
kernel:Do you have a strange power saving mode enabled?
Message from syslogd@bigi at Mar 16 17:17:21 ...
kernel:Dazed and confused, but trying to continue
Message from syslogd@bigi at Mar 16 17:17:21 ...
kernel:Uhhuh. NMI received for unknown reason 00 on CPU 1.
Message from syslogd@bigi at Mar 16 17:17:21 ...
kernel:Do you have a strange power saving mode enabled?
Message from syslogd@bigi at Mar 16 17:17:21 ...
kernel:Dazed and confused, but trying to continue
...
in bursts with the 2.6.32-122 kernel. Tests with the -118 kernel show no problem. The cpuinfo for this server, an HP DL580g2 (Intel) has been attached. I have tried disabling hyper threads at the BIOS but we still get errors. Disabling nmi_watchdog in /proc/sys/kernel makes them go away.
I have talked to dzickus about this ...
Version-Release number of selected component (if applicable):
2.6.32-122
How reproducible:
everytime
Steps to Reproduce:
1. run specsfs on bigi testbed for sure
2.
3.
Actual results:
Expected results:
Additional info:
Barry,
I thought you were the first one to notice this yesterday, turns out you are already the third bz filed for it. :-)
I hate p4 boxes.
*** This bug has been marked as a duplicate of bug 688547 ***
I had see
kernel:Uhhuh. NMI received for unknown reason 31 on CPU 0.
kernel:Uhhuh. NMI received for unknown reason 21 on CPU 0.
kernel:Do you have a strange power saving mode enabled?
kernel:Dazed and confused, but trying to continue
I had try :
add ‘nmi_watchdog=0 pcie_aspm=off nohpet’ to kernel param
change a older kernel
Result:
Use a older kernel 2.6.32-131.21.1 (default is 2.6.32-358.23.2)。
Created attachment 486086 [details] cpuinfo file from bigi system Description of problem: The bigi testbed which runs SPECsfs NFS worload is receiving messages of the form ... Message from syslogd@bigi at Mar 16 17:17:21 ... kernel:Uhhuh. NMI received for unknown reason 31 on CPU 0. Message from syslogd@bigi at Mar 16 17:17:21 ... kernel:Do you have a strange power saving mode enabled? Message from syslogd@bigi at Mar 16 17:17:21 ... kernel:Dazed and confused, but trying to continue Message from syslogd@bigi at Mar 16 17:17:21 ... kernel:Uhhuh. NMI received for unknown reason 00 on CPU 1. Message from syslogd@bigi at Mar 16 17:17:21 ... kernel:Do you have a strange power saving mode enabled? Message from syslogd@bigi at Mar 16 17:17:21 ... kernel:Dazed and confused, but trying to continue ... in bursts with the 2.6.32-122 kernel. Tests with the -118 kernel show no problem. The cpuinfo for this server, an HP DL580g2 (Intel) has been attached. I have tried disabling hyper threads at the BIOS but we still get errors. Disabling nmi_watchdog in /proc/sys/kernel makes them go away. I have talked to dzickus about this ... Version-Release number of selected component (if applicable): 2.6.32-122 How reproducible: everytime Steps to Reproduce: 1. run specsfs on bigi testbed for sure 2. 3. Actual results: Expected results: Additional info: