This bug was fixed in the package makedumpfile - 1:1.6.3-2~16.04.1
---------------
makedumpfile (1:1.6.3-2~16.04.1) xenial; urgency=medium
* Backport latest makedumpfile to xenial. (LP: #1746299)
* Revert to build-depending on dh-systemd, as xenial does not have
debhelper >= 9.20160709.
-- Thadeu Lima de Souza Cascardo <casca...@canonical.com> Mon, 21 May
2018 11:02:15 -0300
** Changed in: makedumpfile (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1750021
Title:
fails to dump with latest kpti fixes
Status in linux package in Ubuntu:
Fix Released
Status in makedumpfile package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Invalid
Status in makedumpfile source package in Xenial:
Fix Released
Status in linux source package in Artful:
Fix Released
Status in makedumpfile source package in Artful:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in makedumpfile source package in Bionic:
Fix Released
Bug description:
When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
backported, it broke the exporting of mem_section on vmcoreinfo.
makedumpfile will fail to dump in that case. Backporting a kernel fix
will make it work again, but that means that some kernel versions
won't be dumpable. A solution for makedumpfile should be done as well.
Cascardo.
break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
a0b1280368d1e91ab72f849ef095b4f07a39bbf1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+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
