Re: TS-7200: time sync issues

[Ken Hornstein <kenh%cmf.nrl.navy.mil@localhost>]

>On Mon, Dec 8, 2008 at 4:52 AM, Ken Hornstein 
><kenh%cmf.nrl.navy.mil@localhost> wrote:
>> Dec  7 20:46:32 modred ntpd[302]: time reset +0.906469 s
>> Dec  7 21:02:04 modred ntpd[302]: time reset +0.573713 s
>> Dec  7 21:18:06 modred ntpd[302]: time reset +0.201409 s
>> Dec  7 21:33:12 modred ntpd[302]: time reset +0.198393 s
>>
>> Eventually what will happen is that ntpd will get "lucky" and get the time
>> within the 128 ms slew threshold, and then ntpd will function normally.
>> I've been trying to figure out what's going on here, but I've had little
>> luck.  Does anyone have any ideas?  Or even an idea of where to start?
>I think this could be similar to
>http://mail-index.netbsd.org/port-arm/2008/06/27/msg000281.html

Thank you for your suggestion ... but I don't think this (and the other
message) you posted relate to this problem.  As I read it, this was
a problem with timecounters and the time got out of whack very quickly.
In my case, the time is "off" after the time is set ... and this problem
existed before timecounters.

(One thought; maybe for some reason hardclock interrupts are blocked
while the TOD clock is being updated?  It doesn't seem like that's the
case from a code inspection, but I could be wrong).

--Ken