On Mon, Feb 23, 2015 at 11:56:02PM -0800, Gary E. Miller wrote: > Miroslav Lichvar <mlich...@redhat.com> wrote: > > On Mon, Feb 23, 2015 at 06:48:51PM -0800, Gary E. Miller wrote: > > > ptp4l[365.571]: clockcheck: clock jumped forward or running > > > faster than expected! > > > > Looks like something else than ptp4l is touching the PHC. > > How can that be? I do "killall ptp4l phc2sys" in my test script.
> Oh, one other thing. Sometimes after running a timestamp hardware > test I can not revert to timestamp software and get a good time. > > After my last test I had a persistent 150mS offset from ptp4l that > would not go away. Killing and restarting ptp4l did not help. I > had to reboot to get back to good time. These sound like a driver bug to me. What kernel and NIC do you have? Perhaps Richard might have some suggestions on how to debug this. -- Miroslav Lichvar ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
