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

[Michael Biebl]

Am 20.02.2018 um 12:40 schrieb Gert Wollny:
> on an 32 bit arm system when the RTC is set to a wrong time booting the system might 
> fail because systemd gets stuck in a loop printing "systemd[1]: Time has been changed". 
> 
> The problem is known upstream and claimed to be a problem of the kernel: 
>   https://github.com/systemd/systemd/issues/1143
> 
> However, while upstream is certainly correct that a kernel bug is the trigger of 
> the lockup, 


...

> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: armhf (armv7l)
> 
> 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? Which hardware?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180220/b8ab60b4/attachment-0002.sig>