[ntp:questions] Calling ONCORE owners...
Carl R. Friend
ax197 at osfn.org
Sun Jan 1 15:54:44 UTC 2006
G'day, all.
I've got a Motorola ONCORE UT+ receiver coupled to a Linux box
running NTP 4.1.1 at 1.786 and OS version 2.4.29-NANO. At the duly
appointed hour last evening when I was supposed to get 23:59:60,
the direct output of the satellite receiver indicated such but NTP
never altered the system clock. Further, even with the leap bit set
from the receiver, the leap bits were not set in NTP. Needless to
say, this caused the computer clock to go into a tizzy and it finally
stepped about a half-hour later.
Here's a look just before and just after the leap second:
ntpq> pe
remote refid st t when poll reach delay offset
jitter
==============================================================================
*GPS_ONCORE(0) .GPS. 0 l 13 16 377 0.000 0.004
0.004
LOCAL(0) LOCAL(0) 14 l 38 64 377 0.000 0.000
0.004
+dsl081-199-165. .GPS. 1 u 53 64 377 131.570 5.731
7.171
-sip.eicat.ca ox.eicat.ca 3 - 39 64 377 149.506 0.459
0.437
-underworld.drax .DCFa. 1 - 23 64 377 231.685 20.352
0.111
+elektra.ultra.n tick.usno.navy. 2 - 32 64 377 131.328 3.508
2.774
ntpq> pstatus 50068
status=9614 reach, conf, sel_sys.peer, 1 event, event_reach,
srcadr=GPS_ONCORE(0), srcport=123, dstadr=127.0.0.1, dstport=123,
leap=00, stratum=0, precision=-26, rootdelay=0.000,
rootdispersion=0.004, refid=GPS, reach=377, unreach=0, hmode=3, pmode=4,
hpoll=4, ppoll=4, flash=00 ok, keyid=0, offset=0.004, delay=0.000,
dispersion=0.246, jitter=0.004,
reftime=c76199ff.ffffc41f Sat, Dec 31 2005 18:59:59.999,
org=c76199ff.ffffc41f Sat, Dec 31 2005 18:59:59.999,
rec=c7619a00.4c3dff3f Sat, Dec 31 2005 19:00:00.297,
xmt=c76199ff.da759ab6 Sat, Dec 31 2005 18:59:59.853,
filtdelay= 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00,
filtoffset= 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00,
filtdisp= 0.00 0.26 0.50 0.75 0.99 1.26 1.52
1.77
ntpq> pe
remote refid st t when poll reach delay offset
jitter
==============================================================================
xGPS_ONCORE(0) .GPS. 0 l 3 16 377 0.000 -1000.0
0.004
LOCAL(0) LOCAL(0) 14 l 62 64 377 0.000 0.000
0.004
*dsl081-199-165. .GPS. 1 u 13 128 377 141.613 4.126
1.604
-sip.eicat.ca ox.eicat.ca 3 - 63 64 377 149.506 0.459
0.437
+underworld.drax .DCFa. 1 - 47 64 377 231.685 20.352
0.111
+elektra.ultra.n ntp0.usno.navy. 2 - 56 64 377 131.328 3.508
2.774
ntpq>
Did anyone else with an ONCORE clock see this behaviour? Does
it suggest a bug in the clock-driver code or something else?
Cheers.
--
+------------------------------------------------+---------------------+
| Carl Richard Friend (UNIX Sysadmin) | West Boylston |
| Minicomputer Collector / Enthusiast | Massachusetts, USA |
| mailto:crfriend at rcn.com +---------------------+
| http://users.rcn.com/crfriend/museum | ICBM: 42:22N 71:47W |
+------------------------------------------------+---------------------+
More information about the questions
mailing list