kernel-packages team mailing list archive

[bugproxy <bugproxy@xxxxxxxxxx>]

------- Comment From Praveen.Pandey@xxxxxxxxxx 2016-01-21 00:20 EDT-------
Hi ,

Tested on today build and it works fine .

root@tuleta4u-lp6:~# vim /etc/default/kdump-tools
root@tuleta4u-lp6:~# kdump-config load
* fadump registered successfully
root@tuleta4u-lp6:~# dpkg -l | grep makedumpfile
ii  makedumpfile                       1.5.5-2ubuntu1.5                 ppc64el      VMcore extraction tool
root@tuleta4u-lp6:~#

-- 
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 Released

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 <hbathini@xxxxxxxxxx> - 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