| Re: [chrony-users] Re: Locking PPS refclock with NTP source |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Re: Locking PPS refclock with NTP source
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 30 Aug 2017 18:51:56 +0200
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com A33EA5F739
On Tue, Aug 29, 2017 at 04:58:14PM +0200, Thibaut BEYLER wrote:
> > #* PPS0 0 4 377 11 +4829ns[+6161ns]
> >> +/- 3021ns
> > PPS0 23 17 383 +0.001 0.052
> >> +5ns 5548ns
> I am using pps_ldisc, i tried pps-gpio but it was not better.
>
> I am using a custom serial cable (pin 1 of the serial cable is linked to
> the bnc ouput on the gps timeserver), same setup had given good results
> using an other software.
The chronyc output suggests the PPS input is very jittery. What
architecture is that? If it has GPIO I'd assume it's not just an
ordinary x86_64 computer. Also, what kernel version is it running? Is
the NOHZ config option enabled? Disabling it with nohz=off might help.
--
Miroslav Lichvar
--
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.