Re: Watchdog problem

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Sa, 07.09.19 15:11, Mikael Djurfeldt (mikael@xxxxxxxxxxxxx) wrote:

> Hi,
>
> I couldn't figure out a better place to ask this question. Please point me
> to another place if you have a better idea. (Perhaps I should bring it up
> with VirtualBox developers instead?)
>
> I run Debian buster (with some upgraded packages) as a Virtualbox guest
> with a Windows host.
>
> When the host has gone to sleep and wakes up again, I get logged out from
> my gdm session. It starts out like this:
>
> Sep  7 13:23:58 hat kernel: [82210.177399] 11:23:58.337557 timesync
> vgsvcTimeSyncWorker: Radical guest time change: 2 491 379 233 000ns
> (GuestNow=1 567 855 438 281 378 000 ns GuestLast=1 567 852 946 902 145 000
> ns fSetTimeLastLoop=false)
> Sep  7 13:23:59 hat systemd[1]: systemd-logind.service: Watchdog timeout
> (limit 3min)!
> Sep  7 13:23:59 hat /usr/lib/gdm3/gdm-x-session[1285]: (EE)
> Sep  7 13:23:59 hat /usr/lib/gdm3/gdm-x-session[1285]: Fatal server error:
> Sep  7 13:23:59 hat /usr/lib/gdm3/gdm-x-session[1285]: (EE) systemd-logind
> disappeared (stopped/restarted?)
>
> Can I fix this by setting systemd-logind.service WatchdogSec to something
> else? What should I set it to to disable watchdogs? I tried to find
> documentation for WatchdogSec but failed. Can you please point me to the
> proper documentation?

This looks like a kernel/virtualbox issue. We use CLOCK_MONOTONIC to
determine when the last keep-alive message was received. Unlike
CLOCK_REALTIME this means the clock stops while the system is
suspended. If Virtualbox doesn't get this right, please report this as
issue to virtualbox.

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel