Re: [chrony-users] Chrony not taking SOCKET data from Application

Hi Miroslav,

I have enabled the refclocks logs where I see the PPS signal are available. And GPS UTC time comes very fast within a second.

Attaches is the refclocks logs. Can you please review once?

>Probably not. Is the CPU running at a constant frequency? Did you try
>disabling all power saving features? You could also try higher PPS
>rate (if the GPS can be configured for that) and switch to the
>pps-gpio-poll kernel module to avoid the interrupt latency/jitter.

CPU is running good and power saving features are not there. Not tried with higher PPS rate. Using pps-gpio-poll as kernel module, I see the CPU gets occupied waiting for the edge of clock right.

Through which parameter of chronyc output can we know the synchronization is in micro/nano/seconds?

I have made makestep to step if difference is more than 100ns continuously, with which I see the system time is many times 0 seconds slower than NTP time (from the output of tracking). Does this configuration effects anything.

Thanks & Regards

Sarveshwar.K

On Wed, Feb 1, 2023 at 2:41 PM Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:

On Tue, Jan 31, 2023 at 10:42:39PM +0530, sarveshwar k wrote:
> Should I have to add more directives to the PPS reference clock or GPS
> refclock to make Last Rx value be always 1second?

If you enable the refclocks log, do you see all PPS and SOCK samples,
or are some missing?

> Can we reduce the offset to less than 100ns with some configuration in
> chrony?

Probably not. Is the CPU running at a constant frequency? Did you try
disabling all power saving features? You could also try higher PPS
rate (if the GPS can be configured for that) and switch to the
pps-gpio-poll kernel module to avoid the interrupt latency/jitter.

--
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.