On 9/8/2022 7:14 AM, Brian Lilly wrote: > For reference, the output of phc2sys running for a good number of hours > with a 60 second report window: > > https://pastebin.com/YEra3LCK <https://pastebin.com/YEra3LCK> > > > > *Brian Lilly / *Senior Firmware Engineer > > Email: bri...@neuralynx.com > > > > *From:* Brian Lilly <bri...@neuralynx.com> > *Sent:* Tuesday, September 6, 2022 1:21 PM > *To:* linuxptp-users@lists.sourceforge.net > *Subject:* [Linuxptp-users] Help with what is undoubtedly a problem with > my configuration > > > > Some background: > > > > I’m building a Petalinux image (Xilinx’ Yocto project based build system > thing) that includes linuxPTP. I have it starting as a service, and > subsequently, I also have phc2sys running to synchronize the system > clock to the clock from eth0 and my PTP master. This seems to be > working, to some degree. > > > > Problem is that the behavior is erratic, to say the least. > >
What hardware? This looks a lot like bad driver or hardware causing the clock on the ethernet device to behave erratically. > > For example: > > phc2sys[46.726]: CLOCK_REALTIME phc offset -93776 s2 freq +32031 > delay 1020 > > phc2sys[47.727]: CLOCK_REALTIME phc offset -83999 s2 freq +32168 > delay 1020 > > phc2sys[48.727]: CLOCK_REALTIME phc offset -119501 s2 freq +27423 > delay 1020 > > phc2sys[49.727]: CLOCK_REALTIME phc offset -479032 s2 freq -13320 > delay 1020 > > phc2sys[50.727]: CLOCK_REALTIME phc offset -1923240 s2 freq -176973 > delay 1020 > > phc2sys[51.727]: CLOCK_REALTIME phc offset -3395674 s2 freq -358174 > delay 1020 > > phc2sys[52.727]: CLOCK_REALTIME phc offset -3394547 s2 freq -392006 > delay 1010 > > phc2sys[53.728]: CLOCK_REALTIME phc offset -2828314 s2 freq -363666 > delay 1010 > > phc2sys[54.728]: CLOCK_REALTIME phc offset -2187172 s2 freq -321424 > delay 1020 > > phc2sys[55.728]: CLOCK_REALTIME phc offset -1661911 s2 freq -285517 > delay 1020 > > > > Eventually failing with a timeout since it can’t synchronize the system > or PTP hardware clock. > > what does the timeout look like? > > The PTP daemon is just chugging along, in a temporal vortex: > > ptp4l[1037]: ptp4l[246.499]: master offset 29510 s2 freq +64760 > path delay 265538 > > ptp4l[1037]: ptp4l[247.499]: master offset -20951 s2 freq +23152 > path delay 265538 > > ptp4l[1037]: ptp4l[248.499]: master offset -23629 s2 freq +14188 > path delay 265538 > > ptp4l[1037]: ptp4l[249.499]: master offset -40569 s2 freq -9840 > path delay 275390 > > ptp4l[1037]: ptp4l[250.499]: master offset -64721 s2 freq -46163 > path delay 275390 > > ptp4l[1037]: ptp4l[251.500]: master offset 90752 s2 freq +89894 > path delay 275390 > > ptp4l[1037]: ptp4l[252.499]: master offset 10070 s2 freq +36437 > path delay 275390 > > ptp4l[1037]: ptp4l[253.499]: master offset -65171 s2 freq -35783 > path delay 275390 > > ptp4l[1037]: ptp4l[254.499]: master offset 12986 s2 freq +22823 > path delay 275390 > > ptp4l[1037]: ptp4l[255.499]: master offset -40304 s2 freq -26571 > path delay 269316 > Is this using hardware timestamping? your frequency shifts are fairly high and erratic, and the measured offset is bouncing between -50usec and +50usec. The path delay is also really high.. 270 microseconds?? What sort of links do you have between your system and the server? Thanks, Jake _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
