It turns out the problem is a kernel bug, version 5.7.3. See: https://bugzilla.kernel.org/show_bug.cgi?id=208221
So that is cleared up. Now to figure out how to fix things that are time stamped in the future. On Fri, Jun 19, 2020 at 07:24:09AM -0700, [email protected] wrote: > OK I've discovered my system time is wandering: > > [root@cave etc]# hwclock --show > 2020-05-28 01:43:00.648034-07:00 > [root@cave etc]# hwclock --show > 2020-05-12 12:53:28.481286-07:00 > [root@cave etc]# for i in 1 2 3 4 ; do hwclock --show ; sleep 2 ; done > 2020-07-07 04:51:42.331546-07:00 > 2020-06-29 02:40:54.721810-07:00 > 2020-07-02 23:53:22.023450-07:00 > 2020-06-30 01:59:06.804296-07:00 > [root@cave etc]# > > as you can see the hwclock varies - a lot. > This is the real time clock. What?? > > Attempting to set it: > hwclock --systohc > > Doesn't help. > > This system is a VPS, so I cannot replace the CMOS battery. > > Suggestions? > > > > -- > Michael Rasmussen > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug -- _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
