On Mon, Feb 10, 2020 at 12:56:24PM +0530, rakesh goyal wrote: > ptp4l_new[76369.348]: timed out while polling for tx timestamp > ptp4l_new[76369.348]: increasing tx_timestamp_timeout may correct this > issue, but it is likely caused by a driver bug
I just wanted to point out that 'one-step Sync' does not mean 'one-step DelayReq'. DelayReq still requires retrieving TX time from hardware. In one-step sync, there is no poll for a tx timestamp for the Sync message. However, what you pasted, and the code you changed, is for DelayReq. In fact, one-step vs. two-step sync shouldn't affect DelayReq at all. The bug you pasted is clearly a problem with the driver and/or hardware (hence the error message). There is no point in trying different hardware to compare logs. Instead, you need to figure out why you can't retrieve the timestamp for the DelayReq message from your network hardware. _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
