Hello Dimitri, or anyone else affected, Accepted makedumpfile into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.5.9-5ubuntu0.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: makedumpfile (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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 Committed 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
