Go to main content

Sun Fire X4800 Server Product Notes

Exit Print View

Updated: September 2018
 
 

RHEL6 Kdump Runs Out of Memory (CR 7000993 and CR 7000942)

If Red Hat Linux 6 (RHEL6) calculates that the kdump size is too small, it displays a message:

"Your running kernel is using more than 70% of the amount of space you reserved for kdump, you should consider increasing your crashkernel reservation"

    One of two conditions might be present:

  • It might have enough memory, but post the messages anyway.

  • It might really not have enough kdump memory space. In this case, if the system crashes, it might not produce a kdump file, and it might post messages similar to the following on the console:

    Out of memory: kill process 322 (insmod) score 21 or a child Killed process 322 (insmod) vsr:1352kB, anon-res: 244kB, file res: 122kB

Workaround

  1. To make the messages stop and to ensure your system has enough kdump memory space, change the following line in boot/grub/menu.lst:

    Change:

    crashkernel=auto

    To:

    crashkernel=512M


    Note -  This step stops your server from displaying warning messages. If your server does 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"