|Re: [chrony-users] kernel PPS troubleshooting|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
On Tue, Dec 10, 2013 at 08:29:25PM -0500, Battocchi, Scott L. wrote:
> I've attached the tracking, measurements, refclocks, and sources logs trimmed to start at the 2.35 hour mark (to coincide with the graph colored by sync source in my previous mail). I also moved the rolling header line for each log to the start of these trimmed ones and removed any subsequent headers from the remainder of the file. They each run about 16 minutes and through multiple sync source selections. I did not include any logs from the first two minutes where sync=1 and dist actually changed since that seemed to be a startup artifact and not related to the rest of the long run issues.
It seems the dropping of the PPS source is caused by SHM source having
too small configured delay. The long-term stability of the SHM source
is worse than the short-term jitter, so the measured dispersion (in
one polling interval) of the SHM source is sometimes smaller than the
current offset, which means it doesn't overlap with the PPS source in
the source selection algorithm and no source is selected with the "no
When no source is selected, the PPS samples are ignored. If the SHM
source doesn't move to the acceptable range to overlap with the PPS
source in 8 polling intervals, the PPS source is marked as unreachable
and the SHM source is selected as the only available source.
The configured delay is included in the interval used in the source
selection algorithm, so increasing the value from 0.01 to 0.4 or
larger should fix the problem.
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.