By default, kdump-tools does not reserve enough memory for a crashkernel on arm64. The smallest reservation I've been able to get away with on my test machine (a Cavium ThunderX crb1s) is 512M.
Adding an arm64 config before that is resolved in Debian may lead to upgrade complications, so I'd like to wait until is fixed before installing an arm64-specific config. This means that, for now, arm64 users will need to manually edit their /etc/default/grub.d/kdump-tools.default config to contain:
By default, kdump-tools does not reserve enough memory for a crashkernel on arm64. The smallest reservation I've been able to get away with on my test machine (a Cavium ThunderX crb1s) is 512M.
While kdump-tools currently supports architecture- specific configs, it currently has issues that I am attempting to address here: /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 863858
https:/
Adding an arm64 config before that is resolved in Debian may lead to upgrade complications, so I'd like to wait until is fixed before installing an arm64-specific config. This means that, for now, arm64 users will need to manually edit their /etc/default/ grub.d/ kdump-tools. default config to contain:
GRUB_CMDLINE_ LINUX_DEFAULT= "$GRUB_ CMDLINE_ LINUX_DEFAULT crashkernel= 1G-:512M"