이 콘텐츠는 선택한 언어로 제공되지 않습니다.
32.5. Using sadump on Fujitsu PRIMEQUEST systems
On Fujitsu PRIMEQUEST systems, you can also enable the stand-alone dump (sadump) functionality provided by the hardware. This utility operates by combining kdump, which is a standard part of Red Hat Enterprise Linux, and the additional sadump BIOS-based function provided by Fujitsu.
Note
For the purpose of ensuring a dump is captured in the event of an unexpected reboot, Fujitsu recommend that sadump is always enabled on PRIMEQUEST hardware.
The sadump utility is usually invoked when a kdump cannot be processed because Red Hat Enterprise Linux has became unresponsive. These conditions can include:
- Red Hat Enterprise Linux panic or hang before kdump starts
- An error while kdump is working
How to use sadump
To use sadump, complete the following steps:
- Install the following packages according to the kernel version in use:
# yum install kernel-debuginfo kernel-debuginfo-common
- Configure UEFI for sadumpFor more details, see the FUJITSU Server PRIMEQUEST 2000 Series Installation Manual.
- Configure Red Hat Enterprise Linux for sadumpFor more details, see Section 32.5.1, “Configure Red Hat Enterprise Linux for sadump”.
- Start sadumpFor more details, see the FUJITSU Server PRIMEQUEST 2000 Series Installation Manual.
- Check the memory dumpFor more details, see Section 32.5.2, “Check the memory dump”.
32.5.1. Configure Red Hat Enterprise Linux for sadump
- Install and configure
kdumpas described in Section 32.1, “Installing the kdump Service” and Section 32.2, “Configuring the kdump Service”. - Ensure that
kdumpstarts as expected for sadump:- Configure Red Hat Enterprise Linux to not reboot after a kernel panic:By default, Red Hat Enterprise Linux reboots automatically after a kernel panic, which prevents sadump to start. To avoid this behavior, configure the
/etc/sysctl.conffile as follows:kernel.panic=0
- Configure Red Hat Enterprise Linux to start kdump by Nonmaskable Interrupt (NMI):In the procedure of starting sadump, starting kdump by NMI is needed at first.Configure
/etc/sysctl.confas follows:kernel.unknown_nmi_panic=1
- Ensure that
kdumpbehaves correctly for sadump:- Configure Red Hat Enterprise Linux to stop after kdump:By default, Red Hat Enterprise Linux reboots automatically when kdump fails, which prevents sadump to start. To avoid this behavior, configure the
/etc/kdump.conffile as follows:default halt
ordefault shell
- Configure Red Hat Enterprise Linux to start sadump:Configure
/etc/kdump.confto not block the System Management Interrupt (SMI) and thus to enable sadump to start:blacklist kvm-intel
