Hi, I run: ptp4l -i eth0 -m The prints looks OK (even after hours). Once I run phc2sys -r -a Or phc2sys -s eth0 -c CLOCK_REALTIME -w
After few seconds I get the print "clockcheck: clock jumped forward or running faster than expected!" and the system clock start to drift massively: ptp4l[255560.398]: master offset 676 s2 freq -4570 path delay 69049 ptp4l[255561.498]: master offset -2347 s2 freq -7390 path delay 69049 ptp4l[255562.598]: master offset 976 s2 freq -4771 path delay 68625 ptp4l[255563.698]: master offset 792 s2 freq -4663 path delay 68302 ptp4l[255564.798]: master offset -1660 s2 freq -6877 path delay 68328 ptp4l[255565.898]: master offset 986 s2 freq -4729 path delay 68328 ptp4l[255566.998]: master offset 1813 s2 freq -3606 path delay 68328 ptp4l[255568.098]: master offset -802 s2 freq -5677 path delay 68328 ptp4l[255569.198]: master offset -2512 s2 freq -7628 path delay 68328 ptp4l[255570.257]: master offset 1082 s2 freq -4787 path delay 68328 ptp4l[255571.257]: master offset -979 s2 freq -6524 path delay 68423 ptp4l[255572.257]: master offset 1430 s2 freq -4409 path delay 68023 ptp4l[255573.257]: master offset 1380 s2 freq -4030 path delay 68018 ptp4l[255574.257]: master offset -896 s2 freq -5892 path delay 68258 ptp4l[255575.257]: master offset -1701 s2 freq -6965 path delay 68156 ptp4l[255576.257]: master offset 160 s2 freq -5615 path delay 67869 ptp4l[255577.257]: master offset 1900 s2 freq -3827 path delay 67869 ptp4l[255578.257]: master offset -276 s2 freq -5433 path delay 68156 ptp4l[255579.258]: master offset -16570 s2 freq -21809 path delay 68352 ptp4l[255580.257]: master offset 15759 s2 freq +5549 path delay 68352 ptp4l[255581.257]: master offset 3349 s2 freq -2134 path delay 68352 ptp4l[255582.258]: master offset -37 s2 freq -4515 path delay 68352 ptp4l[255583.258]: master offset 599 s2 freq -3890 path delay 67887 ptp4l[255584.258]: master offset -1495 s2 freq -5804 path delay 67887 ptp4l[255585.258]: master offset -16125 s2 freq -20883 path delay 67887 ptp4l[255586.258]: master offset 13107 s2 freq +3512 path delay 67887 ptp4l[255587.258]: master offset 5316 s2 freq -347 path delay 68576 ptp4l[255588.257]: clockcheck: clock jumped forward or running faster than expected! ptp4l[255588.258]: master offset 70368744178878 s0 freq -347 path delay 68698 ptp4l[255588.258]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT ptp4l[255589.298]: master offset 70368744172220 s2 freq -10726 path delay 68803 ptp4l[255589.298]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED ptp4l[255590.398]: master offset 70368744177775 s2 freq +599999999 path delay 68571 ptp4l[255591.498]: master offset 70368144943071 s2 freq +599999999 path delay 69310 ptp4l[255592.598]: master offset 70367544898866 s2 freq +599999999 path delay 69537 ptp4l[255593.698]: master offset 70366777805460 s2 freq +599999999 path delay 167158974 ptp4l[255594.799]: master offset 70366112026779 s2 freq +599999999 path delay 232895611 ptp4l[255595.897]: master offset 70365512006329 s2 freq +599999999 path delay 232895611 ptp4l[255596.997]: master offset 70364912009291 s2 freq +599999999 path delay 232895611 ptp4l[255598.097]: master offset 70364316550321 s2 freq +599999999 path delay 228339469 ptp4l[255599.197]: master offset 70363716523526 s2 freq +599999999 path delay 228339469 ptp4l[255600.299]: master offset 70363146133821 s2 freq +599999999 path delay 198722273 ptp4l[255601.399]: master offset 70362614622829 s2 freq +599999999 path delay 130220724 ptp4l[255602.499]: master offset 70362014594252 s2 freq +599999999 path delay 130220724 ptp4l[255603.599]: master offset 70361463936355 s2 freq +599999999 path delay 80864615 ptp4l[255604.699]: master offset 70360821948535 s2 freq +599999999 path delay 122846594 ptp4l[255605.799]: master offset 70360185745813 s2 freq +599999999 path delay 159029525 ptp4l[255606.899]: master offset 70359643657491 s2 freq +599999999 path delay 101100329 ptp4l[255607.999]: master offset 70359043651445 s2 freq +599999999 path delay 101100329 ptp4l[255609.099]: master offset 70358385722044 s2 freq +599999999 path delay 159029525 ptp4l[255610.199]: master offset 70357785694140 s2 freq +599999999 path delay 159029525 ptp4l[255611.299]: master offset 70357185673221 s2 freq +599999999 path delay 159029525 ptp4l[255612.399]: master offset 70356585668163 s2 freq +599999999 path delay 159029525 ptp4l[255613.499]: master offset 70355985670433 s2 freq +599999999 path delay 159029525 ptp4l[255614.599]: master offset 70355385634734 s2 freq +599999999 path delay 159029525 ptp4l[255615.699]: master offset 70354785619993 s2 freq +599999999 path delay 159029525 What can I do to solve this problem? Thanks, Gil. ________________________________________ From: Richard Cochran <richardcoch...@gmail.com> Sent: Wednesday, November 11, 2015 11:52 AM To: Gil Graiber Cc: linuxptp-users@lists.sourceforge.net Subject: Re: [Linuxptp-users] Should Linux PTP syn the clock used by date between PCs? On Wed, Nov 11, 2015 at 07:15:50AM +0000, Gil Graiber wrote: > Please let me know what I am missing here. You need to run phc2sys as well. See section 22.5 of: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_PTP_Using_ptp4l.html Thanks, Richard ------------------------------------------------------------------------------ _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
