This is a good suggestion Rich! I've looped Dann and Cascardo, both maintainers of kdump-tools to also discuss this subject.
We could have a more explicit message when installing the package, maybe in the same screen that asks if we want to enable kdump by default. I'm against the idea of _not_ setting the default crashkernel though - good suggestion for intermediate/advanced users, bad suggestion for beginners I think. Also, I must say: my experience was pretty reciprocal to yours. The default always worked for me in regular/simple HW or VMs, it fails in more peculiar setups, like 200 PCI devices, 1 TiB of RAM, etc. Thanks for bringing-up the discussion =) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1931779 Title: kdump just hung out of the box Status in makedumpfile package in Ubuntu: Fix Released Bug description: I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date 20.04 system, installed specifically to try reproducing a bug. But when I tried, after kdump-config status reported "ready to dump" on reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the panic to console and then just hung forever. After some blind guessing and twiddling both variables, I found that crashkernel=512M-:256M works on this particular setup. (MS7850 motherboard, i5-4670 CPU, 5.4.0-42-generic kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1931779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
