Re: [Linuxptp-users] Software timestamping delay - master offset drift

2023-05-16 Thread Elder Costa
> > > Is it possible to force it to +0 like in the log of the > > > first run above, the one that synchronizes? > > phc_ctl CLOCK_REALTIME freq 0 > Hello, Miroslav, thank you very much. BR. ___ Linuxptp-users mailing list

Re: [Linuxptp-users] Software timestamping delay - master offset drift

2023-05-16 Thread Miroslav Lichvar
On Tue, May 16, 2023 at 11:04:36AM -0300, Elder Costa wrote: > > > ptp4l[484.261]: port 1 (enp3s0): new foreign master 0001c0.fffe.1a3cda-1 > > > ptp4l[488.262]: selected best master clock 0001c0.fffe.1a3cda > > > ptp4l[488.262]: foreign master not using PTP timescale > > > ptp4l[488.262]: port 1

Re: [Linuxptp-users] Software timestamping delay - master offset drift

2023-05-16 Thread Elder Costa
> > ptp4l[484.261]: port 1 (enp3s0): new foreign master 0001c0.fffe.1a3cda-1 > > ptp4l[488.262]: selected best master clock 0001c0.fffe.1a3cda > > ptp4l[488.262]: foreign master not using PTP timescale > > ptp4l[488.262]: port 1 (enp3s0): LISTENING to UNCALIBRATED on RS_SLAVE > > ptp4l[490.263]:

Re: [Linuxptp-users] Software timestamping delay - master offset drift

2023-05-13 Thread Elder Costa
> ptp4l[484.261]: port 1 (enp3s0): new foreign master 0001c0.fffe.1a3cda-1 > ptp4l[488.262]: selected best master clock 0001c0.fffe.1a3cda > ptp4l[488.262]: foreign master not using PTP timescale > ptp4l[488.262]: port 1 (enp3s0): LISTENING to UNCALIBRATED on RS_SLAVE > ptp4l[490.263]: master

Re: [Linuxptp-users] Software timestamping delay - master offset drift

2023-05-12 Thread Elder Costa
Em qui., 11 de mai. de 2023 às 21:43, Richard Cochran < richardcoch...@gmail.com> escreveu: > Maybe you have ntpd or systemd timesync or chrony running on the > client and/or the server? > > IIRC Ubuntu enables systemd thing by default, and it is hard to get > rid of. I disabled clock sync by NTP

Re: [Linuxptp-users] Software timestamping delay - master offset drift

2023-05-11 Thread Richard Cochran
On Thu, May 11, 2023 at 01:01:54PM -0300, Elder Costa wrote: > The master offset increases, non monotonically but with a very definite > trend, whether with or without the step_threshold parameter. > What am I missing? Maybe you have ntpd or systemd timesync or chrony running on the client

[Linuxptp-users] Software timestamping delay - master offset drift

2023-05-11 Thread Elder Costa
I had already notice this while trying to solve the clock sync issue of the other thread. Test setup is two Fitlet PCs, connected point-to-point. The master offset increases, non monotonically but with a very definite trend, whether with or without the step_threshold parameter. $ uname