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 Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800566
Title:
Make reset_devices parameter default for kdump
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Trusty:
Won't Fix
Status in makedumpfile source package in Xenial:
In Progress
Status in makedumpfile source package in Bionic:
In Progress
Status in makedumpfile source package in Cosmic:
Won't Fix
Status in makedumpfile source package in Disco:
In Progress
Status in makedumpfile source package in Eoan:
In Progress
Status in makedumpfile source package in Focal:
Fix Released
Bug description:
[Impact]
* Kdump does not configure by default the crash kernel to perform a
device reset by default, by passing the "reset_devices" parameter.
* Kernel has the "reset_devices" parameter that drivers can opt-in,
and perform special activity in case this parameter is parsed from
command-line. For example, in kdump kernels it hints the drivers that
they are booting from a non-healthy condition and needs to issue some
form of reset to the adapter, like clearing DMA mapping in their
firmware for example. Users currently (kernel v5.5-rc2) are: aacraid,
hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.
This should be enabled by default in the kdump config file to be added
in the kdump kernel command-line for all versions.
[Test Case]
1) Deploy a Bionic VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'reset_devices' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is low, since it doesn't need any changes in
makedumpfile code and we're only adding a parameter on the crash
kernel command-line. The risks are related with bad behavior with the
kernel when using "reset_devices", like if the driver has bugs in this
path. It's considered safer to have the option (and this way prevent
problems for booting a unhealthy kernel with potential stuck DMAs in
the devices) than not having it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+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
