Re: [Linuxptp-users] Bug-report for PTP4l

2022-06-29 Thread Miroslav Lichvar
On Tue, Jun 28, 2022 at 10:18:39AM -0400, Prottay Adhikari wrote: > Hi, > Thanks for the reply. As for your question ... > > What hardware does the VM emulate? > The details can be found here. > https://browser.geekbench.com/v4/cpu/compare/3910977?baseline=3910977 >

Re: [Linuxptp-users] Bug-report for PTP4l

2022-06-28 Thread Prottay Adhikari
Hi, Thanks for the tip. I tried rebooting my VM. Unfortunately, it didn't work. *Prottay M. AdhikariDistributed Embedded Controls Specialist @* Eaton Center of Excellence *Ph.D. *(Electrical Engineering, Rensselaer Polytechnic Institute), On Tue, Jun 28, 2022 at 9:53 AM Martin Pecka wrote: > H

Re: [Linuxptp-users] Bug-report for PTP4l

2022-06-28 Thread Prottay Adhikari
Hi, Thanks for the reply. As for your question ... What hardware does the VM emulate? The details can be found here. https://browser.geekbench.com/v4/cpu/compare/3910977?baseline=3910977 Maybe you could configure a different

Re: [Linuxptp-users] Bug-report for PTP4l

2022-06-28 Thread Martin Pecka
Hi, I've started getting into this issue too on one of my test computers (Jetson TX2 + Orbitty Carrier running Ubuntu 18.04). I usually "resolve" it by rebooting the computer. After a fresh reboot, software timestamping works. Does a reboot help in your case? Martin Hi, The command I am try

Re: [Linuxptp-users] Bug-report for PTP4l

2022-06-28 Thread Miroslav Lichvar
On Tue, Jun 28, 2022 at 09:24:18AM -0400, Prottay Adhikari wrote: > ptp4l[687827.790]: timed out while polling for tx timestamp > ptp4l[687827.790]: increasing tx_timestamp_timeout may correct this issue, > but it is likely caused by a driver bug > ptp4l[687827.790]: port 1 (eth0): send sync failed