------- Comment From hbath...@in.ibm.com 2018-03-22 13:18 EDT------- (In reply to comment #32) > (In reply to comment #31) > > Could you please comment as to whether the workaround resolved the issue? > > Yes, the workaround resolves the issue. But could we have a udev rule added > in kdump-tools > to trigger kdump-tools.service restart after a DLPAR memory/CPU add/remove > operation > instead of manually restarting kdump-tools service after a DLPAR operation..
Basically, a udev rule file that looks like this: 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" put in "/lib/udev/rules.d" dir as part of the kdump-tools package to avoid the need to manually reload kdump.. Thanks Hari -- 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
