Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

[Gert Wollny]

Am Dienstag, den 20.02.2018, 15:31 +0100 schrieb Michael Biebl:
> 
> > Kernel: Linux 4.15.1-cm-fx6-my (SMP w/4 CPU cores; PREEMPT)
> 
> 
> Does this also happen with a Debian provided kernel? If so, which
> kernel version is that? 
I haven't tried this so far, for that reason I was initially also a bit
reluctant to report the bug here and I didn't report anything against
the kernel package. There is another problem: reproducing the bug is
not straightforward: in theory I should be able to trigger it by
setting the clock to a time past the year 2038, but hwclock doesn't let
me, and unplugging the device also doesn't switchset the RTC to a bogus
value right away.

> Which hardware?

Utilite pro (i.e. Freescale i.MX6 Quad) with the RTC EM Microelectronic
EM3027. While other kernel drivers, like rtc-mv.c, have a fail-save
against dates past 2038 that should alleviate the problem, this clock
driver hasn't.