Hello,
Thanks for your help! Actually it doesn't seem to totally not sync, if i
put the date on another day, it actually syncs somehow, but the time
difference is 37 seconds. and the strange thing is that these 37 seconds
look to be more or less constant (eg i can reboot and it will sync back ,
and the time difference will be again 37 seconds)
phc2sys is ran as follows:
/usr/local/sbin/phc2sys -f /etc/phc2sys.conf -a -rr
the phc2sys config is more or less empty (step_threshold is on 0.03)
this is the pmc output on the ubuntu (hwtimestamping) machine:
root@ubuntu:~# pmc -u -b 0 'GET TIME_STATUS_NP'
sending: GET TIME_STATUS_NP
000129.fffe.84b231-0 seq 0 RESPONSE MANAGEMENT TIME_STATUS_NP
master_offset 2863
ingress_time 1549877956534258265
cumulativeScaledRateOffset +0.000000000
scaledLastGmPhaseChange 0
gmTimeBaseIndicator 0
lastGmPhaseChange 0x0000'0000000000000000.0000
gmPresent true
gmIdentity 000129.fffe.84b22b
there are 4 identical machines here, one is master and the others are
slave. time sync between those works very well / reliable.
and this is the one on the embedded machine (software, no phc2sys):
root@zynq:~# pmc -u -b 0 'GET TIME_STATUS_NP'
sending: GET TIME_STATUS_NP
4aceb7.fffe.394574-0 seq 0 RESPONSE MANAGEMENT TIME_STATUS_NP
master_offset -36175
ingress_time 1549877958534455192
cumulativeScaledRateOffset +0.000000000
scaledLastGmPhaseChange 0
gmTimeBaseIndicator 0
lastGmPhaseChange 0x0000'0000000000000000.0000
gmPresent true
gmIdentity 000129.fffe.84b22b
so they are both syncing to the same GM.
we are actually trying to move away from ptpd2 on the embedded system so
there we have no prior linuxptp experience.
in the mean time i also upgraded linuxptp from 1.8 to 2.0 on the embedded
system, it made no difference.
Frank
On Sat, Feb 9, 2019 at 4:57 AM Richard Cochran <richardcoch...@gmail.com>
wrote:
> On Fri, Feb 08, 2019 at 08:22:31PM +0100, Frank Dekervel wrote:
> > What i observe is:
> >
> > - the computers with hardware timestamps do sync fine
> > - the embedded system claims to be in sync with the other computers
> (eg
> > when i do pmc -u -b 0 'GET TIME_STATUS_NP' the master_offset is less
> > than 100usec on the embedded system and on the other computers too)
> > - however, the clocks are totally not in sync (more than a minute
> apart
> > as reported by "date")
>
> Be careful here. The `date` command compares the systems clocks, but
> the ubuntu system clock is not necessarily synchronized with the HW
> clock in the MAC.
>
> > - phc2sys is running on the ubuntu trusty computers but not on the
> > embedded system.
>
> But with what arguments? Which PTP clock is the master in your setup?
>
> > My question is: what could be the cause of a low master_offset but still
> no
> > clocks in sync ?
>
> I guess that the ubuntu system time is simply independent of the
> ubuntu PHC time.
>
> > Also, we have setup monitoring to send alerts when time is not in sync,
> > based on the output of "GET TIME_STATUS_NP". is this the right output to
> > monitor ?
>
> Yes, or you can monitor CURRENT_DATA_SET.offsetFromMaster
>
> HTH,
> Richard
>
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
