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
<https://browser.geekbench.com/v4/cpu/compare/3910977?baseline=3910977>
Maybe you could configure a different one?
I was hoping to avoid this solution. If we have to opt for a different
configuration anyway, is there a configuration you suggest?
Otherwise, you might need to upgrade to a more recent kernel version.
We upgraded from 20.04 to 22.04, the issue persists.
What do you think?
*Prottay M. AdhikariDistributed Embedded Controls Specialist @* Eaton
Center of Excellence
*Ph.D. *(Electrical Engineering, Rensselaer Polytechnic Institute),
On Tue, Jun 28, 2022 at 9:54 AM Miroslav Lichvar <mli...@re...>
wrote:
> 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
> > ptp4l[687827.790]: port 1 (eth0): MASTER to FAULTY on FAULT_DETECTED
> > (FT_UNSPECIFIED)
>
> As the message above suggests, it's likely a driver bug. What hardware
> does the VM emulate? Maybe you could configure a different one?
> Otherwise, you might need to upgrade to a more recent kernel version.
> Issues in SW timestamping are rare.
> >
> > My system is an Ubuntu 20.04 VM hosted on MS Azure.
>
> --
> Miroslav Lichvar
>
>
|
