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 <pecka...@fel.cvut.cz> wrote: > 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 trying to run is > > *sudo ptp4l -i eth0 -m -S* > > > > The response I am seeing is: > > port 1 (eth0): send sync failed > > ptp4l[687780.178]: port 1 (eth0): MASTER to FAULTY on FAULT_DETECTED > > (FT_UNSPECIFIED) > > ptp4l[687796.179]: port 1 (eth0): FAULTY to LISTENING on INIT_COMPLETE > > ptp4l[687803.557]: port 1 (eth0): LISTENING to MASTER on > > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > > ptp4l[687803.557]: port 1 (eth0): assuming the grand master role > > ptp4l[687804.567]: timed out while polling for tx timestamp > > ptp4l[687804.568]: increasing tx_timestamp_timeout may correct this > issue, > > but it is likely caused by a driver bug > > ptp4l[687804.568]: port 1 (eth0): send sync failed > > ptp4l[687804.568]: port 1 (eth0): MASTER to FAULTY on FAULT_DETECTED > > (FT_UNSPECIFIED) > > ptp4l[687820.568]: port 1 (eth0): FAULTY to LISTENING on INIT_COMPLETE > > ptp4l[687826.779]: port 1 (eth0): LISTENING to MASTER on > > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > > ptp4l[687826.780]: port 1 (eth0): assuming the grand master role > > 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 > > ptp4l[687827.790]: port 1 (eth0): MASTER to FAULTY on FAULT_DETECTED > > (FT_UNSPECIFIED) > > > > My system is an Ubuntu 20.04 VM hosted on MS Azure. > > > > If I disable the -S flag and run the ptp4l on HW mode for the other > > interface of my system, it works fine. > > *sudo ptp4l -i enP48399s1 -m* > > > > This interface does not support the -S flag. So, I am trying the -S flag > on > > the other existing interface eth0. Do you have any suggestions on how to > > make the SW PTP run on the eth0 interface? > >
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
