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?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
