[LinuxPPS] Why is my ATOM clock a falseticker?

[Paul Simons]

Alas, I have to admit that I have no idea what you are talking about.  Which event counter and what time?  And, speaking of time, does anyone know why my time is blank (--- --- -- ---- --:--:--)?

(Current status after two days)

# ntpq -c ass

ind assid status  conf reach auth condition  last_event cnt 

=========================================================== 

  1 41514  8015   yes    no  none    reject     restart  1 

  2 41515  9624   yes   yes  none  sys.peer   reachable  2root at mercury:~# ntpq -c ass

ind assid status  conf reach auth condition  last_event cnt 

=========================================================== 

  1 41514  8015   yes    no  none    reject     restart  1 

  2 41515  9624   yes   yes  none  sys.peer   reachable  2# ntpq -c rv
associd=0 status=0464 leap_none, sync_uhf_radio, 6 events, freq_mode,
version="ntpd 4.2.4p4 at 1.1520-o Wed Jan  7 18:06:29 UTC 2009 (1)",
processor="i686", system="Linux/2.6.26.simonet", leap=00, stratum=1,
precision=-20, rootdelay=0.000, rootdispersion=2.090, peer=41515,
refid=TRUE, reftime=cd323ecc.00258be7  --- --- -- ---- --:--:--, poll=6,
clock=cd323efc.aa99e5c3  --- --- -- ---- --:--:--, state=4,
offset=-0.371, frequency=-87.841, jitter=0.057, noise=0.059,
stability=0.002, tai=0

ntpq> rv 41514
associd=41514 status=8015 conf, sel_reject, 1 event, restart,
srcadr=PPS(1), srcport=123, dstadr=127.0.0.1, dstport=123, leap=11,
stratum=0, precision=-20, rootdelay=0.000, rootdispersion=0.000,
refid=PPS, reach=000, unreach=0, hmode=3, pmode=4, hpoll=4, ppoll=4,
flash=1600 peer_stratum, peer_dist, peer_unreach, keyid=0, ttl=0,
offset=0.000, delay=0.000, dispersion=16000.000, jitter=0.001,
reftime=00000000.00000000  --- --- -- ---- --:--:--,
org=00000000.00000000  --- --- -- ---- --:--:--,
rec=00000000.00000000  --- --- -- ---- --:--:--,
xmt=cd323f3b.de250882  --- --- -- ---- --:--:--,
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=   16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0
ntpq> rv 41515
associd=41515 status=9624 conf, reach, sel_sys.peer, 2 events, reachable,
srcadr=TRUETIME(0), srcport=123, dstadr=127.0.0.1, dstport=123, leap=00,
stratum=0, precision=-10, rootdelay=0.000, rootdispersion=0.000,
refid=TRUE, reach=377, unreach=0, hmode=3, pmode=4, hpoll=6, ppoll=10,
flash=00 ok, keyid=0, ttl=0, offset=-0.357, delay=0.000,
dispersion=0.952, jitter=0.735,
reftime=cd3240d3.0017651f  --- --- -- ---- --:--:--,
org=cd3240d3.0017651f  --- --- -- ---- --:--:--,
rec=cd3240d3.00259ae0  --- --- -- ---- --:--:--,
xmt=cd3240d2.de258205  --- --- -- ---- --:--:--,
filtdelay=     0.00    0.00    0.00    0.00    0.00    0.00    0.00    0.00,
filtoffset=   -0.36   -0.37   -0.34   -0.31   -0.41   -2.30   -0.40   -0.40,
filtdisp=      0.00    0.99    1.98    2.96    3.92    4.89    5.87    6.83
ntpq>

The Good News is that "watch -n1 cat /sys/class/pps/pps*/{clear,assert}" shows the pulses are still happening.

On Mon, 2 Feb 2009 05:36:20 Cirilo Bernardo wrote:
>The offset for the PPS is bizarre.  Wasn't there a kernel+NTPD NANO
>issue?  All my kernels are >1yr old and I haven't played with the
>kernel NANO timer option yet.
 >
>Just to make sure that PPS is not missing ticks, (re)start ntpd, check
>the event counter along with time,  and check the event counter and
>time again the next day.  Check that the number of events elapsed is
>consistent with the recorded times.

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ml.enneenne.com/pipermail/linuxpps/attachments/20090202/be6168c4/attachment.htm