Assigned to mvo; please investigate this. Possibilities are that it's caused by faulty hardware clocks, and somehow it's not being set correctly (by the udev 85-hwclock.rules).
Or maybe it's something even weirder.
Assigned to mvo; please investigate this. Possibilities are that it's caused by faulty hardware clocks, and somehow it's not being set correctly (by the udev 85-hwclock.rules).
Or maybe it's something even weirder.