frequency tolerance: 500

[Achim Gratz]

Udo van den Heuvel via devel writes:
> When simply rebooting?

Again, the normally the clock is either set from RTC and then ntpdate or
ntpd with that allowed to step it.

> #  ntpq -c kerninfo -pn
> associd=0 status=0028 leap_none, sync_unspec, 2 events, no_sys_peer,
> pll offset:            25.623
> pll frequency:         186.259
> maximum error:         0.10146
> estimated error:       0.00972
> kernel status:         pll nano
> pll time constant:     6
> precision:             1e-06
> frequency tolerance:   500
> pps frequency:         0
> pps stability:         0
> pps jitter:            0
> calibration interval   0
> calibration cycles:    0
> jitter exceeded:       0
> stability exceeded:    0
> calibration errors:    0
>      remote                                   refid      st t when poll
> reach   delay   offset   jitter
> =======================================================================================================
> xNMEA(0)                                 .GPS.            0 l    -   64    1   0.0000  48.1256   0.0000
> x192.168.10.98                           .GPS.            1 u   35   64    3   0.2999  27.4933   4.5941
>  fd00:c0a8:a00:1::1                      .GPS.            1 u    7   64    1   0.3935  55.0019   0.0000
>  2001:888:0:7::2                         193.67.79.202    2 u    5   64    1  14.9598  60.2632   0.0000
>  2001:888:0:7::22                        193.67.79.202    2 u   60   64    1  15.5002  23.9193   0.0000
>  193.67.79.202                           .STEP.          16 u    -  128    0   0.0000   0.0000   0.0002
>  193.79.237.14                           .STEP.          16 u    -  128    0   0.0000   0.0000   0.0002
>  185.31.230.94                           .STEP.          16 u    -  128    0   0.0000   0.0000   0.0002
>  134.221.205.12                          .STEP.          16 u    -  128    0   0.0000   0.0000   0.0002
>
>
> This behaviour is not normal.

Uh, that is reporting from an ntpd that has just started and hasn't
collected many statistics.  So the only way it can get a PLL frequency
of 186ppm will be if that value is stored in the drift file.  Do you
have one (usually found somewhere in /var/lib/ntp/), does it contain a
sensible value?

> is it software?
>
> rebooted again to 4.19.23 which shows different behaviour than 4.19.30
> and 32.

What are these version numbers, Linux kernel?  If so, this doesn't seem
to be a rasPi, what is it?  Also, just mumbling about "different
behaviour" without showing at least one difference isn#t really going to
get you much help.  So what does your ntp.conf look like, how is the GPS
connected, have you actually provided correct time1 (and perhaps time2
if you're using PPS) values for it?  Etc.pp.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds