Novell is now a part of Micro Focus

My Favorites

Close

Please to see your favorites.

Configuration of fadump

This document (7012786) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11 Service Pack 3 (SLES 11 SP3)
SUSE Linux Enterprise Server 11 Service Pack 4 (SLES 11 SP4)

Situation

There is no YaST2 module at the moment available to setup the firmware assisted dump (fadump). It has to be enabled / disabled manually as described with this document.

Resolution

To enable fadump do the following:

1. in /etc/sysconfig/kdump set

KDUMP_FADUMP=yes

2. Run as user root the command

mkdumprd -f

3. Reboot the system.

4. After a reboot verify with the below that this file is available and shows a value of '1'

cat /sys/kernel/fadump_enabled

This indicates that fadump is enabled in the kernel and the system will now use the fadump mechanism to capture a kernel dump.

NOTE: If after this process the file /etc/sysconfig/kdump is modified again by any means, be it manually or via YaST, the below command has to be run again to make fadump aware of these changes:

mkdumprd -f

To disable fadump do the following:

1. in /etc/sysconfig/kdump set

KDUMP_FADUMP=no

2. Run as user root

mkinitrd

3. Reboot the system.

Additional Information

Possible problems:

1. In case of a second kernel failing with "Out of Memory" messages during fadump capture, use the "fadump_reserve_mem=<size>M" kernel command line to specify a larger size of the memory to reserve for boot memory dump preservation and reboot the system.

The term "boot memory" means the size of the low memory chunk that is required for the second kernel to boot successfully when booted with restricted memory during a system crash. By default, the boot memory size will not be larger than 5% of system RAM or 256MB.  Alternatively, a user can also specify the boot memory size through the boot parameter "fadump_reserve_mem=" which will override the default calculated size.

2. While FADump is configured, only use the “mkdumprd -f” command to update the default initrd (instead of mkinitrd) to ensure dump capture scripts are included in the default initrd. If the default initrd is updated by other methods, dump capture scripts may not be included in the initrd. If this happens, a vmcore will not be captured automatically after a crash. Instead, the system will boot with minimal available memory and with the “/proc/vmcore” file waiting to be saved.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/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:7012786
  • Creation Date:04-JUL-13
  • Modified Date:02-MAR-18
    • SUSESUSE Linux Enterprise Server

Did this document solve your problem? Provide Feedback