emmericp
Failed to timestamp packet on transmission
Hi, The files I am using is l2-load-latency.lua, but it does not show timestamp of the packets, and it show one warning-----Failed to timestamp packet on transmission. By the way, the NIC i am using is Intel 82599es. Do you have an idea of how could I get timestamp of the packets ?
Hello, in our setup an Intel X540-AT2 shows the same issue. Intel XL710 is working. best regards. Thomas.
Can you please try to connect the two ports of the NIC directly and run the script libmoon/examples/hardware-timestamping.lua with two ports as arguments?
Please report the full output (note: it's expected that some tests that this script run fail, I'm not aware of any NIC that passes all tests)
Please find the output of running this script in the attached file. As I see, the script was hanging after some tests and I stopped it manually. Hope this helps to locate the problem. Thanks and best regards Thomas
looks like you are only using a 1 gbit/s link instead of 10 gbit/s link.
does this also happen if you are running at 10 gbit/s, e.g. with a direct connection between the two ports?
(it is possible that the timestamping gets confused by the link speed as it influences the timestamping clock on the NIC, but this used to work before we started relying on DPDK for PTP support)
Am 10.01.2017 um 22:30 schrieb ThomasDeiss [email protected]:
Please find the output of running this script in the attached file. As I see, the script was hanging after some tests and I stopped it manually. Hope this helps to locate the problem. Thanks and best regards Thomas
hw_timestamping.txt https://github.com/emmericp/MoonGen/files/697422/hw_timestamping.txt — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/emmericp/MoonGen/issues/159#issuecomment-271704007, or mute the thread https://github.com/notifications/unsubscribe-auth/AIhlAX111pRdS72GGJtgE-PxjPnNLnfOks5rQ_iNgaJpZM4K2M7R.
unfortunately it does not make a difference to connect both port directly. They are indicated now as 10G. I've attached a log. hw_timestamping_2017_01_11.txt
Weird, the fact that it hangs completely indicates that it's not even able to send out the packets at all.
Can you please run lshw -numeric and post the full output?