On Wed, Mar 04, 2015 at 12:16:48PM -0800, Gary E. Miller wrote: > Which still leaves me with slave PHC clocks that either go crazy or have > huge offsets... > > I have two live test beds now and I'mm getting a better feel for the failure > mechanisms. > > It almost feels like the sign of the offset is wrong on the I210. As > soon as ntpd/chronyd steers to it the time blows up. Positive, not > negative feedback.
Well, it works for me with i210 nicely. If you post your configuration files, command lines and program outputs of ptp4l, phc2sys, chronyd/ntpd for both master and slave systems, maybe we could better see what's happening. There is one test that might be worth trying. Add noselect option to all servers and refclocks in your chronyd/ntpd configuration to just monitor the offsets without actually synchronizing the system clock. If the SHM refclock is marked as falseticker, the problem probably is somewhere upstream from the slave chronyd/ntpd. If the problem shows up only when the noselect option is removed, well, I'm not sure what that could be :). -- 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
