Hi, I'm having the following setup:
NTP Server| | Switch -------> IMX6 2 | \-> IMX6 1 IMX6 1 aka master runs - ntpd - ptp4l -f /etc/linuxptp/ptp4l.conf -i eth0 -m - phc2sys -s CLOCK_REALTIME -c eth0 -w -m IMX6 2 aka slave runs - ptp4l -f /etc/linuxptp/ptp4l.conf -i eth0 -s -m - phc2sys -c CLOCK_REALTIME -s eth0 -w -m Both IMX systems have no RTC so the year after boot is in 1900. Usually the ptp synchronizes first and then ntp sets the current time. The problem is that after the "time jump" ptp does noch synchronize. If the ptp stack is started after ntpd set the time, then the time gets properly synchronized. Did I miss a config option or does ptp simply not support such a time jump? Another question: While fully synchronized I see this: | ptp4l[9839.908]: master offset -965 s2 freq +478 path delay 23865 | ptp4l[9840.908]: master offset -135 s2 freq +1018 path delay 23865 | ptp4l[9841.908]: master offset 658 s2 freq +1771 path delay 23865 | ptp4l[9842.913]: master offset 563 s2 freq +1873 path delay 23880 | ptp4l[9843.910]: master offset -289 s2 freq +1190 path delay 23929 | ptp4l[9844.913]: master offset -42 s2 freq +1350 path delay 23880 | ptp4l[9846.080]: master offset -541 s2 freq +839 path delay 23880 | ptp4l[9846.913]: clockcheck: clock jumped forward or running faster than expected! | ptp4l[9846.915]: master offset 403 s0 freq +839 path delay 23880 | ptp4l[9846.915]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT | ptp4l[9847.913]: master offset 374 s2 freq +1188 path delay 23880 | ptp4l[9847.913]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED | ptp4l[9848.910]: master offset 777 s2 freq +1965 path delay 23880 | ptp4l[9849.910]: master offset 183 s2 freq +1605 path delay 23880 | ptp4l[9850.910]: master offset -448 s2 freq +1028 path delay 23876 Could someone please explain what this means? Sebastian _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
