On Wed, Aug 01, 2018 at 12:17:42PM +0800, l...@codeaurora.org wrote: > ptp4l[195.204]: master offset 2 s2 freq +2 path de[ > 195.207356] **********kernel adjfreq get ppb: fffffffe > lay 3746 > ptp4l[195.522]: port 1: delay timeout > ptp4l[195.523]: delay filtered 3752 raw 31363083 > ptp4l[196.204]: master offset -199005272 s2 freq -3124999 path d[ > 196.207369] **********kernel adjfreq get ppb: 2faf07 > elay 3752 > ptp4l[197.204]: master offset -196906469 s2 freq -3124999 path d[ > 197.207393] **********kernel adjfreq get ppb: 2faf07 > elay 3752
This does look like a HW/driver issue. The local PTP clock is suddenly behind by 199 milliseconds, so ptp4l speeds up the clock to catch up with the true time. Or the GM is skipping ahead. But I assume you have tried it with SW timestamping and it worked ok. -- Miroslav Lichvar ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
