This bug was fixed in the package makedumpfile - 1:1.6.6-2ubuntu1 --------------- makedumpfile (1:1.6.6-2ubuntu1) eoan; urgency=medium
[ Thadeu Lima de Souza Cascardo ] * Merge from Debian unstable. Remaining changes: - Bump amd64 crashkernel from 384M-:128M to 512M-:192M. * Add kdump retry/delay mechanism when dumping over network (LP: #1681909) * Allow proper reload of kdump after multiple hotplug events. (LP: #1828596) [ Connor Kuehl ] * Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860) makedumpfile (1:1.6.6-2) unstable; urgency=medium [ Guilherme G. Piccoli ] * Add kdump retry/delay mechanism when dumping over network [ Thadeu Lima de Souza Cascardo ] * Use a different service for vmcore dump. * Use maxcpus instead of nr_cpus on ppc64el. * Reload kdump when CPU is brought online. * Allow proper reload of kdump after multiple hotplug events. makedumpfile (1:1.6.6-1) unstable; urgency=medium * Update to new upstream version 1.6.6. -- Thadeu Lima de Souza Cascardo <casca...@canonical.com> Tue, 06 Aug 2019 12:18:15 -0300 ** Changed in: makedumpfile (Ubuntu Eoan) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741860 Title: Use the kernel default for crashkernel offset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs