bow...@gmail.com said:
The problem is that they start in sync and over the course of a day drift
that far apart despite having NTP running. We're not sure why NTP isn't
correcting it along the way. Though at this point, we are looking at a
firmware bug.
I wouldn't think of it as two systems
Comments inline.
On Oct 5, 2012, at 18:26, Hal Murray hmur...@megapathdsl.net wrote:
bow...@gmail.com said:
The problem is that they start in sync and over the course of a day drift
that far apart despite having NTP running. We're not sure why NTP isn't
correcting it along the way.
The problem stems from one of the two (identical) machines drifting off by
60-70 seconds per day. So a few ms here and there are ok.
[]
Bob
==
Bob,
NTP is normally limited to a +/- 500 parts per million correction - 43
seconds per day. You may be operating
David,
The problem is that they start in sync and over the course of a day drift that
far apart despite having NTP running. We're not sure why NTP isn't correcting
it along the way. Though at this point, we are looking at a firmware bug.
Thanks!
Bob
On Oct 5, 2012, at 12:30 AM, David J Taylor
I had an early Phenom II that lost time while turned on but the
internal CMOS clock did not so rebooting or reading the CMOS clock
restored the correct time. There was a problem with the System
Management Mode code and The C1E CPU state which was new at that time
where an interrupt was being
