------- Comment From hbath...@in.ibm.com 2020-01-15 15:34 EDT-------
Verified successfully on eoan with kdump-tools
version 1:1.6.6-2ubuntu2

------- Comment From hbath...@in.ibm.com 2020-01-15 15:36 EDT-------
Verified successfully on xenial with kdump-tools version

------- Comment From hbath...@in.ibm.com 2020-01-15 15:38 EDT-------
Verified successfully on bionic with kdump-tools version

** Tags removed: verification-needed-eoan verification-needed-xenial
** Tags added: verification-done-eoan verification-done-xenial

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.

  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  Won't Fix
Status in makedumpfile source package in Eoan:
  Fix Committed
Status in makedumpfile source package in Focal:
  Fix Released

Bug description:
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
                               --- STRUCK HERE ---

  ---uname output---

  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

To manage notifications about this bug go to:

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

Reply via email to