--- Comment From hbath...@in.ibm.com 2020-01-16 11:02 EDT---
(In reply to comment #78)
> Hello Hari,
>
> Glad to see you around on bugs again. :)
Thanks, Mauricio :)
> Could you please confirm whether the fix for this bug also addresses LP bug
> 1655280?
> (i.e., the verification for
--- Comment From hbath...@in.ibm.com 2019-10-25 06:29 EDT---
(In reply to comment #49)
> New version on ppa:cascardo/ppa for bionic. That should handle fadump and
> lock in the case of try-reload/condreload.
>
> Hari, can you give it a try?
Thanks, Cascardo. That works well for FADump
--- Comment From hbath...@in.ibm.com 2019-09-25 02:41 EDT---
(In reply to comment #47)
> Hi, Hari.
>
> makedumpfile 1:1.6.5-1ubuntu1~18.04.2+cascardo2 on ppa:cascardo/ppa uses a
> try-reload instead. Can you test it, please?
Cascardo, try-reload is not considering fadump case (supported
--- Comment From hbath...@in.ibm.com 2019-09-23 13:28 EDT---
Sorry about the delay. Observed that kdump/fadump is loaded even when
kdump-tools service is disabled. Not desirable, I guess. Probably need to
check if kdump-tools service is active before trying a reload?
--
You received this
--- Comment From hbath...@in.ibm.com 2019-07-26 06:48 EDT---
Guilherme, the initial fix (udev rule) is still available. But while testing I
observed failure
due to systemd ratelimiting. I proposed to disable ratelimit but IIUC, Cascardo
preferred a different approach that does not involve
--- Comment From hbath...@in.ibm.com 2019-07-25 05:43 EDT---
(In reply to comment #27)
> Disabling the ratelimit in general would break other failure modes, so I
> would rather just reset-failed when calling try-restart because of the
> hotplug events.
>
> Can you try the package in
--- Comment From hbath...@in.ibm.com 2019-07-15 06:36 EDT---
Cascardo, I did not tinker with other options but disabling ratelimit helped:
"StartLimitInterval=0"
"systemctl reset-failed kdump-tools.service" seems like a good option but
may not be needed if ratelimit is disabled..
Thanks
On Mon, Jun 24, 2019 at 11:59:48AM -, bugproxy wrote:
> --- Comment From hbath...@in.ibm.com 2019-06-24 07:49 EDT---
> Thanks for the change. With it, try-restart is being triggered for
> kdump-tools service after CPU add operation but systemd reported
> failure with below logs:
>
>
--- Comment From hbath...@in.ibm.com 2019-06-24 07:49 EDT---
Thanks for the change. With it, try-restart is being triggered for
kdump-tools service after CPU add operation but systemd reported
failure with below logs:
Jun 24 06:47:06 ubuntu systemd[1]: Stopped Kernel crash dump capture
--- Comment From hbath...@in.ibm.com 2019-05-22 07:16 EDT---
(In reply to comment #12)
[...]
> But I thought this rules were there by accident and the entries would be put
> under arch flags to avoid them for ppc64..
If that is too much to ask, I am fine with the current change.
The
--- Comment From hbath...@in.ibm.com 2019-05-22 02:33 EDT---
(In reply to comment #11)
> Hi, Hari.
>
> So, as you said, other architectures will use add/remove instead of online,
> and we want to support them too. Any reason not to do it that you are
> thinking of?
No action with these
--- Comment From hbath...@in.ibm.com 2019-05-21 06:16 EDT---
Cascardo, the udev rules (/lib/udev/rules.d/50-kdump-tools.rules) should have
been:
SUBSYSTEM=="memory", ACTION=="online", PROGRAM="/bin/systemctl try-restart
kdump-tools.service"
SUBSYSTEM=="memory", ACTION=="offline",
12 matches
Mail list logo
