On Wed, Oct 12, 2011 at 20:21, A C <[email protected]> wrote: >> o127.127.22.1 .PPS. 0 l 5 16 377 0.000 3.009 >> 0.061 > > Note the offset shown is 3 ms (time1 is 0.003) and it varies slightly by a > few tens of microseconds based on the jitter in the system. Kernel PPS is > implemented in this case.
Try turning off kernel PPS (also known as hardpps) by setting flag3 0 or leaving it default for the PPS driver. I see ntpd 4.2.6p3 code adding fudgetime1 to the PPS timestamp from PPSAPI, but I don't see how the hardpps support in the kernel would get that fudge time1 to be able to similarly compensate its direct PPS synchronization. Cheers, Dave Hart _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
