Mirslav,
You have something seriously wrong. The frequency was apparently set
correctly at -168 PPM, then shortly after that there was a series of
step corrections about 172 ms in 20 min, which is about 170 PPM. In
other words, the frequcny change did not work. It certainly worke here,
even with the kernel enabled. You should see the frequency change in the
loopstats. If not, try disabling the kernel to see if that is the problem.
Dave,
Miroslav Lichvar wrote:
On Wed, Oct 27, 2010 at 11:55:22PM +0000, David L. Mills wrote:
See the most recent ntp-dev. It needed some tuning.
Hm, with ntp-dev-4.2.7p74 it still doesn't seem to work as expected.
In the same testing conditions as I used the last time, the frequency
estimate is now 170 ppm off and the clock is stepped several times
before it settles down.
http://mlichvar.fedorapeople.org/tmp/ntp_start4.png
1 Jan 01:00:00 ntpd.new2[3135]: ntpd 4.2.7...@1.2307 Mon Nov 1 12:20:56 UTC
2010 (1)
1 Jan 01:00:00 ntpd.new2[3135]: proto: precision = 0.101 usec
1 Jan 01:00:00 ntpd.new2[3135]: ntp_io: estimated max descriptors: 1024,
initial socket boundary: 16
1 Jan 01:00:00 ntpd.new2[3135]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
1 Jan 01:00:00 ntpd.new2[3135]: Listen normally on 1 lo 127.0.0.1 UDP 123
1 Jan 01:00:00 ntpd.new2[3135]: Listen normally on 2 eth0 192.168.123.4 UDP 123
1 Jan 01:00:00 ntpd.new2[3135]: 192.168.123.1 8011 81 mobilize assoc 9201
1 Jan 01:00:00 ntpd.new2[3135]: 0.0.0.0 c016 06 restart
1 Jan 01:00:00 ntpd.new2[3135]: 0.0.0.0 c012 02 freq_set ntpd 0.000 PPM
1 Jan 01:00:00 ntpd.new2[3135]: 0.0.0.0 c011 01 freq_not_set
1 Jan 01:00:01 ntpd.new2[3135]: 192.168.123.1 8024 84 reachable
1 Jan 01:03:17 ntpd.new2[3135]: 192.168.123.1 963a 8a sys_peer
1 Jan 01:03:17 ntpd.new2[3135]: 0.0.0.0 c614 04 freq_mode
1 Jan 01:08:43 ntpd.new2[3135]: 0.0.0.0 0612 02 freq_set ntpd -168.875 PPM
1 Jan 01:08:43 ntpd.new2[3135]: 0.0.0.0 0615 05 clock_sync
1 Jan 01:32:42 ntpd.new2[3135]: 0.0.0.0 0613 03 spike_detect +0.160001 s
1 Jan 01:41:23 ntpd.new2[3135]: 0.0.0.0 061c 0c clock_step +0.172040 s
1 Jan 01:41:23 ntpd.new2[3135]: 0.0.0.0 0615 05 clock_sync
1 Jan 01:41:24 ntpd.new2[3135]: 0.0.0.0 c618 08 no_sys_peer
1 Jan 01:41:24 ntpd.new2[3135]: 192.168.123.1 8044 84 reachable
1 Jan 01:45:53 ntpd.new2[3135]: 192.168.123.1 965a 8a sys_peer
1 Jan 01:58:07 ntpd.new2[3135]: 0.0.0.0 0613 03 spike_detect +0.140452 s
1 Jan 02:06:52 ntpd.new2[3135]: 0.0.0.0 061c 0c clock_step +0.170957 s
1 Jan 02:06:52 ntpd.new2[3135]: 0.0.0.0 0615 05 clock_sync
1 Jan 02:06:53 ntpd.new2[3135]: 0.0.0.0 c618 08 no_sys_peer
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
