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

[Elder C. <eld...@ti...>]

> 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 offset -37039670930503 s0 freq      -0 path delay
229600
>
> ptp4l[17805.578]: port 1 (enp3s0): new foreign master 0001c0.fffe.1a3e8e-1
> ptp4l[17809.579]: selected best master clock 0001c0.fffe.1a3e8e
> ptp4l[17809.579]: foreign master not using PTP timescale
> ptp4l[17809.579]: port 1 (enp3s0): LISTENING to UNCALIBRATED on RS_SLAVE
> ptp4l[17810.584]: master offset     159453 s0 freq +100000000 path delay
   216530
>

Where does that initial freq value come from?

Is it possible to force it to +0 like in the log of the first run above,
the one
that synchronizes?

If the latter is possible, but requires code change to be tested, where
should I look
at in the source code?