> -----Original Message-----
> From: Frantisek Rysanek [mailto:frantisek.rysa...@post.cz]
> Sent: Thursday, December 07, 2017 8:28 AM
> To: linuxptp-devel@lists.sourceforge.net
> Subject: Re: [Linuxptp-devel] Despite the patch, "timed out while polling for
> tx
> timestamp" keeps happening
>
> => the Intel NIC hardware is possibly sensitive to "irrelevant"
> contents in the traffic. I can come up with the following candidate
> culprits/theories:
> - absence of the VLAN tag
> - correction values of 10-20 ms
> - other mcast traffic interfering
> - higher/different actual jitter in the messages?
>
> > Which device (and driver) are you using? (I can't see it in the history).
> >
> On the ptp4l client?
> The PC is a pre-production engineering sample panel PC by Arbor/TW,
> with Intel Skylake mobile, the NIC that I'm using is an i219LM
> integrated on the mothereboard (not sure if this has a MAC on chip
> within the PCH/south, or if it's a stand-alone NIC). Of the two Intel
> NIC chips, this one is more precise. The kernel is a fresh vanilla
> 4.13.12 and the e1000e driver came with it.
> I'm attaching a dump of dmesg and lspci. Ask for more if you want.
>
> Frank Rysanek
Do you know the packet rate for Tx packets? (How often is it requesting
timestamps)? There was a recent-ish problem I believe we fixed but it appears
to be in 4.13: 5012863b7347 ("e1000e: fix race condition around
skb_tstamp_tx()", 2017-06-06), but that definitely should be in the 4.13
kernel..
There should also be statistics you can check in ethtool stats on the device.
Could you try checking if tx_hwtstamp_timeouts is incrementing? Also whether
tx_hwtstamp_skipped?
Thanks,
Jake
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
