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

[Michael Biebl]

On Tue, 20 Feb 2018 19:38:08 +0100 Gert Wollny <gw.fossdev at gmail.com> wrote:
> 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.

I was under the impression, that this issue was fixed in the kernel. So,
are you still running into this with your self-compiled 4.15.1-cm-fx6-my?

-- 
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/20180225/ccaedf35/attachment-0002.sig>