On Dec 11, 2016, at 10:01 PM, geo.inbox.ignored <geo.inbox.ignored at gmail.com> wrote: > - part 1: clock losing time > > first noticed time was off by 8 min, reset via F2 cl terminal. > > ~40 min later, off by ~2 min, reset via 'service manager' by stopping > ntpd, count 20, started ntpd, within a few seconds, clock reset to > correct time. > > ~1 hour later, noticed clock off again, considered cause to be cmos > battery failing. after removing ~30 screws and bottom cover, found > that cmos batter was soldered to board. checked with dvom, voltage > read 3.2v with main battery and charger removed. > > ran web search on tower box to find that cmos battery is a rechargeable > 3.0 v battery and being that removing screws and cover took several > minutes, with battery being up, cause must be elsewhere. > > note - noticed that a time problem was occurring just after tzdata > update on 2016-1201. > > was not able to pursue further due to next problems. It could be a bad drift file. I think it’s normally configured as /var/lib/ntp/drift, but check your ntp.conf. You should try deleting it when the system is up and running at normal temperature and restart ntpd and let it run for a while. -- Jonathan Billings <billings at negate.org>