On Wed, Dec 11, 2013 at 03:42:09PM -0600, Shawn Bohrer wrote: > I left the message in but let it continue. It appears to work fine > with software timestamps, or at least I don't see any relevant errors > and it is adjusting the clock. I haven't looked into the "port 1: > delay timeout" messages yet.
Those are harmless debug messages that say, "it is time to transmit another delay request." > My end goal though is to use hardware timestamps and that currently > does not work on the vlan interface simply because the SIOCSHWTSTAMP > ioctl fails. For now, if you know the real inteface, you can set the ioctl by hand using the hwstamp_ctl program. Then, just hack ptp4l to skip over the ioctl, and it might work for you. > I'm not sure how it is done, but should ptp4l recognize > that it is a vlan interface and perform ioctl and ethtool queries > against the actual device interface? I know the 'ip' tool associates > vlan807 with eth4 so that mapping can be detected somehow: I think it would be nicer if the kernel did this for us automatically, but I'll have to take this up on the netdev list. Thanks, Richard ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Linuxptp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-users
