[systemd-devel] Hardware watchdog support, slug speed.

Zbigniew Jędrzejewski-Szmek zbyszek at in.waw.pl
Mon Mar 11 15:42:44 PDT 2013

On Mon, Mar 11, 2013 at 11:11:19PM +0100, Sébastien Luttringer wrote:
> After reexecuting the daemon, I got the following info in the journal.
> # systemctl daemon-reexec
> # LC_ALL=C journalctl -f
> mars 11 20:50:15 slice systemd[1]: systemd 198 running in system mode.
> mars 11 20:50:15 slice systemd[1]: Hardware watchdog 'SBC-FITPC2
> Watchdog', version 0
> mars 11 20:50:16 slice systemd[1]: Set hardware watchdog to 1min.
> mars 11 20:50:16 slice systemd[1]: Failed to enable hardware watchdog:
> Inappropriate ioctl for device
Hi Sébastien,
thank you for the great bug report.

> So, I thnk this code should be reworked and only do the ioctl at
> interval defined in RuntimeWatchdogSec, firstly because we use too
> many cycle (global speed/power) and
> secondly, because there is no way to trigger a system reset by the
> wathdog in these condition.
> I'm also interogative about calling ioctl (and trying to reopen
> /dev/watchdog) even when the initial setup of the watchdog have
> failed.
> I could provide some patches to fix this if you are interested.
Definitely. There are some places in systemd where unexpected failure
results in excessive usage of resources. Patches (preferably two,
for the two separate issues you describe) are always welcome.


More information about the systemd-devel mailing list