Hello,

I have frequent synchronization issue on a PTP ordinary clock which has Linux 
kernel 3.18.12 and LinuxPTP v1.6. It runs in slave mode with software 
timestamping.

To force the problem to occur every time, I change the system clock to be 
approximately 5 minutes ahead of PTP Grandmaster clock. In the following, the 
(enhanced) log messages show ptp4l correctly steps the system clock with the 
observed offset, then transitions into SERVO_LOCKED state, however the master 
offset as seen by ptp4l keeps increasing afterwards. The slew and PI reset 
operations seem not to be able to keep up.

Any help is appreciated.
Daniel

ptp4l[137.667]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[137.667]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[137.864]: port 1: new foreign master 00b0ae.fffe.02d104-1
ptp4l[141.864]: selected best master clock 00b0ae.fffe.02d104
ptp4l[141.864]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[143.090]: port 1: minimum delay request interval 2^-7
ptp4l[143.801]: master offset 292990930284 s0 freq      +0 path delay    255286
....................................
ptp4l[158.800]: master offset 292990192008 s0 freq      +0 path delay      2970
ptp4l[159.799]: master offset 292989435868 s1 freq  -93410 path delay    255430
ptp4l[159.800]: ***Before step*** system time = Thu Aug  4 18:59:45 2016 839875 
micros
ptp4l[159.800]: clockadj_step clkid=0 offset=-292989435868
ptp4l[159.800]: ***After step*** system time = Thu Aug  4 18:54:51 2016 850548 
micros
ptp4l[160.799]: master offset 292989436892 s2 freq +100000000 path delay    
255430          <<<=========
ptp4l[160.799]: clockadj_set_freq
ptp4l[160.800]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[160.945]: clockcheck: clock jumped forward or running faster than 
expected!
ptp4l[160.945]: pi_reset
....................................
ptp4l[161.700]: master offset 292989691148 s0 freq +100000000 path delay      
2778
ptp4l[161.700]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
ptp4l[161.792]: clockcheck: clock jumped forward or running faster than 
expected!
ptp4l[161.792]: pi_reset
....................................
ptp4l[162.600]: master offset 292989692174 s0 freq +100000000 path delay      
2904
ptp4l[162.650]: clockcheck: clock jumped forward or running faster than 
expected!
ptp4l[162.650]: pi_reset
....................................
ptp4l[163.500]: master offset 292989693962 s0 freq +100000000 path delay      
2748
ptp4l[163.586]: clockcheck: clock jumped forward or running faster than 
expected!
ptp4l[163.586]: pi_reset
....................................
ptp4l[164.400]: master offset 292989694906 s0 freq +100000000 path delay      
2888
ptp4l[164.431]: clockcheck: clock jumped forward or running faster than 
expected!
ptp4l[164.431]: pi_reset
....................................
ptp4l[165.300]: master offset -147127914636 s0 freq +100000000 path delay 
146705873134
ptp4l[165.382]: clockcheck: clock jumped forward or running faster than 
expected!
ptp4l[165.382]: pi_reset
....................................
ptp4l[166.200]: master offset -422042768 s0 freq +100000000 path delay      2870
ptp4l[166.231]: clockcheck: clock jumped forward or running faster than 
expected!
ptp4l[166.231]: pi_reset
....................................
ptp4l[167.100]: master offset -422041762 s0 freq +100000000 path delay      2980
ptp4l[167.180]: clockcheck: clock jumped forward or running faster than 
expected!
ptp4l[167.180]: pi_reset
....................................
ptp4l[167.999]: master offset -422040068 s0 freq +100000000 path delay      2886
ptp4l[168.031]: clockcheck: clock jumped forward or running faster than 
expected!
ptp4l[168.031]: pi_reset
....................................
ptp4l[168.899]: master offset -422039004 s0 freq +100000000 path delay      2910
ptp4l[168.966]: clockcheck: clock jumped forward or running faster than 
expected!
ptp4l[168.966]: pi_reset
....................................
ptp4l[169.799]: master offset -422037260 s0 freq +100000000 path delay      2770
ptp4l[170.001]: clockcheck: clock jumped forward or running faster than 
expected!
ptp4l[170.001]: pi_reset
ptp4l[170.699]: master offset -585402570 s0 freq +100000000 path delay  51353036
ptp4l[171.599]: master offset -746676648 s0 freq +100000000 path delay  69771338
ptp4l[172.499]: master offset -887764240 s0 freq +100000000 path delay  68002674
....................................

------------------------------------------------------------------------------
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to