[ntp:questions] Re: Calling ONCORE owners...

Richard B. Gilbert rgilbert88 at comcast.net
Sun Jan 1 18:43:50 UTC 2006


Carl R. Friend wrote:

>   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.
>
>  
>
I have an Oncore M12+T receiver.   I was not monitoring my system at the 
time. The clockstats file shows:
53735 86397.200 127.127.30.0 3345062397.000001000 2005 365 23 59 57 57 
rstat 8400 dop  0.0 nsat  6,5 traim 2 sigma 65535 neg-sawtooth  12 sat 
888700080000
53735 86398.197 127.127.30.0 3345062398.000000000 2005 365 23 59 58 58 
rstat 8400 dop  0.0 nsat  6,5 traim 2 sigma 65535 neg-sawtooth   2 sat 
888700080000
53735 86399.197 127.127.30.0 3345062399.000001000 2005 365 23 59 59 59 
rstat 8400 dop  0.0 nsat  6,5 traim 2 sigma 65535 neg-sawtooth  -8 sat 
888700080000
53735 86399.196 127.127.30.0 3345062400.000003000 2005 365 23 59 60  0 
rstat 8400 dop  0.0 nsat  6,5 traim 2 sigma 65535 neg-sawtooth  11 sat 
888700080000

In effect, it repeated 23:59:59.197 twice

This was followed by the new day:
sunblok_$ head $NTPSTATS/clockstats.20060101
53736 0.197 127.127.30.0 3345062399.999998977 2006 1  0  0  0 59 rstat 
8400 dop  0.0 nsat  6,5 traim 2 sigma 65535 neg-sawtooth   0 sat 
888700080000
53736 1.199 127.127.30.0 3345062401.000002000 2006 1  0  0  1  1 rstat 
8400 dop  0.0 nsat  6,5 traim 2 sigma 65535 neg-sawtooth -11 sat 
888700080000
53736 1.398 127.127.30.0 ONCORE[0]: Leap Sec Msg: 13 14 2006 1 1 14 2 0 0 0
53736 1.398 127.127.30.0 ONCORE[0]: Leap second (1) scheduled for 
1Feb2006 at 0:0:0
53736 1.398 127.127.30.0 Set peer.leap to LEAP_ADDSECOND
53736 2.197 127.127.30.0 3345062402.000000000 2006 1  0  0  2  2 rstat 
8400 dop  0.0 nsat  6,5 traim 2 sigma 65535 neg-sawtooth   8 sat 
888700080000

As you can see, it seems a little confused.   To say the least!!!!  I'm 
not certain whether the Oncore itself was confused or whether the driver 
was confused. 

It looks as if there is a lot of improvement needed in the handling of 
leap seconds!

The status, as of a minute or so ago, is:
sunblok_$ ntpq -crv
status=04c4 leap_none, sync_uhf_clock, 12 events, event_peer/strat_chg,
version="ntpd 4.2.0 at 1.1161-r Sat Jan 31 23:23:46 EST 2004 (9)",
processor="sun4u", system="SunOS/5.8", leap=00, stratum=1,
precision=-19, rootdelay=0.000, rootdispersion=0.656, peer=25724,
refid=GPS, reftime=c762a098.33183237  Sun, Jan  1 2006 13:40:24.199,
poll=4, clock=c762a0a3.f46fd7e5  Sun, Jan  1 2006 13:40:35.954, state=4,
offset=-0.002, frequency=5.040, jitter=0.002, stability=0.000




More information about the questions mailing list