On Tue, Aug 13, 2013 at 09:36:25PM +0000, Vick, Matthew wrote: > > For the occasional "hiccup" on the RJ45 side, if the 82576 tries to > timestamp two outbound packets too quickly, it will fail to return the > second one (since the hardware is busy timestamping the first one). > > What options are you running with ptp4l? -P should help reduce the number > of failed timestamps on the RJ45 port.
I don't think changing ptp4l's options makes any difference. That program is single threaded, and it always waits for the time stamp after sending an event message. This behavior is quite on purpose, knowing that some of the hardware out there can only handle on at a time. On the linuxptp-users list, Alexander also recently reported frequent time stamp failures on peer delay request messages. It is beginning to look like the 82576 has a bug in this regard. Thoughts? Thanks, Richard ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
