Hello bugproxy, or anyone else affected, Accepted makedumpfile into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1.5.5-2ubuntu1.5 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 Trusty) 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/1464833 Title: Unable to configure Firmware Assisted dump Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Trusty: Fix Committed Bug description: [SRU justification] This represent a hardware enablement SRU : Firmware assisted dumps (fadump) are not possible on LTS. [Impact] The fadump mechanism cannot be used on Power systems running Trusty [Fix] Backport fadump functionality from makedumpfile 1.5.8 present in Wily and onward. [Test Case] See comment #9 : The proposed SRU has been tested from a PPA on a Power VM. [Regression] None expected from a functionality point of view as it is a new feature. Existing code paths are minimally modified. [Original description of the problem] ---Steps to Reproduce--- 1) Using latest daily ISO install 14.04.02 as a Power VM guest. 2) Upgrade the kernel to 3.19 level (3.19.0-18-generic) 3) In order to use Firmware Assisted Dump feature update the kernel command with fadump=on. 4) Reboot. Post reboot using kdump-config load command fails with following message : # kdump-config load Memory for crashkernel is not reserved Please reserve memory by passing"crashkernel=X@Y" parameter to kernel Then try to loading kdump kernel * failed to load kdump kernel # kdump-config status current state : Not ready to kdump # # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-3.19.0-18-generic root=UUID=3ea23bcf-7269-432f-bacc-f82c6cdd774e ro splash quiet fadump=on crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 # cat /sys/kernel/fadump_enabled 1 # cat /sys/kernel/fadump_registered 0 # # dmesg | grep -i Firmware [ 0.000000] Reserved 5120MB of memory at 97279MB for firmware-assisted dump [ 0.000000] firmware_features = 0x00000001c45ffc5f # # cat /boot/config-3.19.0-18-generic | grep -i FA_DUMP CONFIG_FA_DUMP=y # Are there any user space fixes missing which prevents me from configuring firmware assisted dump ? == Comment: #4 - Hari Krishna Bathini <hbath...@in.ibm.com> - 2015-06-12 05:28:24 == This patch makes kdump-tools fadump aware so as to switch between kdump & fadump seemlessly based on the dump method enabled (fadump/kdump). Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1464833/+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