[ntp:questions] ntpd with PPS on NetBSD/i386

David Lord snews at lordynet.org
Mon Jun 18 15:04:00 UTC 2012


posted to port-i386 at netbsd.org and comp.protocols.time.ntp


ntpd with PPS on NetBSD/i386

Hi

I've had two pool servers as from late 2009 which until recently
were running NetBSD-5. I've attempted updates to NetBSD-6 and
find I can't get PPS support working.

I'm not sure if it's the PPS support in the kernel or the supplied
ntpd with NetBSD-6.

I've attempted to compile on NetBSD-6 from the ntpd sources that I
downloaded from ntp.org and the binaries from that compile don't
work correctly. Compiles from NetBSD-5 complete and install/work ok
on NetBSD-5.


Any help appreciated.



David

##########################

NetBSD-6
NetBSD 6.0_BETA2 (P4X2666_0.41) #0: Thu May 31 14:57:19 GMT 2012
cpu0 id as - VIA Samuel 2

Stock ntpd from NetBSD distribution:
ntpd 4.2.6p5-o Wed Feb  1 07:49:06 UTC 2012

Mon Jun 18 11:30:00 GMT 2012
      remote           refid      st t when poll reach   delay   offset 
  jitter
==============================================================================
*GPS_NMEA(2)     .GPSb.           0 l   47   64  377    0.000    5.131 
  6.620
  PPS(2)          .PPSb.           0 l    -   64    0    0.000    0.000 
   0.000
  pd6000e1.home.l 192.168.59.61    2 u    1   64  377    1.447    0.759 
   2.902
  p4x2400b.home.l 192.168.59.61    2 u   50   64  376    1.810    3.415 
   3.449
+pd6000e2.home.l 81.187.61.74     2 u   64  256  377    0.463   15.534 
  9.521
-ntp1.lordynet.o 81.187.61.74     2 u   82  256  377    0.612   19.160 
11.381
+ntp0.lordynet.o .MSFa.           1 u   74  256  377    0.755   22.472 
14.111
offset:               0.005131 s
frequency:            -32.484 ppm
poll adjust:          -30
watchdog timer:       47 s
ntp_gettime() returns code 5 (ERROR)
   time d3898fb9.1f0ee494  Mon, Jun 18 2012 11:30:01.121, (.121321306),
   maximum error 37397 us, estimated error 3253 us, TAI offset 34
ntp_adjtime() returns code 5 (ERROR)
   modes 0x0 (),
   offset 4896.043 us, frequency -32.484 ppm, interval 256 s,
   maximum error 37397 us, estimated error 3253 us,
   status 0x2207 (PLL,PPSFREQ,PPSTIME,PPSJITTER,NANO),
   time constant 6, precision 0.001 us, tolerance 496 ppm,
   pps frequency -34.647 ppm, stability 0.018 ppm, jitter 1174.656 us,
   intervals 3573, jitter exceeded 3702, stability exceeded 0, errors 13.

Mon Jun 18 12:18:00 GMT 2012
      remote           refid      st t when poll reach   delay   offset 
  jitter
==============================================================================
*GPS_NMEA(2)     .GPSb.           0 l   48   64  377    0.000  -16.407 
  9.765
  PPS(2)          .PPSb.           0 l    -   64    0    0.000    0.000 
   0.000
  pd6000e1.home.l 192.168.59.61    2 u   51   64  377    0.357    4.326 
   1.828
  p4x2400b.home.l 81.187.61.74     2 u   46   64  377    1.083    0.848 
   1.472
+pd6000e2.home.l 81.187.61.74     2 u    7  256  377    0.412   -7.226 
  5.939
-ntp1.lordynet.o 81.187.61.74     2 u   59  256  377    0.489    2.302 
  7.618
+ntp0.lordynet.o .MSFa.           1 u   35  256  377    0.888   -9.582 
  9.952
offset:               -0.016407 s
frequency:            -33.242 ppm
poll adjust:          -30
watchdog timer:       48 s
ntp_gettime() returns code 5 (ERROR)
   time d3899af9.9bca533c  Mon, Jun 18 2012 12:18:01.608, (.608556495),
   maximum error 51786 us, estimated error 2143 us, TAI offset 34
