kexec-tools/98-kexec.rules

SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump.service"
SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump.service"
SUBSYSTEM=="memory", ACTION=="online", PROGRAM="/bin/systemctl try-restart kdump.service"
SUBSYSTEM=="memory", ACTION=="offline", PROGRAM="/bin/systemctl try-restart kdump.service"
Revert "Improve 'cpu add' udev rules" This reverts commit 65d37d19c783081041485ff75dccd9465b8dabb5. Since we have no such bugs in Fedora and original rule works fine thus revert it. 2017-08-17 08:42:11 +00:00			`SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump.service"`
			`SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump.service"`
Fix kdump udev memory event restarts During debugging of another problem issues were noted with the kdump udev rules. The kdump service is restarted on memory add and remove events. These are the wrong events for these types of devices and result in an overly aggressive restarting of the kdump service. There are four udev events to consider, "add", "remove", "online", and "offline". The remove event is a complete removal from the system -- neither the hardware nor the kernel know about the hardware; it has been physically removed. The add event is associated with hardware being physically added to the system. The kernel has some limited knowledge of the device, however, it is not avaiable for the kernel to use until it is brought online. Online events refer to the device being available for the kernel to use. Opposite to that is the offline event, which occurs when a device is no longer in use by the kernel. Note that in all four events the kernel may have some remaining information stored about the device. In the case of memory hotplug, kdump should be restarted when a memory module is onlined or offlined. This is because the memory is not in use by the kernel until the memory is onlined, and it is unused when the memory is offlined. Making these modifications results in smooth service on systems that do heavy memory onlining and offlining. Cc: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Prarit Bhargava <prarit@redhat.com> Acked-by: Vivek Goyal <vgoyal@redhat.com> 2014-05-02 14:28:50 +00:00			`SUBSYSTEM=="memory", ACTION=="online", PROGRAM="/bin/systemctl try-restart kdump.service"`
			`SUBSYSTEM=="memory", ACTION=="offline", PROGRAM="/bin/systemctl try-restart kdump.service"`