Kdump fails on sles10sp2 with message "Uhhuh. NMI received for unknown reason 20"
This document (7001739) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 10 Service Pack 2
Situation
Applies to:
HP ProLiant BL685c g1
HP ProLiant DL785 G5
HP ProLiant DL380 G5
Kernel-kdump and related rpm packages installed to sles10sp2 server with 2.6.16.60-0.34-smp kernel. When admin fires the kdump trigger (through magic key or console) the server console hangs with the following message showing:
Uhhuh. NMI received for unknown reason 20.
Dazed and confused, but trying to continue
Do you have a strange power saving mode enabled?
The server will restart depending on the setting for ASR Timeout. No kernel core will be present after booting.
HP ProLiant BL685c g1
HP ProLiant DL785 G5
HP ProLiant DL380 G5
Kernel-kdump and related rpm packages installed to sles10sp2 server with 2.6.16.60-0.34-smp kernel. When admin fires the kdump trigger (through magic key or console) the server console hangs with the following message showing:
Uhhuh. NMI received for unknown reason 20.
Dazed and confused, but trying to continue
Do you have a strange power saving mode enabled?
The server will restart depending on the setting for ASR Timeout. No kernel core will be present after booting.
Resolution
Reported to engineering. A new kernel update will be released with a new option /proc/sys/kernel/panic_on_unrecovered_nmi. The default value for this is "0". Setting this to "1" allows kernel dumping on HP blades.
The fix is in kernel version 2.6.16.60-0.42.4 and later. After the Kernel has been updated, follow the steps below
Edit /etc/sysctl.conf and add the following line:
kernel.panic_on_unrecovered_nmi = 1
Restart the server after making the modifications. You can check if the setting has been effective, with the following command:
cat /proc/sys/kernel/panic_on_unrecovered_nmi
The above should return the value of 1
The fix is in kernel version 2.6.16.60-0.42.4 and later. After the Kernel has been updated, follow the steps below
Edit /etc/sysctl.conf and add the following line:
kernel.panic_on_unrecovered_nmi = 1
Restart the server after making the modifications. You can check if the setting has been effective, with the following command:
cat /proc/sys/kernel/panic_on_unrecovered_nmi
The above should return the value of 1
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7001739
- Creation Date: 09-Mar-2009
- Modified Date:10-Mar-2021
-
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
