I figured out that I was not adjusting the freq drift right. With that fix, I am able to see valid freq values. However, I now see
ptp4l[206514.694]: clockcheck: clock jumped backward or running slower than expected! ptp4l[206514.694]: master offset -11793044594 s0 freq +31000000 path delay 69948126 repeated many times over. I see similar errors reported in other threads. I will go through and check if any of the solution fixes for me. However, this is my ptp4l config. If there appears anything obviously wrong I'd be glad if pointed out. Thanks so much in advance. [global] # # Default Data Set # twoStepFlag 1 slaveOnly 0 priority1 128 priority2 128 domainNumber 0 #utc_offset 37 clockClass 248 clockAccuracy 0xFE offsetScaledLogVariance 0xFFFF free_running 0 freq_est_interval 1 dscp_event 0 dscp_general 0 dataset_comparison ieee1588 G.8275.defaultDS.localPriority 128 # # Port Data Set # logAnnounceInterval 1 logSyncInterval 0 logMinDelayReqInterval 0 logMinPdelayReqInterval 0 announceReceiptTimeout 3 syncReceiptTimeout 0 delayAsymmetry 0 fault_reset_interval 4 neighborPropDelayThresh 20000000 masterOnly 0 G.8275.portDS.localPriority 128 # # Run time options # assume_two_step 0 logging_level 6 path_trace_enabled 0 follow_up_info 0 hybrid_e2e 0 inhibit_multicast_service 0 net_sync_monitor 0 tc_spanning_tree 0 On Mon, Mar 16, 2020 at 5:15 PM Pavan Chebbi <penpa...@gmail.com> wrote: > Hi, > I am new here, please excuse any error in posting. Please inform if I am > doing something that is not correct by the forum standards, I'd be glad to > correct myself. > > I wanted to get help in an issue I am facing with ptp4l while using HW > timestamping. > > I see a strange issue in my setup where the clocks are perfectly > synchronizing when phc2sys with ptp4l is used, but ptp4l reports master > offset that always increments and has frequency maxed out at -31000000. The > path delay however is stable. > > The slave is able to sync with master's clock but I am worried about these > values. I am not finding a clue as to where could be the problem. Snippets > below. > > ptp4l output on the slave: > ptp4l[165701.384]: master offset -23587382 s2 freq -31000000 path delay 990 > ptp4l[165702.384]: master offset -23591840 s2 freq -31000000 path delay 990 > ptp4l[165703.384]: master offset -23596265 s2 freq -31000000 path delay 959 > ptp4l[165704.384]: master offset -23600618 s2 freq -31000000 path delay 853 > ptp4l[165705.384]: master offset -23605075 s2 freq -31000000 path delay 853 > ptp4l[165706.384]: master offset -23609640 s2 freq -31000000 path delay 959 > ptp4l[165707.384]: master offset -23614100 s2 freq -31000000 path delay 959 > phc2sys output on the slave: > phc2sys[165701.977]: CLOCK_REALTIME phc offset 82 s2 freq -19421 delay > 25707 > phc2sys[165702.978]: CLOCK_REALTIME phc offset -239 s2 freq -19717 delay > 25551 > phc2sys[165703.981]: CLOCK_REALTIME phc offset 82 s2 freq -19468 delay > 26697 > phc2sys[165704.983]: CLOCK_REALTIME phc offset 689 s2 freq -18837 delay > 23866 > phc2sys[165705.985]: CLOCK_REALTIME phc offset -844 s2 freq -20163 delay > 25785 > phc2sys[165706.987]: CLOCK_REALTIME phc offset -673 s2 freq -20245 delay > 26847 > phc2sys[165707.988]: CLOCK_REALTIME phc offset 441 s2 freq -19333 delay > 25704 > > I think if the values are entirely wrong, the clocks should not have > sync'ed correctly. > > Any pointers as to where to look for the issue will be highly appreciated. > > Commands I have used are below: > Master: (p5p1 is the interface) > ptp4l -i p5p1 -m > phc2sys -s CLOCK_REALTIME -c p5p1 -w -m > > Slave: (p2p1 is the interface) > ptp4l -i p2p1 -m -s > phc2sys -s p2p1 -c CLOCK_REALTIME -w -m > > Thanks in advance for any help. > > Regards, > Pavan > > -- Regards, Pavan
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