ntp_adjtime() returns code 5 (ERROR)
   modes 0x0 (),
   offset -15655.340 us, frequency -33.242 ppm, interval 256 s,
   maximum error 51786 us, estimated error 2143 us,
   status 0x2207 (PLL,PPSFREQ,PPSTIME,PPSJITTER,NANO),
   time constant 6, precision 0.001 us, tolerance 496 ppm,
   pps frequency -34.647 ppm, stability 0.018 ppm, jitter 1174.656 us,
   intervals 3573, jitter exceeded 3702, stability exceeded 0, errors 13.



Then backed out and reinstalled NetBSD-5
NetBSD 5.1_STABLE (ME6000G_0.46) #0: Mon May 21 21.28.31 GMT 2012
cpu0 id as - IDT/VIA 686-class 599MHz

ntpd compiled from downloaded source
4.2.6p5 at 1.2349-o Tue Dec 27 09:47:55 UTC 2011

with same ntp.conf as used above the PPS has kicked into action
within 12 minutes (crontab job at 6 minutes intervals logging
ntpd status).

Mon Jun 18 13:06:00 GMT 2012
      remote           refid      st t when poll reach   delay   offset 
  jitter
==============================================================================
*GPS_NMEA(2)     .GPSb.           0 l   25   64   77    0.000  -11.693 
10.042
oPPS(2)          .PPSb.           0 l   24   64   37    0.000   -0.148 
  0.819
-pd6000e1.home.l 81.187.61.74     2 u   30   64   76    0.112   -2.836 
  0.803
-p4x2400b.home.l 81.187.61.74     2 u   25   64   76    0.693   -4.144 
  1.484
+pd6000e2.home.l 81.187.61.74     2 u   70  256    3    0.464   -5.259 
  0.539
-ntp1.lordynet.o 81.187.61.74     2 u   78  256    3    0.353   -0.703 
  0.555
+ntp0.lordynet.o .MSFa.           1 u   70  256    3    0.675   -1.209 
  0.696
offset:               -0.000148 s
frequency:            -34.377 ppm
poll adjust:          -30
watchdog timer:       24 s
ntp_gettime() returns code 0 (OK)
   time d389a638.f43dcc90  Mon, Jun 18 2012 13:06:00.954, (.954068662),
   maximum error 451249 us, estimated error 34 us, TAI offset 34
ntp_adjtime() returns code 0 (OK)
   modes 0x0 (),
   offset -107.640 us, frequency -34.377 ppm, interval 128 s,
   maximum error 451249 us, estimated error 34 us,
   status 0x2107 (PLL,PPSFREQ,PPSTIME,PPSSIGNAL,NANO),
   time constant 6, precision 0.001 us, tolerance 496 ppm,
   pps frequency -34.377 ppm, stability 0.643 ppm, jitter 3.408 us,
   intervals 25, jitter exceeded 6, stability exceeded 0, errors 4.

Mon Jun 18 13:48:00 GMT 2012
      remote           refid      st t when poll reach   delay   offset 
  jitter
==============================================================================
*GPS_NMEA(2)     .GPSb.           0 l   49   64  377    0.000    0.418 
10.983
oPPS(2)          .PPSb.           0 l   48   64  377    0.000   -0.002 
  0.002
  pd6000e1.home.l 192.168.59.61    2 u   54   64  376    0.429   -1.719 
   0.528
  p4x2400b.home.l 192.168.59.61    2 u   36   64  376    1.277   -1.595 
   0.695
+pd6000e2.home.l 81.187.61.74     2 u  200  256  377    0.532   -3.534 
  0.618
  ntp1.lordynet.o 192.168.59.61    2 u  194  256  377    0.430    0.485 
   0.397
+ntp0.lordynet.o .MSFa.           1 u  202  256  377    0.856    0.430 
  0.465
offset:               -0.000002 s
frequency:            -34.402 ppm
poll adjust:          30
watchdog timer:       48 s
ntp_gettime() returns code 0 (OK)
   time d389b010.67e8142c  Mon, Jun 18 2012 13:48:00.405, (.405885798),
   maximum error 24931 us, estimated error 2 us, TAI offset 34
ntp_adjtime() returns code 0 (OK)
   modes 0x0 (),
   offset -1.243 us, frequency -34.402 ppm, interval 256 s,
   maximum error 24931 us, estimated error 2 us,
   status 0x2107 (PLL,PPSFREQ,PPSTIME,PPSSIGNAL,NANO),
   time constant 6, precision 0.001 us, tolerance 496 ppm,
   pps frequency -34.402 ppm, stability 0.037 ppm, jitter 1.467 us,
   intervals 36, jitter exceeded 12, stability exceeded 0, errors 4.



More information about the questions mailing list