On Mon, Feb 07, 2022 at 10:47:51AM +0000, ramesh t wrote: > Did few more iterations of testing (ptp4l in BC mode) by resetting TestUnit. > Still observing "send sync error" with txtimeout of 100ms. > > Question: > 1) ptp4l is running in BC mode providing clock to other connected TestUnits > and syncing clock from another BC/GM. > But in the below case, it would be blocked for almost 100ms (1/10 sec) > Wouldn't this impact ptp packets to testunit or handling ptp packets from > BC/GM?
Yes, it might if the long timeout is, in fact, needed. If you want to run logSyncInterval at 62.5 milliseconds, then you will need to design your system to handle that high rate. This might entail a different choice of MAC. > Feb 7 09:35:20 ptp4l: [610991.536] port 2: send sync failed > Feb 7 09:35:20 ptp4l: [610991.536] port 2: MASTER to FAULTY on > FAULT_DETECTED (FT_UNSPECIFIED) > Feb 7 09:35:20 ptp4l: [610991.557] port 2: link down > Feb 7 09:35:20 ptp4l: [610991.557] port 2: received link status notification > DOWN Why do you keep ignoring this message? Richard _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
