*Does it work if you enable SW timestamping on the client?* I'm pasting the output below with HW timestamping at master and SW timestamping on client:
*ptp4l[641.740]: port 1: INITIALIZING to LISTENING on INIT_COMPLETEptp4l[641.740]: port 0: INITIALIZING to LISTENING on INIT_COMPLETEptp4l[645.780]: selected local clock b49691.fffe.a72050 as best masterptp4l[646.596]: port 1: new foreign master 000a35.fffe.000002-1ptp4l[648.596]: selected best master clock 000a35.fffe.000002ptp4l[648.596]: port 1: LISTENING to UNCALIBRATED on RS_SLAVEptp4l[649.721]: rms 36994812072 max 36994830538 freq -1000000 +/- 0 delay 21137 +/- 1465 ptp4l[650.722]: rms 36994771193 max 36994793561 freq -1000000 +/- 0 delay 22453 +/- 276 ptp4l[651.722]: rms 36994737242 max 36994749517 freq -1000000 +/- 0 delay 21996 +/- 680 ptp4l[652.722]: rms 36994709493 max 36994747491 freq -1000000 +/- 0 delay 21561 +/- 507 ptp4l[653.723]: rms 36994672571 max 36994686986 freq -1000000 +/- 0 delay 21531 +/- 761 ptp4l[654.723]: rms 36994644178 max 36994694356 freq -1000000 +/- 0 delay 22666 +/- 223 ptp4l[655.723]: rms 36994602115 max 36994617235 freq -1000000 +/- 0 delay 20980 +/- 873 ptp4l[656.724]: rms 36994572174 max 36994588866 freq -1000000 +/- 0 delay 22051 +/- 959 ptp4l[657.724]: rms 36994536525 max 36994551653 freq -1000000 +/- 0 delay 23524 +/- 300 ptp4l[658.724]: rms 36994503810 max 36994522571 freq -1000000 +/- 0 delay 22821 +/- 921 ptp4l[659.725]: rms 36994470556 max 36994531559 freq -1000000 +/- 0 delay 21131 +/- 2000 ptp4l[660.725]: rms 36994442536 max 36994473073 freq -1000000 +/- 0 delay 20562 +/- 964 ptp4l[661.726]: rms 36994401104 max 36994416693 freq -1000000 +/- 0 delay 22141 +/- 972 ptp4l[662.726]: rms 36994394078 max 36994606592 freq -1000000 +/- 0 delay 22251 +/- 227 ptp4l[663.726]: rms 36994335309 max 36994354631 freq -1000000 +/- 0 delay 22678 +/- 310 ptp4l[664.727]: rms 36994297566 max 36994315433 freq -1000000 +/- 0 delay 24249 +/- 610 ptp4l[665.727]: rms 36994264080 max 36994280858 freq -1000000 +/- 0 delay 24312 +/- 391 ptp4l[666.727]: rms 36994231842 max 36994246342 freq -1000000 +/- 0 delay 23605 +/- 109 * *What NIC, kernel, and linuxptp version is it using?* NIC: The client NIC is Intel XXV710 Kernel: 5.4.0-132-generic linuxptp version: 2.0 We are running the master on an FPGA card with PCIe interface. The timestamping logic is implemented in FPGA and driver and ptp4l are running on x86. On Mon, Jan 23, 2023 at 2:03 PM Miroslav Lichvar <mlich...@redhat.com> wrote: > On Mon, Jan 23, 2023 at 11:54:25AM +0530, Aditya Venu wrote: > > Any suggestions to the above issue please?! > > I don't see anything wrong in the phc2ctl output, but your ptp4l > output shows frequency stuck at -1, which makes no sense to me. > Does it work if you enable SW timestamping on client? > What NIC, kernel, and linuxptp version is it using? > > -- > Miroslav Lichvar > > -- Disclaimer:- This footer text is to convey that this email is sent by one of the users of IITH. So, do not mark it as SPAM.
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
