This bug was fixed in the package makedumpfile - 1:1.6.6-4ubuntu1
---------------
makedumpfile (1:1.6.6-4ubuntu1) focal; urgency=medium
[ Thadeu Lima de Souza Cascardo ]
* Merge from Debian unstable. Remaining changes:
- Bump amd64 crashkernel from 384M-:128M to 512M-:192M.
* Use reset_devices as a cmdline parameter. (LP: #1800566)
* Use kdump-config reload after cpu or memory hotplug. (LP: #1828596)
[ Guilherme G. Piccoli ]
* Add a systemd-resolved service dependency in order kdump-tools is able
to resolve DNS when in kdump boot. (LP: #1856323)
makedumpfile (1:1.6.6-4) unstable; urgency=medium
* Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860)
* kdump-config: implement try-reload
* udev: hotplug: use try-reload
* Set Rules-Requires-Root to no
makedumpfile (1:1.6.6-3) unstable; urgency=medium
* Add a reload command.
* Use kdump-config reload after cpu or memory hotplug.
* Use reset_devices as a cmdline parameter.
-- Thadeu Lima de Souza Cascardo <casca...@canonical.com> Wed, 18 Dec
2019 14:38:51 -0300
** Changed in: makedumpfile (Ubuntu Focal)
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/1800566
Title:
Make reset_devices parameter default for kdump
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
