openwrt/package/boot/kexec-tools/files/kdump.defaults

#!/bin/sh

# kB disable if mem low than 256MB
memtotal=`grep MemTotal /proc/meminfo | awk '{print $2}'`
if test $memtotal -le 262144; then
	exit 0
fi
KZ=128
if test $memtotal -ge 8388608; then
	KZ=512
elif test $memtotal -ge 4194304; then
	KZ=256
fi

case $(uname -m) in
	i?86|x86_64)
		if ! grep -q crashkernel /boot/grub/grub.cfg; then
			mount /boot -o remount,rw
			sed -i "s/linux.*/& crashkernel=${KZ}M/" /boot/grub/grub.cfg
			mount /boot -o remount,ro
		fi
		;;
esac
kexec-tools: bump version and add support for crashdump kernel split kexec-tools into two packages, kexec and kdump. * kexec to simply execute a new kernel * kdump is for loading and collecting debris of a crashed kernel with support for kdump forensics. In order to properly support booting into a crashkernel, an init script as well as UCI configuration has been added. As modifying the kernel cmdline is required for this to work in x86 platforms use an uci-defaults script to modify /boot/grub/grub.cfg. To test collecting crash information, use the 'c' sysrq-trigger, ie. echo c > /proc/sysrq-trigger This should result in the crash kernel being executed and (depending on the configution) dmesg and/or vmcore getting saved. To check if the crash kernel was loaded properly, use the 'status' command of the kdump init script. Signed-off-by: Daniel Golle <daniel@makrotopia.org> 2017-03-21 21:58:13 +00:00			`#!/bin/sh`

x86: make crashdump works 1. KERNEL_CRASH_DUMP should depends on KERNEL_PROC_KCORE (kexec use it) 2. select crashkernel mem size by totalmem mem <= 256M disable crashkernel by default mem >= 4G use 256M for crashkernel mem >= 8G use 512M for crashkernel default use 128M 3. set BOOT_IMAGE in kdump.init 4. resolve a "Unhandled rela relocation: R_X86_64_PLT32" error Tested on x86_64 Signed-off-by: Chen Minqiang <ptpt52@gmail.com> 2019-07-11 14:34:03 +00:00			`# kB disable if mem low than 256MB`
			memtotal=`grep MemTotal /proc/meminfo \| awk '{print $2}'`
			`if test $memtotal -le 262144; then`
			`exit 0`
			`fi`
			`KZ=128`
			`if test $memtotal -ge 8388608; then`
			`KZ=512`
			`elif test $memtotal -ge 4194304; then`
			`KZ=256`
			`fi`

kexec-tools: bump version and add support for crashdump kernel split kexec-tools into two packages, kexec and kdump. * kexec to simply execute a new kernel * kdump is for loading and collecting debris of a crashed kernel with support for kdump forensics. In order to properly support booting into a crashkernel, an init script as well as UCI configuration has been added. As modifying the kernel cmdline is required for this to work in x86 platforms use an uci-defaults script to modify /boot/grub/grub.cfg. To test collecting crash information, use the 'c' sysrq-trigger, ie. echo c > /proc/sysrq-trigger This should result in the crash kernel being executed and (depending on the configution) dmesg and/or vmcore getting saved. To check if the crash kernel was loaded properly, use the 'status' command of the kdump init script. Signed-off-by: Daniel Golle <daniel@makrotopia.org> 2017-03-21 21:58:13 +00:00			`case $(uname -m) in`
			`i?86\|x86_64)`
			`if ! grep -q crashkernel /boot/grub/grub.cfg; then`
			`mount /boot -o remount,rw`
x86: make crashdump works 1. KERNEL_CRASH_DUMP should depends on KERNEL_PROC_KCORE (kexec use it) 2. select crashkernel mem size by totalmem mem <= 256M disable crashkernel by default mem >= 4G use 256M for crashkernel mem >= 8G use 512M for crashkernel default use 128M 3. set BOOT_IMAGE in kdump.init 4. resolve a "Unhandled rela relocation: R_X86_64_PLT32" error Tested on x86_64 Signed-off-by: Chen Minqiang <ptpt52@gmail.com> 2019-07-11 14:34:03 +00:00			`sed -i "s/linux.*/& crashkernel=${KZ}M/" /boot/grub/grub.cfg`
kexec-tools: bump version and add support for crashdump kernel split kexec-tools into two packages, kexec and kdump. * kexec to simply execute a new kernel * kdump is for loading and collecting debris of a crashed kernel with support for kdump forensics. In order to properly support booting into a crashkernel, an init script as well as UCI configuration has been added. As modifying the kernel cmdline is required for this to work in x86 platforms use an uci-defaults script to modify /boot/grub/grub.cfg. To test collecting crash information, use the 'c' sysrq-trigger, ie. echo c > /proc/sysrq-trigger This should result in the crash kernel being executed and (depending on the configution) dmesg and/or vmcore getting saved. To check if the crash kernel was loaded properly, use the 'status' command of the kdump init script. Signed-off-by: Daniel Golle <daniel@makrotopia.org> 2017-03-21 21:58:13 +00:00			`mount /boot -o remount,ro`
			`fi`
			`;;`
			`esac`