On Mon, Jun 15, 2020 at 06:23:21PM +0300, Vladimir Oltean wrote: > ptp4l is too silent when receiving, for whatever reason, out of order > messages. If the reordering is persistent (which is either a broken > network, or a broken kernel), the behavior looks like a complete > synchronization stall, since the application is designed to never > attempt to recover from such a condition. > > At least save some people some debugging hours and print when the > application reaches this code path. Since it's a debugging tool, we > don't want to create false alarms when the occasional packet gets > reordered in a production system, but have this information readily > available when the program's log level is set to debug, instead of > having users fish for it with code instrumentation. > > Signed-off-by: Vladimir Oltean <olte...@gmail.com>
Applied. Thanks, Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
