On Tue, Feb 25, 2014 at 01:45:08PM -0500, Neal Becker wrote:
Don't know if it's related, but I just saw this:
...
Feb 25 12:06:18 nbecker7 kernel: [ 66.668588] virbr0: port
1(virbr0-nic)
entered disabled state
Feb 25 12:06:54 nbecker7 kernel: [ 109.855407] fuse init (API version 7.22)
Jan 8 10:48:32 nbecker7 systemd: Stopped target Graphical Interface.
...
Was your hardware clock also modified or happenings on a virtual machine
left it alone? In my case something changed that as well.
If you shut down with a new clock value, did not use BIOS to reset it
and your machine syncs via NTP then the next boot will start with a
wrong date and suddenly time will be corrected when chronyd or ntpd will
kick in. An output from 'last -5 reboot' looks in such case quite
"interesting".
Michal