• Uncategorized

About linux : kdump-couldnt-start-because-of-crashkernel-kernel-cmdline-variable

Question Detail

I’m trying to use kdump tool in a Yocto based distribution (based on poky reference distribution). I added the variable crashkernel=64M to the cmdline to reserve memory for the dump kernel by modifying the /boot/extlinux/extlinux.conf file as follow:

# Generic Distro Configuration file generated by OpenEmbedded
LABEL Fedi - Fedi Operating System
        KERNEL ../Image_Dump
        INITRD ../initrd
        APPEND ${cbootargs} root=/dev/mmcblk${devnum}p${distro_bootpart} rw root ${bootargs} crashkernel=64M

After reboot, I checked the /proc/cmdline to see if the kernel has used this parameter during boot.
This is the output of cat /proc/cmdline command:

console=ttyS0,115200 console=tty0 fbcon=map:0 isolcpus=1-2 video=tegrafb no_console_suspend=1 earlycon=uart8250,mmio32,0x3100000 nvdumper_reserved=0x2772e0000 gpt usbcore.old_scheme_first=1 tegraid=18.1.2.0.0 maxcpus=6 boot.slot_suffix= boot.ratchetvalues=0.2031647.1 [email protected] sdhci_tegra.en_boot_part_access=1 root=/dev/mmcblk0p1 rw rootwait crashkernel=64M

It seems that the kernel started as it’s supposed to be with crashkernel parameter but the problem is I still get this error about reserving memory for the kernel.
This is output of systemctl status kdump command:

Sep 20 10:44:01 Fedi systemd[1]: Starting Reboot and dump vmcore via kexec...
Sep 20 10:44:01 Fedi  kdump-helper[410]: Memory for crashkernel is not reserved
Sep 20 10:44:01 Fedi  kdump-helper[410]: Please reserve memory by passing"[email protected]" parameter to kernel
Sep 20 10:44:01 Fedi  kdump-helper[410]: Then try to loading kdump kernel
Sep 20 10:44:01 Fedi  kdump-helper[403]: Failed to load kdump kernel!
Sep 20 10:44:01 Fedi  kdump[412]: Failed to load kdump kernel!
Sep 20 10:44:01 Fedi  systemd[1]: kdump.service: Main process exited, code=exited, status=1/FAILURE
Sep 20 10:44:01 Fedi  systemd[1]: kdump.service: Failed with result 'exit-code'.
Sep 20 10:44:01 Fedi  systemd[1]: Failed to start Reboot and dump vmcore via kexec.

I’ve also tried different sizes 128M, 265M … but I’m still getting the same error. I’m using a Jetson TX2 as platforom.
Any idea how to solve this problem?

Question Answer

No answer for now.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.