hi Richard, Issue: Running ptp4l in BC mode. Have connected one NIC port to BC/GM and another NIC port to testing unit (TU). On resetting of the testing unit, temporarily observing ptp4l going into FAULTY state though it shouldn't be impacted due to reset of testing unit.
On debugged this issue further: By adding debugs to print mono_interval in clockcheck_sample, below is the understanding. In normal working case: Observing clockcheck_sample is getting called once in 120-128 milli seconds. ptp4l: [523771.617] mono 127658899 ptp4l: [523771.737] mono 120000322 On resetting testing Unit, whenever send sync failure is observed, clockcheck_sample is getting called after 200 milli seconds. ptp4l: [523772.664] timed out while polling for tx timestamp ptp4l: [523772.664] PID 6071 increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug ptp4l: [523772.664] port 2: send sync failed ptp4l: [523772.700] mono 210350673 ptp4l: [523772.700] clockcheck port 1: clock jumped backward or running slower than expected! ptp4l: [523772.700] port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT Since mono interval will be used to calculate min and max freq offset, clockcheck is reporting error and resetting servo. As I understand ptp4l is running in single thread and this seems to impact whenever send failure occurs. Please suggest. regards, Ramesh On Friday, January 7, 2022, 08:53:09 PM GMT+5:30, Richard Cochran <richardcoch...@gmail.com> wrote: On Fri, Jan 07, 2022 at 07:32:39AM +0000, ramesh t wrote: > ptp4l: [325744.430] clockcheck: clock jumped forward or running faster than > expected! > ptp4l: [325744.430] port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT See this? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Please suggest. I suggest reading the log messages to see the clearly identified source of the fault. _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
