This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.1
---------------
makedumpfile (1:1.5.9-5ubuntu0.1) xenial; urgency=medium
[ Hari Bathini <hbath...@linux.vnet.ibm.com> ]
* Fix networked kdump failure to reach remote server.
Avoids "Network is unreachable" message when trying to do remote dumps on
either SSH or NFS. (LP: #1571590)
* Replace maxcpus by nr_cpus
nr_cpus is a hard limit that has an impact on the (kdump) kernel
memory consumption, while it is not the case with maxcpus=1, as we can
theoretically hotplug cpus with maxcpus=1 (LP: #1568952)
* define_stampdir() : Loop on hostname -I for 5 sec to get IP address
if HOSTTAG=ip. The network stack may not be ready when kdump-config runs.
Give it some time before reverting HOSTTAG to hostname if an IP address
cannot be found. (LP: #1599561)
* Add cio_ignore result to /etc/default/kdump-tools on s390x
In order to have crashkernel=128M to work correctly on the s390
architecture the result of cio_ignore -u -k needs to be appended to the
KDUMP_CMDLINE_APPEND variable in /etc/default/kdump-tools. This patch
adds the required logic to do the proper modification. (LP: #1570775)
* debian/rules : drop the dh_installinit override
Uses a syntax which is no longer supported and generate an error on
install. (LP: #1599491)
-- Louis Bouchard <louis.bouch...@ubuntu.com> Fri, 22 Jul 2016
10:15:20 +0200
** 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 makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1570775
Title:
makekdump should re-exec with cio_ignore on s390x
Status in Ubuntu on IBM z Systems:
Fix Released
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Xenial:
Fix Released
Bug description:
[SRU justification]
kernel crash dump fails to work without the modification.
[Impact]
Broken functionality.
[Fix]
Add cio_ignore -k -y output to the kexec command.
[Test Case]
Follow indication in comment #2 to reproduce. With the fix, kdump will
function as expected.
[Regression]
A regression situation is outlined in comment #16. Newer channel devices may
not be visible because of the added cio_ignore output. This may be worked
around with a single command.
The resolution outweights this limitation that can be easily worked
around.
[Original description of the problem]
As per
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/comments/19
We should re-exec with cio_ignore lines. As per report there, it
should result in lowered required crashdump setting.
Hypothetically, one should be able to test this imperially by lowering
crashdump memory settings until kdump does not succeed anymore. And
then generated and append `cio_ignore -k -u` to the
KDUMP_CMDLINE_APPEND= and see that kdump starts working again with a
lower memory usage.
Once this is developed / verified / tested, we should probably SRU
this back to xenial.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1570775/+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
