------- Comment From hbath...@in.ibm.com 2019-05-07 15:03 EDT------- While I initially suggested the udev below rules:
SUBSYSTEM=="memory", ACTION=="online", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="memory", ACTION=="offline", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" request you use the below rules instead: SUBSYSTEM=="memory", ACTION=="online", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="memory", ACTION=="offline", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-restart kdump-tools.service" because ppc64 does not follow the standard CPU hot add framework where add/remove event is ejected on CPU hot add/remove operation. It only ejects online/offline event to user space when CPU is hot added/removed. This is because /sys/devices/system/cpu/cpuX nodes are present for all "possible", irrespective of whether a CPU is hot-added/removed. So, a udev event only for CPU hot add (online) is sufficient to pass on an updated DT blob for kdump kernel to scan for CPUs... Also, ran into a couple of other bugs (IBM bug 177451 & IBM bug 177452) while validating this fix on bionic 4.15.0-48-generic and 4.18.0-18-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655280 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
