I am trying to debug some reboot issues and noticed that the output from $ last show the wrong timestamps as follows. It seems like this has been previously highlighted on the mailing list[1]. The recommended solution seems to be to use fake-hwclock[2]. I am wondering if there is a reason this isnt present in the console image as this does not seem to be a unique problem. Are there any downsides to using fake-hwclock? Of course, I am using ntp as well
last|more
root ttyS0 Fri Dec 22 10:25 still logged in
reboot system boot 4.9.45-ti-r57 Sat Jan 1 08:00 still running
root pts/0 192.168.6.1 Thu Dec 21 17:50 - 20:04 (02:14)
root pts/0 192.168.6.1 Thu Dec 21 17:47 - 17:48 (00:00)
root pts/1 192.168.7.1 Thu Dec 21 16:11 - 16:11 (00:00)
core pts/0 192.168.6.1 Thu Dec 21 14:31 - 17:20 (02:48)
root ttyS0 Thu Dec 21 14:09 - crash (-6564±6:-9)
reboot system boot 4.9.45-ti-r57 Sat Jan 1 08:00 still running
root ttyS0 Thu Dec 21 11:33 - crash (-6564±3:-33)
reboot system boot 4.9.45-ti-r57 Thu Dec 21 11:31 still running
root ttyS0 Thu Dec 21 11:14 - down (00:16)
reboot system boot 4.9.45-ti-r57 Sat Jan 1 08:00 - 11:31 (6564+03:31)
[1] https://groups.google.com/d/msg/beagleboard/tJYoluZxr3s/rL2N0zDdCgAJ
[2] https://packages.debian.org/sid/main/fake-hwclock