Hi Richard,
thank you for the hints. I have loaded the same version of linuxptp on
all three devices and applied your configuration changes.
Now the situation has changed. The master is in sync with the
SW-timestamping slave and the HW-timestamping slave is 37 seconds behind.
Why is that?
Below the logs:
Master:
-------
ptp4l: [590123.733] selected /dev/ptp0 as PTP clock
ptp4l: [590123.741] driver changed our HWTSTAMP options
ptp4l: [590123.742] tx_type 1 not 1
ptp4l: [590123.742] rx_filter 1 not 12
ptp4l: [590123.743] port 1: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l: [590123.745] port 0: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l: [590123.747] port 1: link up
ptp4l: [590131.661] port 1: LISTENING to MASTER on
ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l: [590131.662] selected best master clock 00049f.fffe.03fa92
ptp4l: [590131.662] assuming the grand master role
Slave (HW ts):
--------------
ptp4l: [62558.294] selected /dev/ptp0 as PTP clock
ptp4l: [62558.298] driver changed our HWTSTAMP options
ptp4l: [62558.298] tx_type 1 not 1
ptp4l: [62558.299] rx_filter 1 not 12
ptp4l: [62558.299] port 1: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l: [62558.300] port 0: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l: [62558.301] port 1: link up
ptp4l: [62558.483] port 1: new foreign master 00049f.fffe.03fa92-1
phc2sys: [62558.795] phc offset -36 s2 freq +2008 delay 4666
phc2sys: [62559.795] phc offset -38 s2 freq +1995 delay 4667
phc2sys: [62560.796] phc offset 14 s2 freq +2036 delay 4708
phc2sys: [62561.797] phc offset 10 s2 freq +2036 delay 4709
ptp4l: [62562.484] selected best master clock 00049f.fffe.03fa92
ptp4l: [62562.485] port 1: LISTENING to UNCALIBRATED on RS_SLAVE
phc2sys: [62562.798] phc offset 6 s2 freq +2035 delay 4709
phc2sys: [62563.799] phc offset -33 s2 freq +1998 delay 4708
ptp4l: [62563.931] master offset -190 s0 freq +2024 path
delay 12850
phc2sys: [62564.800] phc offset -16 s2 freq +2005 delay 4666
ptp4l: [62564.931] master offset -135 s2 freq +2079 path
delay 12850
ptp4l: [62564.932] port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
phc2sys: [62565.801] phc offset 88 s2 freq +2104 delay 4709
Regards
Petr
On 18/07/17 20:09, Richard Cochran wrote:
On Tue, Jul 18, 2017 at 04:09:57PM +0200, Petr Kulhavy wrote:
1. GM using HW time stamping
Okay, so make sure the master has the correct UTC offset.
[global]
utc_offset 37
or
ptp4l --utc_offset=37
The HW-timestamping slave is also running:
/usr/sbin/phc2sys -s /dev/ptp0 -c CLOCK_REALTIME -S 1.0 -O 0
With '-O 0' you have set the UTC/TAI offset to zero by hand. That
explains the offset between your two slaves. Instead, use this:
phc2sys -a -r
Log of the SW-timestamping slave is:
ptp4l: [413741.946] running in a temporal vortex
The log of the HW-timestamping device is:
ptp4l: [252.634] running in a temporal vortex
These messages about "temporal vortex" mean that the GM is reporting a
UTC offset that is less than the hard coded default. Probably you are
running an older ptp4l version on the GM than on the slaves. I
recommend running the same version on all the nodes.
Thanks,
Richard
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
