Miroslav,
This doesn't make any sense. Your data show the frequency set to 0.0 and
the a series of clock steps after that. If this is with your simulator,
try it with the real machine. I have tested with three machines herewith
and without kernel and with no such problems.
Dave
Miroslav Lichvar wrote:
On Mon, Nov 01, 2010 at 02:29:58PM +0000, David L. Mills wrote:
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.
That was with disabled kernel. With kernel loop I'm getting similar
results. The real frequency offset is 0, so I'd think the initial
estimation should be close to 0 too.
Here is log and loopstats for another run with daemon loop:
1 Jan 01:00:00 ntpd.new2[4684]: ntpd 4.2.7...@1.2307 Mon Nov 1 12:20:56 UTC
2010 (1)
1 Jan 01:00:00 ntpd.new2[4684]: proto: precision = 0.101 usec
1 Jan 01:00:00 ntpd.new2[4684]: ntp_io: estimated max descriptors: 1024,
initial socket boundary: 16
1 Jan 01:00:00 ntpd.new2[4684]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
1 Jan 01:00:00 ntpd.new2[4684]: Listen normally on 1 lo 127.0.0.1 UDP 123
1 Jan 01:00:00 ntpd.new2[4684]: Listen normally on 2 eth0 192.168.123.4 UDP 123
1 Jan 01:00:00 ntpd.new2[4684]: 192.168.123.1 8011 81 mobilize assoc 9201
1 Jan 01:00:00 ntpd.new2[4684]: 0.0.0.0 c016 06 restart
1 Jan 01:00:00 ntpd.new2[4684]: 0.0.0.0 c012 02 freq_set ntpd 0.000 PPM
1 Jan 01:00:00 ntpd.new2[4684]: 0.0.0.0 c011 01 freq_not_set
1 Jan 01:00:01 ntpd.new2[4684]: 192.168.123.1 8024 84 reachable
1 Jan 01:03:17 ntpd.new2[4684]: 192.168.123.1 963a 8a sys_peer
1 Jan 01:03:17 ntpd.new2[4684]: 0.0.0.0 c614 04 freq_mode
1 Jan 01:08:47 ntpd.new2[4684]: 0.0.0.0 0612 02 freq_set ntpd -165.821 PPM
1 Jan 01:08:47 ntpd.new2[4684]: 0.0.0.0 0615 05 clock_sync
1 Jan 01:31:54 ntpd.new2[4684]: 0.0.0.0 0613 03 spike_detect +0.153100 s
1 Jan 01:35:07 ntpd.new2[4684]: 0.0.0.0 061c 0c clock_step +0.171386 s
1 Jan 01:35:07 ntpd.new2[4684]: 0.0.0.0 0615 05 clock_sync
1 Jan 01:35:08 ntpd.new2[4684]: 0.0.0.0 c618 08 no_sys_peer
1 Jan 01:35:08 ntpd.new2[4684]: 192.168.123.1 8044 84 reachable
1 Jan 01:45:17 ntpd.new2[4684]: 192.168.123.1 965a 8a sys_peer
1 Jan 01:59:34 ntpd.new2[4684]: 0.0.0.0 0613 03 spike_detect +0.144404 s
1 Jan 02:01:46 ntpd.new2[4684]: 0.0.0.0 061c 0c clock_step +0.167177 s
1 Jan 02:01:46 ntpd.new2[4684]: 0.0.0.0 0615 05 clock_sync
1 Jan 02:01:47 ntpd.new2[4684]: 0.0.0.0 c618 08 no_sys_peer
1 Jan 02:01:47 ntpd.new2[4684]: 192.168.123.1 8064 84 reachable
1 Jan 02:11:48 ntpd.new2[4684]: 192.168.123.1 967a 8a sys_peer
1 Jan 02:28:13 ntpd.new2[4684]: 0.0.0.0 0613 03 spike_detect +0.146559 s
1 Jan 02:33:39 ntpd.new2[4684]: 0.0.0.0 061c 0c clock_step +0.182170 s
1 Jan 02:33:39 ntpd.new2[4684]: 0.0.0.0 0615 05 clock_sync
1 Jan 02:33:40 ntpd.new2[4684]: 0.0.0.0 c618 08 no_sys_peer
1 Jan 02:33:40 ntpd.new2[4684]: 192.168.123.1 8084 84 reachable
1 Jan 02:44:53 ntpd.new2[4684]: 192.168.123.1 969a 8a sys_peer
1 Jan 03:00:15 ntpd.new2[4684]: 0.0.0.0 0613 03 spike_detect +0.147427 s
1 Jan 03:07:51 ntpd.new2[4684]: 0.0.0.0 061c 0c clock_step +0.171264 s
1 Jan 03:07:51 ntpd.new2[4684]: 0.0.0.0 0615 05 clock_sync
1 Jan 03:07:52 ntpd.new2[4684]: 0.0.0.0 c618 08 no_sys_peer
51544 197.102 -0.099862463 0.000 0.035306712 0.000000 6
51544 527.102 -0.054723795 -165.821 0.039326766 0.000000 6
51544 591.102 -0.024111853 -165.821 0.038345881 0.000000 6
51544 658.102 0.003622031 -165.821 0.037185371 0.000000 6
51544 919.102 0.043855357 -165.139 0.037579887 0.241212 6
51544 1451.103 0.060703080 -163.214 0.035653859 0.716975 6
51544 1584.102 0.104651664 -162.384 0.036793107 0.732004 6
51544 2107.273 0.000000000 -162.384 0.000000119 0.684727 6
51544 2717.102 0.088034845 -159.184 0.031125018 1.300354 6
51544 2850.102 0.109450728 -158.316 0.030083233 1.254456 6
51544 3045.102 0.121347186 -156.906 0.028452882 1.274993 6
51544 3706.269 0.000000000 -156.906 0.000000119 1.192647 6
51544 4308.102 0.094251577 -153.524 0.033322965 1.635326 6
51544 4374.102 0.098657012 -153.135 0.031209669 1.535849 6
51544 4900.102 0.127630261 -149.134 0.030938959 2.016296 6
51544 5619.284 0.000000000 -149.134 0.000000119 1.886072 6
51544 6293.102 0.080298556 -145.908 0.028389827 2.100808 6
51544 6361.102 0.105205597 -145.482 0.027978198 1.970900 6
51544 6425.102 0.108166860 -145.069 0.026192141 1.849371 6
51544 6555.102 0.114087990 -144.185 0.024589778 1.757936 6
51544 7084.102 0.126352510 -140.201 0.023406780 2.165198 6
51544 7671.273 0.000000000 -140.201 0.000000119 2.025357 6
51544 7876.102 0.028533998 -139.852 0.010088292 1.898554 6
51544 8146.102 0.059726636 -138.891 0.014514631 1.808157 6
51544 8680.102 0.065378885 -136.810 0.013723472 1.844462 6
51544 8745.102 0.096238729 -136.437 0.016847350 1.730365 6
51544 8809.102 0.117385634 -135.990 0.017442850 1.626332 6
51544 9400.248 0.000000000 -135.990 0.000000119 1.521295 6
Here is a plot of real frequency offset, not sure if this will be any
help:
http://mlichvar.fedorapeople.org/tmp/ntp_start4_freq.png
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
