kernel-packages team mailing list archive

[Chris J Arges <1475497@xxxxxxxxxxxxxxxxxx>]

Hi,
Did you modify '/etc/default/kdump-tools' to have USE_KDUMP=1?
That will update the grub entry to have a crashkernel entry. From there you can reboot and re-check status.

Do you have a normal use case on how to use fadump? This will help in reproducing this on this end.
Thanks,
--chris

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1475497

Title:
  Unable to configure Firmware Assisted dump

Status in kexec-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  ---Steps to Reproduce---
  1) Using latest daily ISO install ubuntu15.10 as a Power VM guest. 
  2) Upgrade the kernel to 4 level (4.0.0-4-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-4.0.0-4-generic root=UUID=6298dfdc-e683-473d-a8bc-b3249731b356 ro splash quiet fadump=on fadump_reserve_mem=512M crashkernel=512M

  #cat /sys/kernel/fadump_enabled
  1

  #cat /sys/kernel/fadump_registered 
  0

  # dmesg | grep -i Firmware
  [    0.000000] Reserved 512MB of memory at 3583MB for firmware-assisted dump
  [    0.000000] firmware_features = 0x00000001c45ffc5f


  #cat /boot/config-4.0.0-4-generic | grep -i FA_DUMP
  CONFIG_FA_DUMP=y
   

  
  I think userspace tool is missing for fadump as kdump config file not aware about fadump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1475497/+subscriptions