sledp2-kdump

Recommended update for kdump

This update fixes a problem that some systems hang after enabling kdump. The cause for that regression is that the kdump init script sets the kernel.unknown_nmi_panic sysctl which is useful on some systems to trigger a dump with the NMI button but leads to a panic on other systems. After that update you may not be able to trigger kdump with the NMI button any more. You can always get back the old behavour by adding a line -------------- 8< ---------------- kernel.unknown_nmi_panic=1 -------------- >8 ---------------- in /etc/sysctl.conf (which enables it forever) or by calling "sysctl kernel.unknown_nmi_panic=1" (which enables it once). However, use that setting for your own risk! It also fixes the detection of the crashed kernel version by passing an additional command line parameter that contains the kernel version to the kdump kernel and deletes resulting empty directories if copying of the dump failed. This update fixes a problem that some systems hang after enabling kdump. The cause for that regression is that the kdump init script sets the kernel.unknown_nmi_panic sysctl which is useful on some systems to trigger a dump with the NMI button but leads to a panic on other systems. After that update you may not be able to trigger kdump with the NMI button any more. You can always get back the old behavour by adding a line -------------- 8< ---------------- kernel.unknown_nmi_panic=1 -------------- >8 ---------------- in /etc/sysctl.conf (which enables it forever) or by calling "sysctl kernel.unknown_nmi_panic=1" (which enables it once). However, use that setting for your own risk! It also fixes the detection of the crashed kernel version by passing an additional command line parameter that contains the kernel version to the kdump kernel and deletes resulting empty directories if copying of the dump failed. recommended kdump x86_64 552358ab21b3a273fadeae392bebd63ecde865ce