Sles11 Sp1 Does Not Produce A Kdump File After A Crash (Cr7001706); Sles11 Fails To Install On Systems Equipped With 6-Core Cmods - Oracle Sun Fire X4800 Product Notes

SLES11 SP1 Does Not Produce A Kdump File After A Crash (CR7001706)

crashkernel=512M
Note -
not have enough kdump memory space, complete step 2 as well.
2. Add pci=nomsi to the KDUMP_COMMANDLINE_APPEND line in /etc/sysconfig/kdump. For
example, change:
KDUMP_COMMANDLINE_APPEND="irqpoll maxcpus=1 reset_devices
cgroup_disable=memory"
To:
KDUMP_COMMANDLINE_APPEND="irqpoll maxcpus=1 pci=nomsi reset_devices
cgroup_disable=memory"
SLES11 SP1 Does Not Produce A Kdump File After A Crash
(CR7001706)
After a crash, SUSE Linux Enterprise Server 11 (SLES11) SP1 might not produce a kdump file.
In this case, it might also display a message similar to the following on the console:
INFO: Cannot find debug information: Unable to find debuginfo file. [ 41.368017]
Restarting system.
Workaround
Perform a regular update from Novell after installation.
SLES11 Fails to Install On Systems Equipped with 6–Core
CMODs (CR 7024769)
Servers equipped with 6-socket CMODs (Model E7540) might fail to install or boot with SUSE
Linux Enterprise Server 11 (SLES11).
Workaround
Install SLES11 SP1 or newer.
54 Sun Fire X4800 Server Product Notes • July 2017
This step stops your server from displaying warning messages. If your server does