On Wed, May 26, 2021 at 02:05:01PM +0000, Amar Subramanyam wrote: > Hi Miroslav, > > I am afraid, the patches that was intended to fix the reported issue doesn't > do so. The issue that we reported was not due to timestamps from non-slave > port being compared in jbod mode. But due to mono_interval (CLOCK_MONOTIC > interval b/w two successive calls to clock_check_sample()) becoming high due > to the execution BMCA algorithm between two successive calls to > clock_check_sample() function. We believe that this is due to execution time > being higher, and solution is to increase the default value of > sanity_freq_limit accordingly.
The execution of the BMCA took 30 milliseconds? In that case the fix would be to make the minimum interval longer. Can you post a strace -tt log containing the last second leading to the fault? I suspect it's rather the PHC interval that's wrong. There might be an unexpected interaction with phc2sys. Can you reproduce the issue with no phc2sys running? -- Miroslav Lichvar _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
