kdump not starting: Memory for crashkernel is not reserved

Discuss usability issues, general maintenance, and general support issues for a grsecurity-enabled system.

kdump not starting: Memory for crashkernel is not reserved

Postby SheepOnMeth » Fri Mar 01, 2013 2:51 pm

This is more kernel related than GRsecurity but has anyone had a problem with kdump starting after compiling a kernel?

I noticed /var/log/boot.log it failed, and when trying to start it manually I get:
Code: Select all
# service kdump restart
Memory for crashkernel is not reserved
Please reserve memory by passing "crashkernel=X@Y" parameter to the kernel
Stopping kdump:                                            [FAILED]
Starting kdump:


In /etc/grub.conf I changed crashkernel=auto to crashkernel=128M@16M but that didn't make a difference.

In the .config file for the kernel I have crash dump enabled:
Code: Select all
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_PHYSICAL_START=0x1000000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x1000000


Any ideas?

TIA
SheepOnMeth
 
Posts: 1
Joined: Thu Feb 28, 2013 3:35 pm

Re: kdump not starting: Memory for crashkernel is not reserv

Postby PaX Team » Sun Mar 10, 2013 10:24 pm

has kdump ever worked on grsec? we restrict access through /dev/mem to non-RAM pages only which i think is what kdump needs.
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm


Return to grsecurity support