grsecurity forums

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

has kdump ever worked on grsec? we restrict access through /dev/mem to non-RAM pages only which i think is what kdump needs.