Just for the record... On Tue, Feb 24, 2015 at 02:54:37PM -0800, Gary E. Miller wrote: > > See if you get the same clock jump issue or not. > > Since my ptp4l is in linreg mode, it can not jump my system clock. > > So what should I look for? > > I just did that, looks ugly, but I really have no idea: > > # killall ptp4l phc2sys > ptp4l: no process found > phc2sys: no process found > # ptp4l -i eth0 -l 6 -m -f ptp.conf > ptp4l[52360.386]: selected /dev/ptp0 as PTP clock > ptp4l[52360.386]: port 1: INITIALIZING to LISTENING on INITIALIZE > ptp4l[52360.386]: port 0: INITIALIZING to LISTENING on INITIALIZE > ptp4l[52362.144]: port 1: new foreign master 003048.fffe.345fe2-1 > ptp4l[52366.144]: selected best master clock 003048.fffe.345fe2 > ptp4l[52366.144]: foreign master not using PTP timescale > ptp4l[52366.144]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE > ptp4l[52367.211]: master offset -99132 s0 freq +599999998 path delay > 46363
Here the huge initial frequency offset is left over from the previous run. When starting up, the ptp4l program reads out the existing offset and uses it as a starting point. > ptp4l[52368.211]: master offset -107849 s0 freq +599999998 path delay > 46363 > ptp4l[52369.211]: master offset -125869 s0 freq +599999998 path delay > 55328 > ptp4l[52370.211]: master offset -134962 s1 freq +599994160 path delay > 55306 > ptp4l[52371.211]: master offset -599870879 s2 freq +186802553 path delay > 55306 > ptp4l[52371.211]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED > ptp4l[52372.211]: master offset -786797418 s2 freq -149872567 path delay > 55306 > ptp4l[52373.211]: master offset -637009628 s2 freq -599999999 path delay > 58203 > ptp4l[52374.211]: master offset -37092094 s2 freq -37208915 path delay > 60342 > ptp4l[52375.211]: master offset 244012 s2 freq +177926 path delay > 58203 Here the program exits with a much more reasonable frequency offset. > Strangely a kill and restart looks reasonable: > > kong linuxptp # ptp4l -i eth0 -l 6 -m -f ptp.conf > ptp4l[52498.377]: selected /dev/ptp0 as PTP clock > ptp4l[52498.378]: port 1: INITIALIZING to LISTENING on INITIALIZE > ptp4l[52498.378]: port 0: INITIALIZING to LISTENING on INITIALIZE > ptp4l[52500.147]: port 1: new foreign master 003048.fffe.345fe2-1 > ptp4l[52504.147]: selected best master clock 003048.fffe.345fe2 > ptp4l[52504.147]: foreign master not using PTP timescale > ptp4l[52504.147]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE > ptp4l[52506.215]: master offset -125996 s0 freq +177925 path delay > 66149 > ptp4l[52507.215]: master offset -114049 s0 freq +177925 path delay > 46374 > ptp4l[52508.215]: master offset -126964 s0 freq +177925 path delay > 49315 > ptp4l[52509.215]: master offset -136826 s1 freq +177442 path delay > 52187 > ptp4l[52510.215]: master offset -188068 s2 freq -21513 path delay > 52187 > ptp4l[52510.215]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED > ptp4l[52511.216]: master offset -176435 s2 freq -97696 path delay > 52187 > ptp4l[52512.215]: master offset -89938 s2 freq -100192 path delay > 55059 > ptp4l[52513.216]: master offset 1079 s2 freq -9460 path delay > 54937 > ptp4l[52514.215]: master offset 1241 s2 freq -8949 path delay > 54937 ... > It is possible the PLL is going nuts on startup? No, it just starts playing with really bad cards. Thanks, Richard ------------------------------------------------------------------------------ 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
