This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1
---------------
makedumpfile (1:1.6.5-1ubuntu1) disco; urgency=low
[ Ubuntu Merge-o-Matic ]
* Merge from Debian unstable. Remaining changes:
- Bump amd64 crashkernel from 384M-:128M to 512M-:192M.
[ Thadeu Lima de Souza Cascardo ]
* Use a different service for vmcore dump. (LP: #1811692)
makedumpfile (1:1.6.5-1) unstable; urgency=medium
* Update to new upstream version 1.6.5.
* debian: remove debian/source/local-options
* [i18n] Move PT debconf translation (Closes: #910465)
makedumpfile (1:1.6.4-3) unstable; urgency=medium
* Reload kdump after memory/CPU hotplug. (LP: #1655280)
* Fix adding crashkernel to zipl.conf when no quotation mark is used.
(LP: #1790788)
-- Thadeu Lima de Souza Cascardo <casca...@canonical.com> Mon, 14 Jan
2019 15:42:44 -0200
** Changed in: makedumpfile (Ubuntu Disco)
Status: Fix Committed => 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/1811692
Title:
udev coldplug will interrupt makedumpfile
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Disco:
Fix Released
Bug description:
After introducing the udev rules to restart kdump-tools service when
there is memory or cpu hotplug, it will be restarted during coldplug
as well. This will cause the dump capture itself to be interrupted
after a crash. When it is restarted and tries to dump again, it will
find an existing dump file and will fail to dump.
My proposed solution is to use a different systemd service for the
real capture.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1811692/+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
