On 3/16/2020 9:33 AM, Pavan Chebbi wrote:
> I figured out that I was not adjusting the freq drift right. With that
> fix, I am able to see valid freq values. However, I now see 
> 
> ptp4l[206514.694]: clockcheck: clock jumped backward or running slower
> than expected!
> ptp4l[206514.694]: master offset -11793044594 s0 freq +31000000 path
> delay  69948126
> 

The most likely cause of this is either an NTP daemon modifying the
clock, or a driver bug.

Thanks,
Jake


_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to