Menu
▾
▴
linuxptp-users — Open discussion on using the linuxptp software.
You can subscribe to this list here.
| 2012 |
Jan
|
Feb
(10) |
Mar
(47) |
Apr
|
May
(26) |
Jun
(10) |
Jul
(4) |
Aug
(2) |
Sep
(2) |
Oct
(20) |
Nov
(14) |
Dec
(8) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
(6) |
Feb
(18) |
Mar
(27) |
Apr
(57) |
May
(32) |
Jun
(21) |
Jul
(79) |
Aug
(108) |
Sep
(13) |
Oct
(73) |
Nov
(51) |
Dec
(24) |
| 2014 |
Jan
(24) |
Feb
(41) |
Mar
(39) |
Apr
(5) |
May
(6) |
Jun
(2) |
Jul
(5) |
Aug
(15) |
Sep
(7) |
Oct
(6) |
Nov
|
Dec
(7) |
| 2015 |
Jan
(27) |
Feb
(18) |
Mar
(37) |
Apr
(8) |
May
(13) |
Jun
(44) |
Jul
(4) |
Aug
(50) |
Sep
(35) |
Oct
(6) |
Nov
(24) |
Dec
(19) |
| 2016 |
Jan
(30) |
Feb
(30) |
Mar
(23) |
Apr
(4) |
May
(12) |
Jun
(19) |
Jul
(26) |
Aug
(13) |
Sep
|
Oct
(23) |
Nov
(37) |
Dec
(15) |
| 2017 |
Jan
(33) |
Feb
(19) |
Mar
(20) |
Apr
(43) |
May
(39) |
Jun
(23) |
Jul
(20) |
Aug
(27) |
Sep
(10) |
Oct
(15) |
Nov
|
Dec
(24) |
| 2018 |
Jan
(3) |
Feb
(10) |
Mar
(34) |
Apr
(34) |
May
(28) |
Jun
(50) |
Jul
(27) |
Aug
(75) |
Sep
(21) |
Oct
(42) |
Nov
(25) |
Dec
(31) |
| 2019 |
Jan
(39) |
Feb
(28) |
Mar
(19) |
Apr
(7) |
May
(30) |
Jun
(22) |
Jul
(54) |
Aug
(36) |
Sep
(19) |
Oct
(33) |
Nov
(36) |
Dec
(32) |
| 2020 |
Jan
(29) |
Feb
(38) |
Mar
(29) |
Apr
(30) |
May
(39) |
Jun
(45) |
Jul
(31) |
Aug
(52) |
Sep
(40) |
Oct
(8) |
Nov
(48) |
Dec
(30) |
| 2021 |
Jan
(35) |
Feb
(32) |
Mar
(23) |
Apr
(55) |
May
(43) |
Jun
(63) |
Jul
(17) |
Aug
(24) |
Sep
(9) |
Oct
(31) |
Nov
(67) |
Dec
(55) |
| 2022 |
Jan
(31) |
Feb
(48) |
Mar
(76) |
Apr
(18) |
May
(13) |
Jun
(46) |
Jul
(75) |
Aug
(54) |
Sep
(59) |
Oct
(65) |
Nov
(44) |
Dec
(7) |
| 2023 |
Jan
(38) |
Feb
(32) |
Mar
(35) |
Apr
(23) |
May
(46) |
Jun
(53) |
Jul
(18) |
Aug
(10) |
Sep
(24) |
Oct
(15) |
Nov
(40) |
Dec
(6) |
|
From: Richard C. <ric...@gm...> - 2023-12-07 05:00:48
|
Dear LinuxPTP Users, New posts to this list has been disabled. If you want to continue to participate on the mailing lists, please subscribe to the new list at the Network Time Foundation. https://lists.nwtime.org/sympa/info/linuxptp-users Thanks, Richard |
|
From: gntech h. <gt...@gm...> - 2023-12-06 22:19:52
|
Any ideas as to why the patch previously posted was necessary to resolve the incorrect source IP address in multicast packets? Is this more appropriate for the development list? I posted here based on https://lists.nwtime.org/sympa/info/linuxptp-users. Thank you, gthweng On Mon, Dec 4, 2023 at 3:08 PM geontech hweng <gt...@gm...> wrote: > Hi everyone, > > I am standing up PTP between an Ubuntu 20.04 system (server) and the 1GbE > PS interface of an AMD Ultrascale+ MPSoC board (client). The client has > PTP enabled as part of the Petalinux build v3.1.1. On the Ubuntu host, > v3.1.1 was built from source and installed because v1.9.2 that is packaged > for 20.04 has published vulnerabilities. Tests were performed with the > systems connected using a small desktop switch and connected directly. In > both cases, the interfaces are configured for static IP addresses and the > interfaces of both systems have multicast enabled. The client never prints > anything beyond the following. > > ```bash > sudo ptp4l -i eth0 --slaveOnly=1 -m --tx_timestamp_timeout=10 > Password: > ptp4l[6063.829]: selected /dev/ptp0 as PTP clock > ptp4l[6063.830]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE > ptp4l[6063.830]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE > ptp4l[6066.310]: port 1: new foreign master f4939f.fffe.f45b6d-1 > ptp4l[6070.310]: selected best master clock f4939f.fffe.f45b6d > ``` > The command used on the Ubuntu server is 'sudo ptp4l -i eno1 > --masterOnly=1 -m --logSyncInterval=-3 --tx_timestamp_timeout=10" > > Using wireshark and tcpdump, we have ascertained that the source IP > address for the multicast packets from the server contains the IP address > for another interface of the Ubuntu system. The source IP address is > incorrect. During the investigation, we discovered a post on this list is > 2017 that described the same issue and included a patch that fixed the > issue. The post is titled "Wrong Interface" and was posted on 017-06-22 > 20:59:12. The links to the original message and patch are below. > > https://sourceforge.net/p/linuxptp/mailman/message/35907900/ > > https://sourceforge.net/p/linuxptp/mailman/attachment/CAP6mCQSva38taSYXvXZaW2JoQ2YzZxfk3scM8QfYMxDFjqg68g%40mail.gmail.com/1/ > > Application of the changes in the patch corrected the issue for v3.1.1 on > the Ubuntu system. The client now converges to sub-100ns rms offsets with > HWTS enabled on both systems. A comparison of udp.c for v3.1.1 and v4.1 > indicates that nothing was changed to address this behavior in the most > recent release. Do you consider this an issue? If yes, will it be > corrected? If not, how do you recommend that users mitigate this issue? > > Thank you! > > gthweng > > |
|
From: Miroslav L. <mli...@re...> - 2023-12-06 09:52:30
|
On Wed, Dec 06, 2023 at 08:19:49AM +0000, Erling Rennemo Jellum wrote: > We are in the situation where we want to synchronize multiple devices where some only support the E2E delay mechanism and others only support the P2P delay mechanism (the gPTP profile specifically). Ideally, we would just use a single network interface on the grandmaster. See below for a Figure illustrating a possible topology. It would mean that the GM should exchange Peer Delay messages with the switch (which is a Transparent Clock), while also replying to Delay Request messages from the E2E slave, and sending out Sync+Follow Up to both the E2E and the P2P slave. > > Has anyone looked into this before? I guess it would be possible with two isolated networks and two instances of linuxPTP operating on two different network interfaces, but can it work on a single network? >From the PTP point of view it could work with two different PTP domain numbers. The GM can run multiple ptp4l instances. They can even share the same PHC, no need for vclocks. But practically I think it will depend on the switch whether it can be configured for such operation. -- Miroslav Lichvar |
|
From: Erling R. J. <erl...@se...> - 2023-12-06 08:54:08
|
Hi all. We are in the situation where we want to synchronize multiple devices where some only support the E2E delay mechanism and others only support the P2P delay mechanism (the gPTP profile specifically). Ideally, we would just use a single network interface on the grandmaster. See below for a Figure illustrating a possible topology. It would mean that the GM should exchange Peer Delay messages with the switch (which is a Transparent Clock), while also replying to Delay Request messages from the E2E slave, and sending out Sync+Follow Up to both the E2E and the P2P slave. Has anyone looked into this before? I guess it would be possible with two isolated networks and two instances of linuxPTP operating on two different network interfaces, but can it work on a single network? Thanks for any suggestions. |
|
From: geontech h. <gt...@gm...> - 2023-12-04 22:13:36
|
Hi everyone, I am standing up PTP between an Ubuntu 20.04 system (server) and the 1GbE PS interface of an AMD Ultrascale+ MPSoC board (client). The client has PTP enabled as part of the Petalinux build v3.1.1. On the Ubuntu host, v3.1.1 was built from source and installed because v1.9.2 that is packaged for 20.04 has published vulnerabilities. Tests were performed with the systems connected using a small desktop switch and connected directly. In both cases, the interfaces are configured for static IP addresses and the interfaces of both systems have multicast enabled. The client never prints anything beyond the following. ```bash sudo ptp4l -i eth0 --slaveOnly=1 -m --tx_timestamp_timeout=10 Password: ptp4l[6063.829]: selected /dev/ptp0 as PTP clock ptp4l[6063.830]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[6063.830]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[6066.310]: port 1: new foreign master f4939f.fffe.f45b6d-1 ptp4l[6070.310]: selected best master clock f4939f.fffe.f45b6d ``` The command used on the Ubuntu server is 'sudo ptp4l -i eno1 --masterOnly=1 -m --logSyncInterval=-3 --tx_timestamp_timeout=10" Using wireshark and tcpdump, we have ascertained that the source IP address for the multicast packets from the server contains the IP address for another interface of the Ubuntu system. The source IP address is incorrect. During the investigation, we discovered a post on this list is 2017 that described the same issue and included a patch that fixed the issue. The post is titled "Wrong Interface" and was posted on 017-06-22 20:59:12. The links to the original message and patch are below. https://sourceforge.net/p/linuxptp/mailman/message/35907900/ https://sourceforge.net/p/linuxptp/mailman/attachment/CAP6mCQSva38taSYXvXZaW2JoQ2YzZxfk3scM8QfYMxDFjqg68g%40mail.gmail.com/1/ Application of the changes in the patch corrected the issue for v3.1.1 on the Ubuntu system. The client now converges to sub-100ns rms offsets with HWTS enabled on both systems. A comparison of udp.c for v3.1.1 and v4.1 indicates that nothing was changed to address this behavior in the most recent release. Do you consider this an issue? If yes, will it be corrected? If not, how do you recommend that users mitigate this issue? Thank you! gthweng |
|
From: geontech h. <gt...@gm...> - 2023-12-04 21:49:53
|
Hi everyone, I am standing up PTP between an Ubuntu 20.04 system (server) and the 1GbE PS interface of an AMD Ultrascale+ MPSoC board (client). The client has PTP enabled as part of the Petalinux build v3.1.1. On the Ubuntu host, v3.1.1 was built from source and installed because v1.9.2 that is packaged for 20.04 has published vulnerabilities. Tests were performed with the systems connected using a small desktop switch and connected directly. In both cases, the interfaces are configured for static IP addresses and the interfaces of both systems have multicast enabled. The client never prints anything beyond the following. ```bash sudo ptp4l -i eth0 --slaveOnly=1 -m --tx_timestamp_timeout=10 Password: ptp4l[6063.829]: selected /dev/ptp0 as PTP clock ptp4l[6063.830]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[6063.830]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[6066.310]: port 1: new foreign master f4939f.fffe.f45b6d-1 ptp4l[6070.310]: selected best master clock f4939f.fffe.f45b6d ``` The command used on the Ubuntu server is 'sudo ptp4l -i eno1 --masterOnly=1 -m --logSyncInterval=-3 --tx_timestamp_timeout=10" Using wireshark and tcpdump, we have ascertained that the source IP address for the multicast packets from the server contains the IP address for another interface of the Ubuntu system. The source IP address is incorrect. During the investigation, we discovered a post on this list is 2017 that described the same issue and included a patch that fixed the issue. The post is titled "Wrong Interface" and was posted on 017-06-22 20:59:12. The links to the original message and patch are below. https://sourceforge.net/p/linuxptp/mailman/message/35907900/ https://sourceforge.net/p/linuxptp/mailman/attachment/CAP6mCQSva38taSYXvXZaW2JoQ2YzZxfk3scM8QfYMxDFjqg68g%40mail.gmail.com/1/ Application of the changes in the patch corrected the issue for v3.1.1 on the Ubuntu system. The client now converges to sub-100ns rms offsets with HWTS enabled on both systems. A comparison of udp.c for v3.1.1 and v4.1 indicates that nothing was changed to address this behavior in the most recent release. Do you consider this an issue? If yes, will it be corrected? If not, how do you recommend that users mitigate this issue? Thank you! gthweng |
|
From: Hopf, D. <dan...@co...> - 2023-11-30 11:16:24
|
After some further digging, I now understand the behavior of this (which turns out to be fully as intended): The automotive slave config file overrides the default value of 'servo_offset_threshold' to 30: ptp4l[26251.269]: config item (null).servo_offset_threshold is 30 The (default) value of 'servo_num_offset_values' is 10: ptp4l[26251.269]: config item (null).servo_num_offset_values is 10 This leads to the slave transitioning from the servo state SERVO_LOCKED to SERVO_LOCKED_STABLE after 'servo_num_offset_vlaues' (10) reports of accuracy <= 'servo_offset_threshold' (30) are reached: ptp4l[26334.041]: PI servo: sync interval 1.000 kp 0.700 ki 0.300000 The accuracy is the first value in the log lines reported with "rms ...", e.g.: ptp4l[26333.540]: rms 24 max 60 freq +5559 +/- 33 delay 8899 +/- 0 --> 24 I would appreciate, if in that case some message like "Servo transitioning from SERVO_LOCKED to SERVO_LOCKED_STABLE" would be logged. I thought I saw something like that in other profiles, but this seems not reported using the default automotive-slave.cfg Thanks again for the help Richard! BR Daniel Internal -----Ursprüngliche Nachricht----- Von: Hopf, Daniel Gesendet: Dienstag, 28. November 2023 17:19 An: Richard Cochran <ric...@gm...> Cc: lin...@li... Betreff: AW: [Linuxptp-users] Slave takes VERY long to sync to Master using Automotive profile OK, to phrase it in my understanding: Master sends SYNC slower than slave "summary_interval": ptp4l slave reports the sample by "master offset ..." Master sends SYNC faster than slave "summary_interval" ptp4l slave reports the (average) statistics by "rms ..." Is that correct? Then the only unclear point left for me is how or when the *MASTER* decides to switch from sending SYNCs every 125 ms to sending SYNCs every one second. This seems arbitrary in my test setup. Thanks Daniel |
|
From: Richard C. <ric...@gm...> - 2023-11-29 17:56:05
|
On Wed, Nov 29, 2023 at 10:27:54PM +0800, paulzhn via Linuxptp-users wrote: > I'm wondering why the offset exists. - Linux system clock is in UTC timescale. - PHC is in TAI timescale. HTH, Richard |
|
From: <311...@qq...> - 2023-11-29 14:28:15
|
Hi, I want to sync my PHC clock with system clock as the source, so I executed the command: ptp4l -i ens2f1np1 -m phc2sys -a -r -r -m The phc2sys seems running correctly: $phc2sys -a -r -r -m phc2sys[7362514.851]: reconfiguring after port state change phc2sys[7362514.851]: selecting ens2f1np1 for synchronization phc2sys[7362514.851]: selecting CLOCK_REALTIME as the master clock phc2sys[7362514.851]: ens2f1np1 sys offset -149 s0 freq -6182 delay 385 phc2sys[7362515.851]: ens2f1np1 sys offset -152 s2 freq -6185 delay 382 phc2sys[7362516.851]: ens2f1np1 sys offset -143 s2 freq -6328 delay 380 However, it creates a stable offset between the phc clock and the system clock, which is about -37000000011ns: $phc_ctl ens2f1np1 cmp phc_ctl[7362590.195]: offset from CLOCK_REALTIME is -37000000001ns $phc_ctl ens2f1np1 cmp phc_ctl[7362590.688]: offset from CLOCK_REALTIME is -37000000004ns $phc_ctl ens2f1np1 cmp phc_ctl[7362591.107]: offset from CLOCK_REALTIME is -37000000002ns $phc_ctl ens2f1np1 cmp phc_ctl[7362591.476]: offset from CLOCK_REALTIME is -36999999999ns I'm wondering why the offset exists. The purpose for I want to do this sync is because the phc clock has a linear delay than the system clock, and I need to have an accuracy phc clock for the packet hardware timestamping. I'm not familiar with the nic hardware clock, don't know if it's normal. My OS is RedHat 8.6 with 4.18.0-372.9.1.el8.x86_64. The phc2sys and ptp4l version are 3.1.1. Thanks a lot. |
|
From: Hopf, D. <dan...@co...> - 2023-11-28 18:54:30
|
OK, to phrase it in my understanding: Master sends SYNC slower than slave "summary_interval": ptp4l slave reports the sample by "master offset ..." Master sends SYNC faster than slave "summary_interval" ptp4l slave reports the (average) statistics by "rms ..." Is that correct? Then the only unclear point left for me is how or when the *MASTER* decides to switch from sending SYNCs every 125 ms to sending SYNCs every one second. This seems arbitrary in my test setup. Thanks Daniel Internal |
|
From: Richard C. <ric...@gm...> - 2023-11-28 00:10:05
|
On Mon, Nov 27, 2023 at 08:18:54AM +0000, Hopf, Daniel wrote:
> Thanks Richard,
>
> Then maybe I misunderstood the output of ptp4l.
> I am specifically confused about the lines indicating "master
> offset" (which in my log started popping up after ~80 seconds, but
> sometimes don't show up even after 15 minutes) - what changed in the
> state of the synchronization that the logs suddenly changed from
> reporting "rms ... max ... freq ..." lines to reporting "master
> offset"?
That is only the reporting of the offset.
The offset reporting is rate limited by:
summary_interval
The time interval in which are printed summary statistics of the
clock. It is specified as a power of two in seconds. The statis‐
tics include offset root mean square (RMS), maximum absolute
offset, frequency offset mean and standard deviation, and path
delay mean and standard deviation. The units are nanoseconds and
parts per billion (ppb). If there is only one clock update in
the interval, the sample will be printed instead of the statis‐
tics. The messages are printed at the LOG_INFO level. The de‐
fault is 0 (1 second).
So when the Sync message period changes, the reporting format also changes.
HTH,
Richard
|
|
From: Hopf, D. <dan...@co...> - 2023-11-27 11:53:02
|
Thanks Richard, Then maybe I misunderstood the output of ptp4l. I am specifically confused about the lines indicating "master offset" (which in my log started popping up after ~80 seconds, but sometimes don't show up even after 15 minutes) - what changed in the state of the synchronization that the logs suddenly changed from reporting "rms ... max ... freq ..." lines to reporting "master offset"? Also, as soon as the slave starts showing "master offset" lines, the master sends its SYNC messages not every 125 ms anymore, but rather only once per second. I think this is due to the "automotive-master.cfg" having a "logSyncInterval" of -3 (= every 125 ms), and the "default.cfg" having a "operLogSyncInterval" of 0 (= every second)? So I assume that the Master first uses "logSyncInterval" and with the switch to reporting "master offset" lines, it somehow switches to "operLogSyncInterval" for it's Sync send timeouts? See this snippet here: ptp4l[26331.354]: port 1 (eth0): delay timeout ptp4l[26331.355]: delay filtered 8906 raw 8875 ptp4l[26331.532]: rms 31 max 56 freq +5554 +/- 42 delay 8906 +/- 0 ptp4l[26332.354]: port 1 (eth0): delay timeout ptp4l[26332.360]: delay filtered 8906 raw 8871 ptp4l[26332.535]: rms 47 max 71 freq +5586 +/- 60 delay 8906 +/- 0 ptp4l[26333.355]: port 1 (eth0): delay timeout ptp4l[26333.364]: delay filtered 8899 raw 8894 ptp4l[26333.540]: rms 24 max 60 freq +5559 +/- 33 delay 8899 +/- 0 ptp4l[26334.041]: PI servo: sync interval 1.000 kp 0.700 ki 0.300000 ptp4l[26334.041]: master offset -53 s2 freq +5515 path delay 8899 (<---- what triggers this now being shown instead of rms / max / freq?) ptp4l[26334.356]: port 1 (eth0): delay timeout ptp4l[26334.364]: delay filtered 8899 raw 8952 ptp4l[26335.042]: master offset 49 s2 freq +5602 path delay 8899 ptp4l[26336.042]: master offset -28 s2 freq +5539 path delay 8899 ptp4l[26337.042]: master offset 12 s2 freq +5571 path delay 8899 ptp4l[26338.043]: master offset -5 s2 freq +5557 path delay 8899 ptp4l[26338.356]: port 1 (eth0): delay timeout ptp4l[26338.364]: delay filtered 8899 raw 8949 ptp4l[26339.043]: master offset -13 s2 freq +5548 path delay 8899 ptp4l[26340.044]: master offset -118 s2 freq +5439 path delay 8899 ptp4l[26341.044]: master offset -10 s2 freq +5512 path delay 8899 ptp4l[26342.045]: master offset 40 s2 freq +5559 path delay 8899 Thanks, Daniel Internal -----Ursprüngliche Nachricht----- Von: Richard Cochran <ric...@gm...> Gesendet: Samstag, 25. November 2023 20:32 An: Hopf, Daniel <dan...@co...> Cc: lin...@li... Betreff: Re: [Linuxptp-users] Slave takes VERY long to sync to Master using Automotive profile CAUTION: This is an external email. Do not click or open any attachments unless you recognize the sender and know that the content is safe. (http://links.conti.de/mailcheck) On Fri, Nov 24, 2023 at 02:59:25PM +0000, Hopf, Daniel wrote: > Following are the logs of a try where they synced up after ~80 seconds. > Here's the SLAVE log (I increased neighborPropDelayThresh from 800 to 8000 and set tx_timestamp_timeout to 100 in my slave config file): > -(~/linuxptp-latest:$)-> sudo ./ptp4l -f > ./configs/automotive-slave-DH.cfg -i eth0 -m -l 7 > ptp4l[26253.262]: rms 25054 max 50349 <-- within 50 usec > ptp4l[26254.264]: rms 2904 max 3109 3 usec > ptp4l[26255.267]: rms 1722 max 2380 2 usec > ptp4l[26256.271]: rms 521 max 931 under 1 usec Why do you say it took 80 seconds? Log suggests client synchronized to within 50 microseconds after one second. Thanks, Richard |
|
From: Richard C. <ric...@gm...> - 2023-11-25 19:32:22
|
On Fri, Nov 24, 2023 at 02:59:25PM +0000, Hopf, Daniel wrote: > Following are the logs of a try where they synced up after ~80 seconds. > Here's the SLAVE log (I increased neighborPropDelayThresh from 800 to 8000 and set tx_timestamp_timeout to 100 in my slave config file): > -(~/linuxptp-latest:$)-> sudo ./ptp4l -f ./configs/automotive-slave-DH.cfg -i eth0 -m -l 7 > ptp4l[26253.262]: rms 25054 max 50349 <-- within 50 usec > ptp4l[26254.264]: rms 2904 max 3109 3 usec > ptp4l[26255.267]: rms 1722 max 2380 2 usec > ptp4l[26256.271]: rms 521 max 931 under 1 usec Why do you say it took 80 seconds? Log suggests client synchronized to within 50 microseconds after one second. Thanks, Richard |
|
From: Hopf, D. <dan...@co...> - 2023-11-24 19:33:10
|
I'm using the newest snapshot of linuxptp (ptp4l -v reports 4.1-00013-g458953c) for: - Master device (Intel NUC, containing a Intel i219-V NIC) - Slave device - an NVIDIA Orin Development Kit (Marvell AQR113C network chip I think) From my understanding, using the automotive profiles, Master and Slave should achieve a stable time-synchronization within less than 1 second (at least that's a typical automotive startup requirement). However, for me it takes a huge time until the Slave reports "master offset" values. Best-case for me was ~6 - 18 seconds, sometimes it takes a couple of minutes, sometimes it doesn't sync, even after 15 minutes. The two devices are connected directly to each other, using a 2m Ethernet cable. I know that the Intel i219-V seems to be quite broken in terms of its PTP compatibility: It has latency numbers in the 8000ns range, whereas one should expect something in the low hundreds. Interestingly, even the Marvell chip in the NVIDIA Orin seems to be worse, reporting a 1800ns delay. However, in the rare event that they actually *DO* SYNC up, I get quite good numbers in the +/-50ns accuracy range. Following are the logs of a try where they synced up after ~80 seconds. MASTER log (shortened and commented by me): daniel@nuc10:~/linuxptp$ sudo ./ptp4l -f ./configs/automotive-master.cfg -i eno1 -m -l 7 [sudo] password for daniel: ptp4l[26252.431]: config item (null).assume_two_step is 1 ptp4l[26252.431]: config item (null).check_fup_sync is 0 ptp4l[26252.431]: config item (null).tx_timestamp_timeout is 10 ptp4l[26252.431]: config item (null).hwts_filter is 0 ptp4l[26252.431]: config item (null).clock_servo is 0 ptp4l[26252.431]: config item (null).clock_type is 32768 ptp4l[26252.431]: config item (null).clock_servo is 0 ptp4l[26252.431]: config item (null).clockClass is 248 ptp4l[26252.431]: config item (null).clockAccuracy is 254 ptp4l[26252.432]: config item (null).offsetScaledLogVariance is 65535 ptp4l[26252.432]: config item (null).productDescription is ';;' ptp4l[26252.432]: config item (null).revisionData is ';;' ptp4l[26252.432]: config item (null).userDescription is '' ptp4l[26252.432]: config item (null).manufacturerIdentity is '00:00:00' ptp4l[26252.432]: config item (null).domainNumber is 0 ptp4l[26252.432]: config item (null).clientOnly is 0 ptp4l[26252.432]: config item (null).gmCapable is 1 ptp4l[26252.432]: config item (null).gmCapable is 1 ptp4l[26252.432]: config item (null).G.8275.defaultDS.localPriority is 128 ptp4l[26252.432]: config item (null).maxStepsRemoved is 255 ptp4l[26252.432]: config item (null).clock_class_threshold is 248 ptp4l[26252.432]: config item (null).time_stamping is 1 ptp4l[26252.432]: config item (null).twoStepFlag is 1 ptp4l[26252.432]: config item (null).twoStepFlag is 1 ptp4l[26252.432]: config item (null).time_stamping is 1 ptp4l[26252.432]: config item (null).priority1 is 248 ptp4l[26252.432]: config item (null).priority2 is 248 ptp4l[26252.432]: interface index 2 is up ptp4l[26252.432]: config item eno1.phc_index is -1 ptp4l[26252.432]: config item (null).free_running is 0 ptp4l[26252.432]: selected /dev/ptp0 as PTP clock ptp4l[26252.432]: config item (null).clockIdentity is '000000.0000.000000' ptp4l[26252.432]: config item (null).uds_address is '/var/run/ptp4l' ptp4l[26252.432]: section item /var/run/ptp4l.announceReceiptTimeout now 0 ptp4l[26252.432]: section item /var/run/ptp4l.delay_mechanism now 0 ptp4l[26252.432]: section item /var/run/ptp4l.network_transport now 0 ptp4l[26252.432]: section item /var/run/ptp4l.delay_filter_length now 1 ptp4l[26252.432]: config item (null).uds_ro_address is '/var/run/ptp4lro' ptp4l[26252.432]: section item /var/run/ptp4lro.announceReceiptTimeout now 0 ptp4l[26252.432]: section item /var/run/ptp4lro.delay_mechanism now 0 ptp4l[26252.432]: section item /var/run/ptp4lro.network_transport now 0 ptp4l[26252.432]: section item /var/run/ptp4lro.delay_filter_length now 1 ptp4l[26252.432]: config item (null).free_running is 0 ptp4l[26252.432]: config item (null).freq_est_interval is 1 ptp4l[26252.432]: config item (null).write_phase_mode is 0 ptp4l[26252.432]: config item (null).gmCapable is 1 ptp4l[26252.432]: config item (null).kernel_leap is 1 ptp4l[26252.432]: config item (null).utc_offset is 37 ptp4l[26252.432]: config item (null).timeSource is 160 ptp4l[26252.432]: config item (null).step_window is 0 ptp4l[26252.432]: config item (null).pi_proportional_const is 0.000000 ptp4l[26252.432]: config item (null).pi_integral_const is 0.000000 ptp4l[26252.432]: config item (null).pi_proportional_scale is 0.000000 ptp4l[26252.432]: config item (null).pi_proportional_exponent is -0.300000 ptp4l[26252.432]: config item (null).pi_proportional_norm_max is 0.700000 ptp4l[26252.432]: config item (null).pi_integral_scale is 0.000000 ptp4l[26252.432]: config item (null).pi_integral_exponent is 0.400000 ptp4l[26252.432]: config item (null).pi_integral_norm_max is 0.300000 ptp4l[26252.432]: config item (null).step_threshold is 0.000000 ptp4l[26252.432]: config item (null).first_step_threshold is 0.000020 ptp4l[26252.432]: config item (null).max_frequency is 900000000 ptp4l[26252.432]: config item (null).servo_offset_threshold is 0 ptp4l[26252.432]: config item (null).servo_num_offset_values is 10 ptp4l[26252.432]: config item (null).dataset_comparison is 0 ptp4l[26252.432]: config item (null).delay_filter_length is 10 ptp4l[26252.432]: config item (null).delay_filter is 1 ptp4l[26252.432]: config item (null).tsproc_mode is 0 ptp4l[26252.432]: config item (null).initial_delay is 0 ptp4l[26252.432]: config item (null).summary_interval is 0 ptp4l[26252.432]: config item (null).sanity_freq_limit is 200000000 ptp4l[26252.432]: PI servo: sync interval 1.000 kp 0.700 ki 0.300000 ptp4l[26252.432]: config item /var/run/ptp4l.phc_index is -1 ptp4l[26252.432]: config item /var/run/ptp4l.boundary_clock_jbod is 0 ptp4l[26252.432]: config item /var/run/ptp4l.serverOnly is 1 ptp4l[26252.432]: config item /var/run/ptp4l.BMCA is 1 ptp4l[26252.432]: config item /var/run/ptp4l.network_transport is 0 ptp4l[26252.432]: config item /var/run/ptp4l.delayAsymmetry is 0 ptp4l[26252.432]: config item /var/run/ptp4l.follow_up_info is 1 ptp4l[26252.432]: config item /var/run/ptp4l.freq_est_interval is 1 ptp4l[26252.432]: config item /var/run/ptp4l.msg_interval_request is 0 ptp4l[26252.432]: config item /var/run/ptp4l.net_sync_monitor is 0 ptp4l[26252.432]: config item /var/run/ptp4l.path_trace_enabled is 1 ptp4l[26252.432]: config item /var/run/ptp4l.tc_spanning_tree is 0 ptp4l[26252.432]: config item /var/run/ptp4l.ingressLatency is 0 ptp4l[26252.432]: config item /var/run/ptp4l.egressLatency is 0 ptp4l[26252.432]: config item /var/run/ptp4l.delay_mechanism is 0 ptp4l[26252.432]: config item /var/run/ptp4l.power_profile.version is 0 ptp4l[26252.432]: config item /var/run/ptp4l.power_profile.grandmasterID is 0 ptp4l[26252.432]: config item /var/run/ptp4l.power_profile.2011.grandmasterTimeInaccuracy is -1 ptp4l[26252.432]: config item /var/run/ptp4l.power_profile.2011.networkTimeInaccuracy is -1 ptp4l[26252.432]: config item /var/run/ptp4l.power_profile.2017.totalTimeInaccuracy is -1 ptp4l[26252.432]: config item /var/run/ptp4l.hybrid_e2e is 0 ptp4l[26252.432]: config item /var/run/ptp4l.fault_badpeernet_interval is 16 ptp4l[26252.432]: config item /var/run/ptp4l.fault_reset_interval is 4 ptp4l[26252.432]: config item /var/run/ptp4l.delay_filter_length is 1 ptp4l[26252.432]: config item /var/run/ptp4l.delay_filter is 1 ptp4l[26252.432]: config item /var/run/ptp4l.tsproc_mode is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.phc_index is -1 ptp4l[26252.432]: config item /var/run/ptp4lro.boundary_clock_jbod is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.serverOnly is 1 ptp4l[26252.432]: config item /var/run/ptp4lro.BMCA is 1 ptp4l[26252.432]: config item /var/run/ptp4lro.network_transport is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.delayAsymmetry is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.follow_up_info is 1 ptp4l[26252.432]: config item /var/run/ptp4lro.freq_est_interval is 1 ptp4l[26252.432]: config item /var/run/ptp4lro.msg_interval_request is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.net_sync_monitor is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.path_trace_enabled is 1 ptp4l[26252.432]: config item /var/run/ptp4lro.tc_spanning_tree is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.ingressLatency is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.egressLatency is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.delay_mechanism is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.power_profile.version is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.power_profile.grandmasterID is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.power_profile.2011.grandmasterTimeInaccuracy is -1 ptp4l[26252.432]: config item /var/run/ptp4lro.power_profile.2011.networkTimeInaccuracy is -1 ptp4l[26252.432]: config item /var/run/ptp4lro.power_profile.2017.totalTimeInaccuracy is -1 ptp4l[26252.432]: config item /var/run/ptp4lro.hybrid_e2e is 0 ptp4l[26252.432]: config item /var/run/ptp4lro.fault_badpeernet_interval is 16 ptp4l[26252.432]: config item /var/run/ptp4lro.fault_reset_interval is 4 ptp4l[26252.432]: config item /var/run/ptp4lro.delay_filter_length is 1 ptp4l[26252.432]: config item /var/run/ptp4lro.delay_filter is 1 ptp4l[26252.432]: config item /var/run/ptp4lro.tsproc_mode is 0 ptp4l[26252.432]: config item (null).slave_event_monitor is '' ptp4l[26252.432]: config item eno1.phc_index is -1 ptp4l[26252.432]: config item eno1.boundary_clock_jbod is 0 ptp4l[26252.432]: config item eno1.serverOnly is 1 ptp4l[26252.432]: config item eno1.BMCA is 1 ptp4l[26252.432]: config item eno1.network_transport is 3 ptp4l[26252.432]: config item eno1.delayAsymmetry is 0 ptp4l[26252.432]: config item eno1.follow_up_info is 1 ptp4l[26252.432]: config item eno1.freq_est_interval is 1 ptp4l[26252.433]: config item eno1.msg_interval_request is 0 ptp4l[26252.433]: config item eno1.net_sync_monitor is 0 ptp4l[26252.433]: config item eno1.path_trace_enabled is 1 ptp4l[26252.433]: config item eno1.tc_spanning_tree is 0 ptp4l[26252.433]: config item eno1.ingressLatency is 0 ptp4l[26252.433]: config item eno1.egressLatency is 0 ptp4l[26252.433]: config item eno1.delay_mechanism is 2 ptp4l[26252.433]: config item eno1.power_profile.version is 0 ptp4l[26252.433]: config item eno1.power_profile.grandmasterID is 0 ptp4l[26252.433]: config item eno1.power_profile.2011.grandmasterTimeInaccuracy is -1 ptp4l[26252.433]: config item eno1.power_profile.2011.networkTimeInaccuracy is -1 ptp4l[26252.433]: config item eno1.power_profile.2017.totalTimeInaccuracy is -1 ptp4l[26252.433]: config item eno1.unicast_master_table is 0 ptp4l[26252.433]: config item eno1.unicast_listen is 0 ptp4l[26252.433]: config item eno1.hybrid_e2e is 0 ptp4l[26252.433]: config item eno1.fault_badpeernet_interval is 16 ptp4l[26252.433]: config item eno1.fault_reset_interval is 4 ptp4l[26252.433]: config item eno1.delay_filter_length is 10 ptp4l[26252.433]: config item eno1.delay_filter is 1 ptp4l[26252.433]: config item eno1.tsproc_mode is 0 ptp4l[26252.433]: config item eno1.logMinDelayReqInterval is 0 ptp4l[26252.433]: config item eno1.logAnnounceInterval is 1 ptp4l[26252.433]: config item eno1.inhibit_announce is 1 ptp4l[26252.433]: config item eno1.ignore_source_id is 0 ptp4l[26252.433]: config item eno1.announceReceiptTimeout is 3 ptp4l[26252.433]: config item eno1.syncReceiptTimeout is 3 ptp4l[26252.433]: config item eno1.transportSpecific is 1 ptp4l[26252.433]: config item eno1.ignore_transport_specific is 0 ptp4l[26252.433]: config item eno1.G.8275.portDS.localPriority is 128 ptp4l[26252.433]: config item eno1.logSyncInterval is -3 ptp4l[26252.433]: config item eno1.operLogSyncInterval is 0 ptp4l[26252.433]: config item eno1.logMinPdelayReqInterval is 0 ptp4l[26252.433]: config item eno1.operLogPdelayReqInterval is 0 ptp4l[26252.433]: config item eno1.neighborPropDelayThresh is 800 ptp4l[26252.433]: config item eno1.min_neighbor_prop_delay is -20000000 ptp4l[26252.433]: config item eno1.delay_response_timeout is 0 ptp4l[26252.433]: config item eno1.interface_rate_tlv is 0 ptp4l[26252.433]: config item eno1.asCapable is 0 ptp4l[26252.433]: config item eno1.inhibit_delay_req is 1 ptp4l[26252.433]: config item eno1.ptp_dst_mac is '01:80:C2:00:00:0E' ptp4l[26252.433]: config item eno1.p2p_dst_mac is '01:80:C2:00:00:0E' ptp4l[26252.433]: config item global.socket_priority is 0 ptp4l[26252.496]: port 1 (eno1): INITIALIZING to MASTER on INIT_COMPLETE ptp4l[26252.496]: config item /var/run/ptp4l.logMinDelayReqInterval is 0 ptp4l[26252.496]: config item /var/run/ptp4l.logAnnounceInterval is 1 ptp4l[26252.496]: config item /var/run/ptp4l.inhibit_announce is 1 ptp4l[26252.496]: config item /var/run/ptp4l.ignore_source_id is 0 ptp4l[26252.496]: config item /var/run/ptp4l.announceReceiptTimeout is 0 ptp4l[26252.496]: config item /var/run/ptp4l.syncReceiptTimeout is 3 ptp4l[26252.496]: config item /var/run/ptp4l.transportSpecific is 1 ptp4l[26252.496]: config item /var/run/ptp4l.ignore_transport_specific is 0 ptp4l[26252.496]: config item /var/run/ptp4l.G.8275.portDS.localPriority is 128 ptp4l[26252.496]: config item /var/run/ptp4l.logSyncInterval is -3 ptp4l[26252.496]: config item /var/run/ptp4l.operLogSyncInterval is 0 ptp4l[26252.497]: config item /var/run/ptp4l.logMinPdelayReqInterval is 0 ptp4l[26252.497]: config item /var/run/ptp4l.operLogPdelayReqInterval is 0 ptp4l[26252.497]: config item /var/run/ptp4l.neighborPropDelayThresh is 800 ptp4l[26252.497]: config item /var/run/ptp4l.min_neighbor_prop_delay is -20000000 ptp4l[26252.497]: config item /var/run/ptp4l.delay_response_timeout is 0 ptp4l[26252.497]: config item /var/run/ptp4l.interface_rate_tlv is 0 ptp4l[26252.497]: config item /var/run/ptp4l.asCapable is 0 ptp4l[26252.497]: config item /var/run/ptp4l.inhibit_delay_req is 1 ptp4l[26252.497]: config item (null).uds_ro_address is '/var/run/ptp4lro' ptp4l[26252.497]: config item (null).uds_address is '/var/run/ptp4l' ptp4l[26252.497]: config item /var/run/ptp4l.uds_file_mode is 432 ptp4l[26252.497]: port 0 (/var/run/ptp4l): INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[26252.497]: config item /var/run/ptp4lro.logMinDelayReqInterval is 0 ptp4l[26252.497]: config item /var/run/ptp4lro.logAnnounceInterval is 1 ptp4l[26252.497]: config item /var/run/ptp4lro.inhibit_announce is 1 ptp4l[26252.497]: config item /var/run/ptp4lro.ignore_source_id is 0 ptp4l[26252.497]: config item /var/run/ptp4lro.announceReceiptTimeout is 0 ptp4l[26252.497]: config item /var/run/ptp4lro.syncReceiptTimeout is 3 ptp4l[26252.497]: config item /var/run/ptp4lro.transportSpecific is 1 ptp4l[26252.497]: config item /var/run/ptp4lro.ignore_transport_specific is 0 ptp4l[26252.497]: config item /var/run/ptp4lro.G.8275.portDS.localPriority is 128 ptp4l[26252.497]: config item /var/run/ptp4lro.logSyncInterval is -3 ptp4l[26252.497]: config item /var/run/ptp4lro.operLogSyncInterval is 0 ptp4l[26252.497]: config item /var/run/ptp4lro.logMinPdelayReqInterval is 0 ptp4l[26252.497]: config item /var/run/ptp4lro.operLogPdelayReqInterval is 0 ptp4l[26252.497]: config item /var/run/ptp4lro.neighborPropDelayThresh is 800 ptp4l[26252.497]: config item /var/run/ptp4lro.min_neighbor_prop_delay is -20000000 ptp4l[26252.497]: config item /var/run/ptp4lro.delay_response_timeout is 0 ptp4l[26252.497]: config item /var/run/ptp4lro.interface_rate_tlv is 0 ptp4l[26252.497]: config item /var/run/ptp4lro.asCapable is 0 ptp4l[26252.497]: config item /var/run/ptp4lro.inhibit_delay_req is 1 ptp4l[26252.497]: config item (null).uds_ro_address is '/var/run/ptp4lro' ptp4l[26252.497]: config item (null).uds_address is '/var/run/ptp4l' ptp4l[26252.498]: config item /var/run/ptp4lro.uds_ro_file_mode is 438 ptp4l[26252.498]: port 0 (/var/run/ptp4lro): INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[26252.498]: port 1 (eno1): received link status notification ptp4l[26252.498]: interface index 2 is up ptp4l[26252.622]: port 1 (eno1): master sync timeout ptp4l[26252.747]: port 1 (eno1): master sync timeout ptp4l[26252.872]: port 1 (eno1): master sync timeout ------------ [... master sync timeouts, every 125 ms ...] ptp4l[26256.757]: port 1 (eno1): master sync timeout ptp4l[26256.821]: port 1 (eno1): peer port id set to 48b02d.fffe.a5308a-1 ptp4l[26256.882]: port 1 (eno1): master sync timeout ------------ [... master sync timeouts, every 125 ms ...] ptp4l[26338.288]: port 1 (eno1): master sync timeout ptp4l[26338.413]: port 1 (eno1): master sync timeout ptp4l[26338.539]: port 1 (eno1): master sync timeout ------------ [here the SYNC locks, master switches from 125 ms sync timeouts to 1 s] ptp4l[26339.539]: port 1 (eno1): master sync timeout ptp4l[26340.540]: port 1 (eno1): master sync timeout ptp4l[26341.540]: port 1 (eno1): master sync timeout ptp4l[26342.541]: port 1 (eno1): master sync timeout ptp4l[26343.541]: port 1 (eno1): master sync timeout ptp4l[26344.541]: port 1 (eno1): master sync timeout ptp4l[26345.542]: port 1 (eno1): master sync timeout ptp4l[26346.542]: port 1 (eno1): master sync timeout ptp4l[26347.543]: port 1 (eno1): master sync timeout ptp4l[26348.543]: port 1 (eno1): master sync timeout ptp4l[26349.544]: port 1 (eno1): master sync timeout ptp4l[26350.544]: port 1 (eno1): master sync timeout ptp4l[26351.545]: port 1 (eno1): master sync timeout ptp4l[26352.545]: port 1 (eno1): master sync timeout ptp4l[26353.546]: port 1 (eno1): master sync timeout ptp4l[26354.546]: port 1 (eno1): master sync timeout ptp4l[26355.547]: port 1 (eno1): master sync timeout ptp4l[26356.547]: port 1 (eno1): master sync timeout ptp4l[26357.547]: port 1 (eno1): master sync timeout ptp4l[26358.547]: port 1 (eno1): master sync timeout ^Cdaniel@nuc10:~/linuxptp$ Here's the SLAVE log (I increased neighborPropDelayThresh from 800 to 8000 and set tx_timestamp_timeout to 100 in my slave config file): -(~/linuxptp-latest:$)-> sudo ./ptp4l -f ./configs/automotive-slave-DH.cfg -i eth0 -m -l 7 [sudo] password for daniel: ptp4l[26251.267]: config item (null).assume_two_step is 1 ptp4l[26251.267]: config item (null).check_fup_sync is 0 ptp4l[26251.267]: config item (null).tx_timestamp_timeout is 100 ptp4l[26251.267]: config item (null).hwts_filter is 0 ptp4l[26251.267]: config item (null).clock_servo is 0 ptp4l[26251.267]: config item (null).clock_type is 32768 ptp4l[26251.267]: config item (null).clock_servo is 0 ptp4l[26251.267]: config item (null).clockClass is 248 ptp4l[26251.267]: config item (null).clockAccuracy is 254 ptp4l[26251.267]: config item (null).offsetScaledLogVariance is 65535 ptp4l[26251.268]: config item (null).productDescription is ';;' ptp4l[26251.268]: config item (null).revisionData is ';;' ptp4l[26251.268]: config item (null).userDescription is '' ptp4l[26251.268]: config item (null).manufacturerIdentity is '00:00:00' ptp4l[26251.268]: config item (null).domainNumber is 0 ptp4l[26251.268]: config item (null).clientOnly is 1 ptp4l[26251.268]: config item (null).gmCapable is 1 ptp4l[26251.268]: config item (null).gmCapable is 1 ptp4l[26251.268]: config item (null).G.8275.defaultDS.localPriority is 128 ptp4l[26251.268]: config item (null).maxStepsRemoved is 255 ptp4l[26251.268]: config item (null).clock_class_threshold is 248 ptp4l[26251.268]: config item (null).time_stamping is 1 ptp4l[26251.268]: config item (null).twoStepFlag is 1 ptp4l[26251.268]: config item (null).twoStepFlag is 1 ptp4l[26251.268]: config item (null).time_stamping is 1 ptp4l[26251.268]: config item (null).priority1 is 248 ptp4l[26251.268]: config item (null).priority2 is 248 ptp4l[26251.268]: interface index 3 is up ptp4l[26251.268]: config item eth0.phc_index is -1 ptp4l[26251.268]: config item (null).free_running is 0 ptp4l[26251.268]: selected /dev/ptp0 as PTP clock ptp4l[26251.268]: config item (null).clockIdentity is '000000.0000.000000' ptp4l[26251.268]: config item (null).uds_address is '/var/run/ptp4l' ptp4l[26251.268]: section item /var/run/ptp4l.announceReceiptTimeout now 0 ptp4l[26251.268]: section item /var/run/ptp4l.delay_mechanism now 0 ptp4l[26251.268]: section item /var/run/ptp4l.network_transport now 0 ptp4l[26251.268]: section item /var/run/ptp4l.delay_filter_length now 1 ptp4l[26251.268]: config item (null).uds_ro_address is '/var/run/ptp4lro' ptp4l[26251.268]: section item /var/run/ptp4lro.announceReceiptTimeout now 0 ptp4l[26251.268]: section item /var/run/ptp4lro.delay_mechanism now 0 ptp4l[26251.268]: section item /var/run/ptp4lro.network_transport now 0 ptp4l[26251.268]: section item /var/run/ptp4lro.delay_filter_length now 1 ptp4l[26251.268]: config item (null).free_running is 0 ptp4l[26251.268]: config item (null).freq_est_interval is 1 ptp4l[26251.268]: config item (null).write_phase_mode is 0 ptp4l[26251.268]: config item (null).gmCapable is 1 ptp4l[26251.268]: config item (null).kernel_leap is 1 ptp4l[26251.268]: config item (null).utc_offset is 37 ptp4l[26251.268]: config item (null).timeSource is 160 ptp4l[26251.268]: config item (null).step_window is 0 ptp4l[26251.268]: config item (null).pi_proportional_const is 0.000000 ptp4l[26251.269]: config item (null).pi_integral_const is 0.000000 ptp4l[26251.269]: config item (null).pi_proportional_scale is 0.000000 ptp4l[26251.269]: config item (null).pi_proportional_exponent is -0.300000 ptp4l[26251.269]: config item (null).pi_proportional_norm_max is 0.700000 ptp4l[26251.269]: config item (null).pi_integral_scale is 0.000000 ptp4l[26251.269]: config item (null).pi_integral_exponent is 0.400000 ptp4l[26251.269]: config item (null).pi_integral_norm_max is 0.300000 ptp4l[26251.269]: config item (null).step_threshold is 1.000000 ptp4l[26251.269]: config item (null).first_step_threshold is 0.000020 ptp4l[26251.269]: config item (null).max_frequency is 900000000 ptp4l[26251.269]: config item (null).servo_offset_threshold is 30 ptp4l[26251.269]: config item (null).servo_num_offset_values is 10 ptp4l[26251.269]: config item (null).dataset_comparison is 0 ptp4l[26251.269]: config item (null).tsproc_mode is 0 ptp4l[26251.269]: config item (null).delay_filter is 1 ptp4l[26251.269]: config item (null).delay_filter_length is 10 ptp4l[26251.269]: config item (null).initial_delay is 0 ptp4l[26251.269]: config item (null).summary_interval is 0 ptp4l[26251.269]: config item (null).sanity_freq_limit is 200000000 ptp4l[26251.269]: PI servo: sync interval 1.000 kp 0.700 ki 0.300000 ptp4l[26251.269]: config item /var/run/ptp4l.phc_index is -1 ptp4l[26251.269]: config item /var/run/ptp4l.boundary_clock_jbod is 0 ptp4l[26251.269]: config item /var/run/ptp4l.serverOnly is 0 ptp4l[26251.269]: config item /var/run/ptp4l.BMCA is 1 ptp4l[26251.269]: config item /var/run/ptp4l.network_transport is 0 ptp4l[26251.269]: config item /var/run/ptp4l.delayAsymmetry is 0 ptp4l[26251.269]: config item /var/run/ptp4l.follow_up_info is 1 ptp4l[26251.269]: config item /var/run/ptp4l.freq_est_interval is 1 ptp4l[26251.269]: config item /var/run/ptp4l.msg_interval_request is 1 ptp4l[26251.269]: config item /var/run/ptp4l.net_sync_monitor is 0 ptp4l[26251.269]: config item /var/run/ptp4l.path_trace_enabled is 1 ptp4l[26251.269]: config item /var/run/ptp4l.tc_spanning_tree is 0 ptp4l[26251.269]: config item /var/run/ptp4l.ingressLatency is 0 ptp4l[26251.269]: config item /var/run/ptp4l.egressLatency is 0 ptp4l[26251.269]: config item /var/run/ptp4l.delay_mechanism is 0 ptp4l[26251.269]: config item /var/run/ptp4l.power_profile.version is 0 ptp4l[26251.269]: config item /var/run/ptp4l.power_profile.grandmasterID is 0 ptp4l[26251.269]: config item /var/run/ptp4l.power_profile.2011.grandmasterTimeInaccuracy is -1 ptp4l[26251.269]: config item /var/run/ptp4l.power_profile.2011.networkTimeInaccuracy is -1 ptp4l[26251.269]: config item /var/run/ptp4l.power_profile.2017.totalTimeInaccuracy is -1 ptp4l[26251.269]: config item /var/run/ptp4l.hybrid_e2e is 0 ptp4l[26251.269]: config item /var/run/ptp4l.fault_badpeernet_interval is 16 ptp4l[26251.269]: config item /var/run/ptp4l.fault_reset_interval is 4 ptp4l[26251.269]: config item /var/run/ptp4l.tsproc_mode is 0 ptp4l[26251.269]: config item /var/run/ptp4l.delay_filter is 1 ptp4l[26251.269]: config item /var/run/ptp4l.delay_filter_length is 1 ptp4l[26251.269]: config item /var/run/ptp4lro.phc_index is -1 ptp4l[26251.269]: config item /var/run/ptp4lro.boundary_clock_jbod is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.serverOnly is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.BMCA is 1 ptp4l[26251.269]: config item /var/run/ptp4lro.network_transport is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.delayAsymmetry is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.follow_up_info is 1 ptp4l[26251.269]: config item /var/run/ptp4lro.freq_est_interval is 1 ptp4l[26251.269]: config item /var/run/ptp4lro.msg_interval_request is 1 ptp4l[26251.269]: config item /var/run/ptp4lro.net_sync_monitor is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.path_trace_enabled is 1 ptp4l[26251.269]: config item /var/run/ptp4lro.tc_spanning_tree is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.ingressLatency is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.egressLatency is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.delay_mechanism is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.power_profile.version is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.power_profile.grandmasterID is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.power_profile.2011.grandmasterTimeInaccuracy is -1 ptp4l[26251.269]: config item /var/run/ptp4lro.power_profile.2011.networkTimeInaccuracy is -1 ptp4l[26251.269]: config item /var/run/ptp4lro.power_profile.2017.totalTimeInaccuracy is -1 ptp4l[26251.269]: config item /var/run/ptp4lro.hybrid_e2e is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.fault_badpeernet_interval is 16 ptp4l[26251.269]: config item /var/run/ptp4lro.fault_reset_interval is 4 ptp4l[26251.269]: config item /var/run/ptp4lro.tsproc_mode is 0 ptp4l[26251.269]: config item /var/run/ptp4lro.delay_filter is 1 ptp4l[26251.269]: config item /var/run/ptp4lro.delay_filter_length is 1 ptp4l[26251.269]: config item (null).slave_event_monitor is '' ptp4l[26251.269]: config item eth0.phc_index is -1 ptp4l[26251.269]: config item eth0.boundary_clock_jbod is 0 ptp4l[26251.269]: config item eth0.serverOnly is 0 ptp4l[26251.269]: config item eth0.BMCA is 1 ptp4l[26251.269]: config item eth0.network_transport is 3 ptp4l[26251.269]: config item eth0.delayAsymmetry is 0 ptp4l[26251.269]: config item eth0.follow_up_info is 1 ptp4l[26251.269]: config item eth0.freq_est_interval is 1 ptp4l[26251.269]: config item eth0.msg_interval_request is 1 ptp4l[26251.269]: config item eth0.net_sync_monitor is 0 ptp4l[26251.269]: config item eth0.path_trace_enabled is 1 ptp4l[26251.269]: config item eth0.tc_spanning_tree is 0 ptp4l[26251.269]: config item eth0.ingressLatency is 0 ptp4l[26251.269]: config item eth0.egressLatency is 0 ptp4l[26251.269]: config item eth0.delay_mechanism is 2 ptp4l[26251.269]: config item eth0.power_profile.version is 0 ptp4l[26251.269]: config item eth0.power_profile.grandmasterID is 0 ptp4l[26251.269]: config item eth0.power_profile.2011.grandmasterTimeInaccuracy is -1 ptp4l[26251.269]: config item eth0.power_profile.2011.networkTimeInaccuracy is -1 ptp4l[26251.269]: config item eth0.power_profile.2017.totalTimeInaccuracy is -1 ptp4l[26251.269]: config item eth0.unicast_master_table is 0 ptp4l[26251.269]: config item eth0.unicast_listen is 0 ptp4l[26251.269]: config item eth0.hybrid_e2e is 0 ptp4l[26251.269]: config item eth0.fault_badpeernet_interval is 16 ptp4l[26251.269]: config item eth0.fault_reset_interval is 4 ptp4l[26251.269]: config item eth0.tsproc_mode is 0 ptp4l[26251.269]: config item eth0.delay_filter is 1 ptp4l[26251.269]: config item eth0.delay_filter_length is 10 ptp4l[26251.269]: config item eth0.logMinDelayReqInterval is 0 ptp4l[26251.269]: config item eth0.logAnnounceInterval is 1 ptp4l[26251.269]: config item eth0.inhibit_announce is 1 ptp4l[26251.269]: config item eth0.ignore_source_id is 1 ptp4l[26251.269]: config item eth0.announceReceiptTimeout is 3 ptp4l[26251.269]: config item eth0.syncReceiptTimeout is 3 ptp4l[26251.269]: config item eth0.transportSpecific is 1 ptp4l[26251.269]: config item eth0.ignore_transport_specific is 0 ptp4l[26251.269]: config item eth0.G.8275.portDS.localPriority is 128 ptp4l[26251.269]: config item eth0.logSyncInterval is -3 ptp4l[26251.269]: config item eth0.operLogSyncInterval is 0 ptp4l[26251.269]: config item eth0.logMinPdelayReqInterval is 0 ptp4l[26251.269]: config item eth0.operLogPdelayReqInterval is 2 ptp4l[26251.269]: config item eth0.neighborPropDelayThresh is 8000 ptp4l[26251.269]: config item eth0.min_neighbor_prop_delay is -20000000 ptp4l[26251.269]: config item eth0.delay_response_timeout is 0 ptp4l[26251.269]: config item eth0.interface_rate_tlv is 0 ptp4l[26251.269]: config item eth0.asCapable is 0 ptp4l[26251.269]: config item eth0.inhibit_delay_req is 0 ptp4l[26251.270]: config item eth0.ptp_dst_mac is '01:80:C2:00:00:0E' ptp4l[26251.270]: config item eth0.p2p_dst_mac is '01:80:C2:00:00:0E' ptp4l[26251.270]: config item global.socket_priority is 0 ptp4l[26251.321]: port 1 (eth0): INITIALIZING to SLAVE on INIT_COMPLETE ptp4l[26251.321]: config item /var/run/ptp4l.logMinDelayReqInterval is 0 ptp4l[26251.321]: config item /var/run/ptp4l.logAnnounceInterval is 1 ptp4l[26251.321]: config item /var/run/ptp4l.inhibit_announce is 1 ptp4l[26251.321]: config item /var/run/ptp4l.ignore_source_id is 1 ptp4l[26251.321]: config item /var/run/ptp4l.announceReceiptTimeout is 0 ptp4l[26251.321]: config item /var/run/ptp4l.syncReceiptTimeout is 3 ptp4l[26251.321]: config item /var/run/ptp4l.transportSpecific is 1 ptp4l[26251.321]: config item /var/run/ptp4l.ignore_transport_specific is 0 ptp4l[26251.321]: config item /var/run/ptp4l.G.8275.portDS.localPriority is 128 ptp4l[26251.321]: config item /var/run/ptp4l.logSyncInterval is -3 ptp4l[26251.321]: config item /var/run/ptp4l.operLogSyncInterval is 0 ptp4l[26251.321]: config item /var/run/ptp4l.logMinPdelayReqInterval is 0 ptp4l[26251.321]: config item /var/run/ptp4l.operLogPdelayReqInterval is 2 ptp4l[26251.321]: config item /var/run/ptp4l.neighborPropDelayThresh is 8000 ptp4l[26251.321]: config item /var/run/ptp4l.min_neighbor_prop_delay is -20000000 ptp4l[26251.321]: config item /var/run/ptp4l.delay_response_timeout is 0 ptp4l[26251.321]: config item /var/run/ptp4l.interface_rate_tlv is 0 ptp4l[26251.321]: config item /var/run/ptp4l.asCapable is 0 ptp4l[26251.321]: config item /var/run/ptp4l.inhibit_delay_req is 0 ptp4l[26251.321]: config item (null).uds_ro_address is '/var/run/ptp4lro' ptp4l[26251.321]: config item (null).uds_address is '/var/run/ptp4l' ptp4l[26251.322]: config item /var/run/ptp4l.uds_file_mode is 432 ptp4l[26251.322]: port 0 (/var/run/ptp4l): INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[26251.322]: config item /var/run/ptp4lro.logMinDelayReqInterval is 0 ptp4l[26251.322]: config item /var/run/ptp4lro.logAnnounceInterval is 1 ptp4l[26251.322]: config item /var/run/ptp4lro.inhibit_announce is 1 ptp4l[26251.322]: config item /var/run/ptp4lro.ignore_source_id is 1 ptp4l[26251.322]: config item /var/run/ptp4lro.announceReceiptTimeout is 0 ptp4l[26251.322]: config item /var/run/ptp4lro.syncReceiptTimeout is 3 ptp4l[26251.322]: config item /var/run/ptp4lro.transportSpecific is 1 ptp4l[26251.322]: config item /var/run/ptp4lro.ignore_transport_specific is 0 ptp4l[26251.322]: config item /var/run/ptp4lro.G.8275.portDS.localPriority is 128 ptp4l[26251.322]: config item /var/run/ptp4lro.logSyncInterval is -3 ptp4l[26251.322]: config item /var/run/ptp4lro.operLogSyncInterval is 0 ptp4l[26251.322]: config item /var/run/ptp4lro.logMinPdelayReqInterval is 0 ptp4l[26251.322]: config item /var/run/ptp4lro.operLogPdelayReqInterval is 2 ptp4l[26251.322]: config item /var/run/ptp4lro.neighborPropDelayThresh is 8000 ptp4l[26251.322]: config item /var/run/ptp4lro.min_neighbor_prop_delay is -20000000 ptp4l[26251.322]: config item /var/run/ptp4lro.delay_response_timeout is 0 ptp4l[26251.322]: config item /var/run/ptp4lro.interface_rate_tlv is 0 ptp4l[26251.322]: config item /var/run/ptp4lro.asCapable is 0 ptp4l[26251.322]: config item /var/run/ptp4lro.inhibit_delay_req is 0 ptp4l[26251.322]: config item (null).uds_ro_address is '/var/run/ptp4lro' ptp4l[26251.322]: config item (null).uds_address is '/var/run/ptp4l' ptp4l[26251.322]: config item /var/run/ptp4lro.uds_ro_file_mode is 438 ptp4l[26251.322]: port 0 (/var/run/ptp4lro): INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[26251.322]: port 1 (eth0): received link status notification ptp4l[26251.322]: interface index 3 is up ptp4l[26251.382]: PI servo: sync interval 0.125 kp 1.306 ki 0.130583 ptp4l[26252.321]: port 1 (eth0): delay timeout ptp4l[26252.323]: port 1 (eth0): peer port id set to 1c697a.fffe.a99e34-1 ptp4l[26252.323]: delay filtered 8905 raw 8905 ptp4l[26253.262]: rms 25054 max 50349 freq +8642 +/- 1995 delay 8905 +/- 0 ptp4l[26253.321]: port 1 (eth0): delay timeout ptp4l[26253.328]: delay filtered 8880 raw 8856 ptp4l[26254.264]: rms 2904 max 3109 freq +4871 +/- 605 delay 8880 +/- 0 ptp4l[26254.322]: port 1 (eth0): delay timeout ptp4l[26254.328]: delay filtered 8905 raw 8924 ptp4l[26255.267]: rms 1722 max 2380 freq +4115 +/- 165 delay 8905 +/- 0 ptp4l[26255.322]: port 1 (eth0): delay timeout ptp4l[26255.332]: delay filtered 8914 raw 8964 ptp4l[26256.271]: rms 521 max 931 freq +4741 +/- 245 delay 8914 +/- 0 ptp4l[26256.322]: port 1 (eth0): delay timeout ptp4l[26256.328]: delay filtered 8906 raw 8906 ptp4l[26257.274]: rms 141 max 206 freq +5405 +/- 135 delay 8906 +/- 0 ptp4l[26257.322]: port 1 (eth0): delay timeout ptp4l[26257.328]: delay filtered 8915 raw 8934 ptp4l[26257.950]: port 1 (eth0): announce timeout ptp4l[26258.085]: port 1 (eth0): received link status notification ptp4l[26258.277]: rms 165 max 208 freq +5638 +/- 28 delay 8915 +/- 0 ptp4l[26258.322]: port 1 (eth0): delay timeout ptp4l[26258.328]: delay filtered 8906 raw 8885 ptp4l[26259.281]: rms 96 max 176 freq +5658 +/- 56 delay 8906 +/- 0 ptp4l[26259.322]: port 1 (eth0): delay timeout ptp4l[26259.328]: delay filtered 8905 raw 8900 ptp4l[26260.285]: rms 36 max 84 freq +5625 +/- 37 delay 8905 +/- 0 ptp4l[26260.323]: port 1 (eth0): delay timeout ptp4l[26260.328]: delay filtered 8906 raw 8927 ptp4l[26261.288]: rms 45 max 77 freq +5542 +/- 44 delay 8906 +/- 0 ptp4l[26261.323]: port 1 (eth0): delay timeout ptp4l[26261.328]: delay filtered 8915 raw 8925 ptp4l[26262.293]: rms 35 max 78 freq +5569 +/- 48 delay 8915 +/- 0 ptp4l[26262.323]: port 1 (eth0): delay timeout ptp4l[26262.332]: delay filtered 8915 raw 8892 ptp4l[26263.296]: rms 45 max 70 freq +5512 +/- 46 delay 8915 +/- 0 ptp4l[26263.323]: port 1 (eth0): delay timeout ptp4l[26263.325]: delay filtered 8915 raw 8882 ptp4l[26264.299]: rms 40 max 62 freq +5562 +/- 52 delay 8915 +/- 0 ptp4l[26264.324]: port 1 (eth0): delay timeout ptp4l[26264.332]: delay filtered 8915 raw 8941 ptp4l[26265.303]: rms 32 max 55 freq +5545 +/- 43 delay 8915 +/- 0 ptp4l[26265.325]: port 1 (eth0): delay timeout ptp4l[26265.332]: delay filtered 8912 raw 8919 ptp4l[26266.306]: rms 30 max 59 freq +5541 +/- 41 delay 8912 +/- 0 ptp4l[26266.325]: port 1 (eth0): delay timeout ptp4l[26266.332]: delay filtered 8922 raw 8932 ptp4l[26267.309]: rms 31 max 71 freq +5539 +/- 42 delay 8922 +/- 0 ptp4l[26267.326]: port 1 (eth0): delay timeout ptp4l[26267.332]: delay filtered 8909 raw 8898 ptp4l[26268.313]: rms 44 max 69 freq +5504 +/- 54 delay 8909 +/- 0 ptp4l[26268.326]: port 1 (eth0): delay timeout ptp4l[26268.332]: delay filtered 8922 raw 8940 ptp4l[26269.316]: rms 32 max 78 freq +5506 +/- 42 delay 8922 +/- 0 ptp4l[26269.326]: port 1 (eth0): delay timeout ptp4l[26269.332]: delay filtered 8926 raw 8945 ptp4l[26270.320]: rms 33 max 47 freq +5517 +/- 46 delay 8926 +/- 0 ptp4l[26270.327]: port 1 (eth0): delay timeout ptp4l[26270.332]: delay filtered 8928 raw 8960 ptp4l[26271.324]: rms 29 max 55 freq +5491 +/- 34 delay 8928 +/- 0 ptp4l[26271.327]: port 1 (eth0): delay timeout ptp4l[26271.328]: delay filtered 8936 raw 8965 ptp4l[26272.327]: rms 37 max 58 freq +5479 +/- 48 delay 8936 +/- 0 ptp4l[26272.327]: port 1 (eth0): delay timeout ptp4l[26272.336]: delay filtered 8936 raw 8920 ptp4l[26273.328]: port 1 (eth0): delay timeout ptp4l[26273.336]: delay filtered 8936 raw 8932 ptp4l[26273.336]: rms 49 max 64 freq +5528 +/- 61 delay 8936 +/- 0 ptp4l[26274.329]: port 1 (eth0): delay timeout ptp4l[26274.336]: delay filtered 8932 raw 8862 ptp4l[26274.336]: rms 33 max 61 freq +5514 +/- 45 delay 8932 +/- 0 ptp4l[26275.329]: port 1 (eth0): delay timeout ptp4l[26275.331]: delay filtered 8936 raw 8940 ptp4l[26275.337]: rms 41 max 78 freq +5480 +/- 51 delay 8936 +/- 0 ptp4l[26276.330]: port 1 (eth0): delay timeout ptp4l[26276.340]: delay filtered 8937 raw 8934 ptp4l[26276.340]: rms 45 max 81 freq +5473 +/- 59 delay 8937 +/- 0 ptp4l[26277.330]: port 1 (eth0): delay timeout ptp4l[26277.336]: delay filtered 8937 raw 8912 ptp4l[26277.344]: rms 39 max 71 freq +5468 +/- 52 delay 8937 +/- 0 ptp4l[26278.330]: port 1 (eth0): delay timeout ptp4l[26278.336]: delay filtered 8933 raw 8928 ptp4l[26278.347]: rms 47 max 73 freq +5495 +/- 63 delay 8933 +/- 0 ptp4l[26279.331]: port 1 (eth0): delay timeout ptp4l[26279.336]: delay filtered 8933 raw 8961 ptp4l[26279.350]: rms 34 max 76 freq +5491 +/- 47 delay 8933 +/- 0 ptp4l[26280.331]: port 1 (eth0): delay timeout ptp4l[26280.340]: delay filtered 8933 raw 8950 ptp4l[26280.354]: rms 31 max 58 freq +5478 +/- 43 delay 8933 +/- 0 ptp4l[26281.332]: port 1 (eth0): delay timeout ptp4l[26281.340]: delay filtered 8930 raw 8904 ptp4l[26281.358]: rms 37 max 48 freq +5490 +/- 51 delay 8930 +/- 0 ptp4l[26282.332]: port 1 (eth0): delay timeout ptp4l[26282.340]: delay filtered 8930 raw 8909 ptp4l[26282.361]: rms 49 max 69 freq +5446 +/- 60 delay 8930 +/- 0 ptp4l[26283.333]: port 1 (eth0): delay timeout ptp4l[26283.340]: delay filtered 8920 raw 8853 ptp4l[26283.365]: rms 39 max 75 freq +5461 +/- 53 delay 8920 +/- 0 ptp4l[26284.334]: port 1 (eth0): delay timeout ptp4l[26284.340]: delay filtered 8920 raw 8900 ptp4l[26284.369]: rms 35 max 71 freq +5504 +/- 38 delay 8920 +/- 0 ptp4l[26285.334]: port 1 (eth0): delay timeout ptp4l[26285.344]: delay filtered 8910 raw 8882 ptp4l[26285.373]: rms 49 max 68 freq +5489 +/- 67 delay 8910 +/- 0 ptp4l[26286.335]: port 1 (eth0): delay timeout ptp4l[26286.340]: delay filtered 8910 raw 8929 ptp4l[26286.376]: rms 38 max 70 freq +5477 +/- 52 delay 8910 +/- 0 ptp4l[26287.336]: port 1 (eth0): delay timeout ptp4l[26287.344]: delay filtered 8906 raw 8872 ptp4l[26287.379]: rms 40 max 72 freq +5519 +/- 47 delay 8906 +/- 0 ptp4l[26288.336]: port 1 (eth0): delay timeout ptp4l[26288.344]: delay filtered 8906 raw 8939 ptp4l[26288.381]: rms 41 max 78 freq +5463 +/- 49 delay 8906 +/- 0 ptp4l[26289.336]: port 1 (eth0): delay timeout ptp4l[26289.344]: delay filtered 8905 raw 8906 ptp4l[26289.385]: rms 49 max 76 freq +5485 +/- 67 delay 8905 +/- 0 ptp4l[26290.336]: port 1 (eth0): delay timeout ptp4l[26290.344]: delay filtered 8905 raw 8968 ptp4l[26290.388]: rms 32 max 47 freq +5496 +/- 44 delay 8905 +/- 0 ptp4l[26291.337]: port 1 (eth0): delay timeout ptp4l[26291.344]: delay filtered 8903 raw 8882 ptp4l[26291.391]: rms 31 max 51 freq +5468 +/- 41 delay 8903 +/- 0 ptp4l[26292.337]: port 1 (eth0): delay timeout ptp4l[26292.344]: delay filtered 8896 raw 8893 ptp4l[26292.394]: rms 21 max 40 freq +5486 +/- 28 delay 8896 +/- 0 ptp4l[26293.338]: port 1 (eth0): delay timeout ptp4l[26293.344]: delay filtered 8903 raw 8957 ptp4l[26293.397]: rms 40 max 74 freq +5495 +/- 54 delay 8903 +/- 0 ptp4l[26294.338]: port 1 (eth0): delay timeout ptp4l[26294.344]: delay filtered 8912 raw 8919 ptp4l[26294.401]: rms 39 max 65 freq +5483 +/- 54 delay 8912 +/- 0 ptp4l[26295.339]: port 1 (eth0): delay timeout ptp4l[26295.344]: delay filtered 8912 raw 8904 ptp4l[26295.405]: rms 38 max 57 freq +5476 +/- 52 delay 8912 +/- 0 ptp4l[26296.339]: port 1 (eth0): delay timeout ptp4l[26296.340]: delay filtered 8905 raw 8882 ptp4l[26296.410]: rms 40 max 65 freq +5504 +/- 54 delay 8905 +/- 0 ptp4l[26297.339]: port 1 (eth0): delay timeout ptp4l[26297.348]: delay filtered 8912 raw 8920 ptp4l[26297.413]: rms 30 max 55 freq +5505 +/- 41 delay 8912 +/- 0 ptp4l[26298.340]: port 1 (eth0): delay timeout ptp4l[26298.348]: delay filtered 8905 raw 8889 ptp4l[26298.416]: rms 53 max 70 freq +5488 +/- 71 delay 8905 +/- 0 ptp4l[26299.340]: port 1 (eth0): delay timeout ptp4l[26299.348]: delay filtered 8905 raw 8907 ptp4l[26299.420]: rms 27 max 39 freq +5533 +/- 26 delay 8905 +/- 0 ptp4l[26300.341]: port 1 (eth0): delay timeout ptp4l[26300.348]: delay filtered 8898 raw 8889 ptp4l[26300.423]: rms 38 max 62 freq +5523 +/- 51 delay 8898 +/- 0 ptp4l[26301.341]: port 1 (eth0): delay timeout ptp4l[26301.348]: delay filtered 8898 raw 8887 ptp4l[26301.426]: rms 31 max 46 freq +5532 +/- 41 delay 8898 +/- 0 ptp4l[26302.341]: port 1 (eth0): delay timeout ptp4l[26302.348]: delay filtered 8905 raw 8987 ptp4l[26302.430]: rms 34 max 76 freq +5511 +/- 46 delay 8905 +/- 0 ptp4l[26303.341]: port 1 (eth0): delay timeout ptp4l[26303.348]: delay filtered 8905 raw 8958 ptp4l[26303.434]: rms 34 max 64 freq +5472 +/- 33 delay 8905 +/- 0 ptp4l[26304.341]: port 1 (eth0): delay timeout ptp4l[26304.343]: delay filtered 8905 raw 8912 ptp4l[26304.437]: rms 52 max 97 freq +5545 +/- 62 delay 8905 +/- 0 ptp4l[26305.342]: port 1 (eth0): delay timeout ptp4l[26305.348]: delay filtered 8909 raw 8942 ptp4l[26305.441]: rms 41 max 58 freq +5525 +/- 56 delay 8909 +/- 0 ptp4l[26306.343]: port 1 (eth0): delay timeout ptp4l[26306.344]: delay filtered 8916 raw 8954 ptp4l[26306.445]: rms 41 max 62 freq +5541 +/- 55 delay 8916 +/- 0 ptp4l[26307.344]: port 1 (eth0): delay timeout ptp4l[26307.352]: delay filtered 8910 raw 8908 ptp4l[26307.449]: rms 43 max 89 freq +5553 +/- 57 delay 8910 +/- 0 ptp4l[26308.344]: port 1 (eth0): delay timeout ptp4l[26308.352]: delay filtered 8910 raw 8889 ptp4l[26308.452]: rms 35 max 61 freq +5542 +/- 48 delay 8910 +/- 0 ptp4l[26309.344]: port 1 (eth0): delay timeout ptp4l[26309.352]: delay filtered 8927 raw 8960 ptp4l[26309.456]: rms 52 max 92 freq +5586 +/- 65 delay 8927 +/- 0 ptp4l[26310.345]: port 1 (eth0): delay timeout ptp4l[26310.352]: delay filtered 8927 raw 8872 ptp4l[26310.460]: rms 40 max 70 freq +5555 +/- 55 delay 8927 +/- 0 ptp4l[26311.345]: port 1 (eth0): delay timeout ptp4l[26311.352]: delay filtered 8927 raw 8865 ptp4l[26311.464]: rms 36 max 57 freq +5573 +/- 49 delay 8927 +/- 0 ptp4l[26312.346]: port 1 (eth0): delay timeout ptp4l[26312.352]: delay filtered 8927 raw 8942 ptp4l[26312.466]: rms 40 max 73 freq +5573 +/- 56 delay 8927 +/- 0 ptp4l[26313.346]: port 1 (eth0): delay timeout ptp4l[26313.352]: delay filtered 8910 raw 8888 ptp4l[26313.470]: rms 40 max 71 freq +5579 +/- 55 delay 8910 +/- 0 ptp4l[26314.347]: port 1 (eth0): delay timeout ptp4l[26314.356]: delay filtered 8918 raw 8929 ptp4l[26314.475]: rms 44 max 70 freq +5582 +/- 61 delay 8918 +/- 0 ptp4l[26315.348]: port 1 (eth0): delay timeout ptp4l[26315.356]: delay filtered 8907 raw 8907 ptp4l[26315.478]: rms 30 max 51 freq +5588 +/- 41 delay 8907 +/- 0 ptp4l[26316.348]: port 1 (eth0): delay timeout ptp4l[26316.356]: delay filtered 8907 raw 8936 ptp4l[26316.481]: rms 37 max 65 freq +5553 +/- 44 delay 8907 +/- 0 ptp4l[26317.348]: port 1 (eth0): delay timeout ptp4l[26317.356]: delay filtered 8905 raw 8904 ptp4l[26317.485]: rms 33 max 59 freq +5619 +/- 31 delay 8905 +/- 0 ptp4l[26318.349]: port 1 (eth0): delay timeout ptp4l[26318.356]: delay filtered 8911 raw 8915 ptp4l[26318.488]: rms 39 max 81 freq +5543 +/- 34 delay 8911 +/- 0 ptp4l[26319.349]: port 1 (eth0): delay timeout ptp4l[26319.360]: delay filtered 8905 raw 8899 ptp4l[26319.492]: rms 27 max 44 freq +5565 +/- 38 delay 8905 +/- 0 ptp4l[26320.349]: port 1 (eth0): delay timeout ptp4l[26320.360]: delay filtered 8905 raw 8875 ptp4l[26320.495]: rms 45 max 69 freq +5592 +/- 59 delay 8905 +/- 0 ptp4l[26321.090]: port 1 (eth0): received link status notification ptp4l[26321.350]: port 1 (eth0): delay timeout ptp4l[26321.356]: delay filtered 8905 raw 8902 ptp4l[26321.499]: rms 50 max 69 freq +5607 +/- 66 delay 8905 +/- 0 ptp4l[26322.350]: port 1 (eth0): delay timeout ptp4l[26322.356]: delay filtered 8903 raw 8888 ptp4l[26322.502]: rms 38 max 65 freq +5609 +/- 50 delay 8903 +/- 0 ptp4l[26323.350]: port 1 (eth0): delay timeout ptp4l[26323.352]: delay filtered 8905 raw 8933 ptp4l[26323.505]: rms 51 max 85 freq +5566 +/- 67 delay 8905 +/- 0 ptp4l[26324.351]: port 1 (eth0): delay timeout ptp4l[26324.356]: delay filtered 8905 raw 8916 ptp4l[26324.509]: rms 48 max 83 freq +5563 +/- 66 delay 8905 +/- 0 ptp4l[26325.351]: port 1 (eth0): delay timeout ptp4l[26325.360]: delay filtered 8909 raw 8984 ptp4l[26325.512]: rms 25 max 35 freq +5566 +/- 35 delay 8909 +/- 0 ptp4l[26326.352]: port 1 (eth0): delay timeout ptp4l[26326.360]: delay filtered 8906 raw 8909 ptp4l[26326.514]: rms 45 max 67 freq +5592 +/- 59 delay 8906 +/- 0 ptp4l[26327.353]: port 1 (eth0): delay timeout ptp4l[26327.354]: delay filtered 8906 raw 8904 ptp4l[26327.517]: rms 20 max 32 freq +5595 +/- 26 delay 8906 +/- 0 ptp4l[26328.353]: port 1 (eth0): delay timeout ptp4l[26328.360]: delay filtered 8906 raw 8920 ptp4l[26328.521]: rms 30 max 69 freq +5584 +/- 41 delay 8906 +/- 0 ptp4l[26329.353]: port 1 (eth0): delay timeout ptp4l[26329.360]: delay filtered 8906 raw 8875 ptp4l[26329.524]: rms 33 max 56 freq +5576 +/- 44 delay 8906 +/- 0 ptp4l[26330.353]: port 1 (eth0): delay timeout ptp4l[26330.360]: delay filtered 8906 raw 8892 ptp4l[26330.529]: rms 42 max 85 freq +5527 +/- 44 delay 8906 +/- 0 ptp4l[26331.354]: port 1 (eth0): delay timeout ptp4l[26331.355]: delay filtered 8906 raw 8875 ptp4l[26331.532]: rms 31 max 56 freq +5554 +/- 42 delay 8906 +/- 0 ptp4l[26332.354]: port 1 (eth0): delay timeout ptp4l[26332.360]: delay filtered 8906 raw 8871 ptp4l[26332.535]: rms 47 max 71 freq +5586 +/- 60 delay 8906 +/- 0 ptp4l[26333.355]: port 1 (eth0): delay timeout ptp4l[26333.364]: delay filtered 8899 raw 8894 ptp4l[26333.540]: rms 24 max 60 freq +5559 +/- 33 delay 8899 +/- 0 ptp4l[26334.041]: PI servo: sync interval 1.000 kp 0.700 ki 0.300000 ptp4l[26334.041]: master offset -53 s2 freq +5515 path delay 8899 ptp4l[26334.356]: port 1 (eth0): delay timeout ptp4l[26334.364]: delay filtered 8899 raw 8952 ptp4l[26335.042]: master offset 49 s2 freq +5602 path delay 8899 ptp4l[26336.042]: master offset -28 s2 freq +5539 path delay 8899 ptp4l[26337.042]: master offset 12 s2 freq +5571 path delay 8899 ptp4l[26338.043]: master offset -5 s2 freq +5557 path delay 8899 ptp4l[26338.356]: port 1 (eth0): delay timeout ptp4l[26338.364]: delay filtered 8899 raw 8949 ptp4l[26339.043]: master offset -13 s2 freq +5548 path delay 8899 ptp4l[26340.044]: master offset -118 s2 freq +5439 path delay 8899 ptp4l[26341.044]: master offset -10 s2 freq +5512 path delay 8899 ptp4l[26342.045]: master offset 40 s2 freq +5559 path delay 8899 ptp4l[26342.357]: port 1 (eth0): delay timeout ptp4l[26342.364]: delay filtered 8899 raw 8928 ptp4l[26343.045]: master offset 17 s2 freq +5548 path delay 8899 ptp4l[26344.046]: master offset -35 s2 freq +5501 path delay 8899 ptp4l[26345.046]: master offset -29 s2 freq +5496 path delay 8899 ptp4l[26346.046]: master offset -127 s2 freq +5390 path delay 8899 ptp4l[26346.358]: port 1 (eth0): delay timeout ptp4l[26346.364]: delay filtered 8893 raw 8849 ptp4l[26347.047]: master offset 49 s2 freq +5527 path delay 8893 ptp4l[26348.047]: master offset -15 s2 freq +5478 path delay 8893 ptp4l[26349.047]: master offset -66 s2 freq +5423 path delay 8893 ptp4l[26350.048]: master offset 48 s2 freq +5517 path delay 8893 ptp4l[26350.359]: port 1 (eth0): delay timeout ptp4l[26350.368]: delay filtered 8893 raw 8932 ptp4l[26351.048]: master offset -94 s2 freq +5389 path delay 8893 ^C-(daniel@daniel-orin1:0)-(298 files:3,9M@linuxptp-latest)-(0 jobs)-(15:23)- -(~/linuxptp-latest:$)-> Right after that try, I restarted Master and Slave and they didn't sync for the whole 5 minutes I waited for. Any suggestions/help would be highly appreciated! BR Daniel Internal |
|
From: Jean-Sebastien S. <js....@gm...> - 2023-11-24 14:56:07
|
Richard: Thank you very much for the reply and information. This is appreciated and helpful. This information narrowed down my field of search and reviewing the code helped answer some further questions I had. Regards, JS On Mon, Nov 20, 2023 at 4:52 PM Richard Cochran <ric...@gm...> wrote: > On Mon, Nov 20, 2023 at 12:54:03PM -0500, Jean-Sebastien Stoezel wrote: > > > When it comes to software timestamping, what is the PHC equivalent on the > > device? Is it a hardware timer? Or is it purely software? ethtool is > > reporting no PHC, and so I'd assume the PHC is some sort of software > timer > > somewhere in the kernel. > > With software timestamping, ptp4l adjusts the Linux system clock > (CLOCK_REALTIME) directly. > > HTH, > Richard > |
|
From: First L. <ssr...@gm...> - 2023-11-23 09:32:23
|
Hello, I have a system that I am using LinuxPTP with to synchronize a very simple network. I am using Intel I210-T1 NICs, and outputting a 1-PPS signal to validate that LinuxPTP is working well. I am trying to compare the offsetFromMaster value in LinuxPTP and the 1-PPS signal, since they both measure Time Error between Master and Slave, just in different ways. In general, I'm seeing the values are relatively close to each other (they have similar amplitudes), but in no way resemble one another. Sometimes, I see offsetFromMaster have a large abnormal jump, which I don't see happening at the PPS signal. I'm wondering why this is. Since I'm using HW Timestamping, the offsetFromMaster calculation should be doing the standard offset calculation based on the HW timestamps taken on the NIC, defined in the spec: ((t2-t1) - (t4-t3)) / 2. And the PPS Signal is asserted once per second based on the clock on the NIC I believe. What would cause discrepancies between the two measurements of Time Error? Thanks. |
|
From: Janusz U. <j.u...@el...> - 2023-11-21 12:38:09
|
Hi, eg. https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list Best regards, Janusz W dniu 21.11.2023 o 06:30, ramesh t via Linuxptp-users pisze: > hello, > > Do we have latest leapsecond file available for use? Current one is expiring on December 28th 2023. > > https://www.ietf.org/timezones/data/leap-seconds.list (not working) > https://data.iana.org/time-zones/tzdb/leapseconds (File expires on: 28 December 2023) > > Please suggest. > > regards, > Ramesh > > > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
|
From: ramesh t <ram...@ya...> - 2023-11-21 11:07:23
|
Thanks George Hansel. On Tuesday, November 21, 2023 at 11:55:13 AM GMT+5:30, George Hansel <geo...@gm...> wrote: IERS is the leap second authority: https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list On Mon, Nov 20, 2023 at 9:34 PM ramesh t via Linuxptp-users <lin...@li...> wrote: > hello, > > Do we have latest leapsecond file available for use? Current one is expiring on December 28th 2023. > > https://www.ietf.org/timezones/data/leap-seconds.list (not working) > https://data.iana.org/time-zones/tzdb/leapseconds (File expires on: 28 December 2023) > > Please suggest. > > regards, > Ramesh > > > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users > |
|
From: George H. <geo...@gm...> - 2023-11-21 06:25:21
|
IERS is the leap second authority: https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list On Mon, Nov 20, 2023 at 9:34 PM ramesh t via Linuxptp-users < lin...@li...> wrote: > hello, > > Do we have latest leapsecond file available for use? Current one is > expiring on December 28th 2023. > > https://www.ietf.org/timezones/data/leap-seconds.list (not working) > https://data.iana.org/time-zones/tzdb/leapseconds (File expires on: 28 > December 2023) > > Please suggest. > > regards, > Ramesh > > > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users > |
|
From: ramesh t <ram...@ya...> - 2023-11-21 05:31:03
|
hello, Do we have latest leapsecond file available for use? Current one is expiring on December 28th 2023. https://www.ietf.org/timezones/data/leap-seconds.list (not working) https://data.iana.org/time-zones/tzdb/leapseconds (File expires on: 28 December 2023) Please suggest. regards, Ramesh |
|
From: Richard C. <ric...@gm...> - 2023-11-20 21:52:20
|
On Mon, Nov 20, 2023 at 12:54:03PM -0500, Jean-Sebastien Stoezel wrote: > When it comes to software timestamping, what is the PHC equivalent on the > device? Is it a hardware timer? Or is it purely software? ethtool is > reporting no PHC, and so I'd assume the PHC is some sort of software timer > somewhere in the kernel. With software timestamping, ptp4l adjusts the Linux system clock (CLOCK_REALTIME) directly. HTH, Richard |
|
From: Jean-Sebastien S. <js....@gm...> - 2023-11-20 17:54:22
|
Hello, I am running linuxPTP 1.8 on a 4.14.0-xilinx device. This device only has software timestamping made available. *root@Megalive:~# ethtool -T eth0Time stamping parameters for eth0:Capabilities: software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE) software-receive (SOF_TIMESTAMPING_RX_SOFTWARE) software-system-clock (SOF_TIMESTAMPING_SOFTWARE)PTP Hardware Clock: noneHardware Transmit Timestamp Modes: noneHardware Receive Filter* I'm able to synchronize this device running as a TimeReceiver, to a TimeSender, at least reportedly. ptp4l will report that the servo S2 state is reached and stable, with a reported offset to the TimeSender in the 1us range (with occasional jumps to double digit offsets). I am ok with this offset jitter, provided it is reported in an accurate way. When it comes to software timestamping, what is the PHC equivalent on the device? Is it a hardware timer? Or is it purely software? ethtool is reporting no PHC, and so I'd assume the PHC is some sort of software timer somewhere in the kernel. Can a virtual PPS be generated from this virtual PHC, in the form of an event potentially? How would you handle this event? Regards, JS |
|
From: Osterried M. (ETAS-DAP/XPC-Fe3) <mar...@et...> - 2023-11-20 12:55:28
|
Hi Vladimir, I had a look at the clock distribution internal and external of SoC, as far as understood, both PHCs use clocks which are phase locked to each other. Also run a test for several days, repeatedly sampled the PHCs and it shows they are in sync, without the need to re-sync. In current development phase, just to evaluate the options, we have direct register access from user space, not changed the ocelot ptp driver. Thanks for your info, which helped a lot. > Hi Vladimir, > > thanks for your answer. > > We do not have a connection between EC1_1588_PULSE_OUT1 and SWITCH_1588_DAT0 on our board, so this option is not possible for us. > > But we use this trigger signal, which actually is EC1_1588_TRIG_IN1 and SWITCH_1588_DAT1. Both pins are connected together to a GPIO pin. > In ES_DEVCPU_PTP_PTP_PINS_PTP_PIN_CFG register, SWITCH_1588_DAT1 is configured for STORE action. > Generating an edge on these trigger signals is latching a timestamp of the ENETC (aka /dev/ptp0) and SWITCH (aka /dev/ptp1). > As the input clocks of ENETC and SWITCH is derived from the same clock source, the PHCs always run at the same speed (with period configured in ENETC TMR_CTRL and ES_DEVCPU_PTP_PTP_CFG_PTP_SYS_CLK_CFG). Have you studied the clock distribution trees for the ENETC and the Felix switch IPs before drawing the conclusion that their input clocks are derived from the same source? As far as I see, ENETC, through HWA_CGA_M4_CLK_SEL, uses Cluster Group A PLL 2 divided by 3 as clock (400 MHz), whereas Felix has its sys_clk at 156.25 MHz and it comes from one of the SerDes PLLs, depending on the particular RCW configuration. > When latching the timestamps of ENETC and SWITCH, we can calculate the offset between them, which in turn we use to clock_adjtime(ADJ_SETOFFSET|ADJ_NANO) one PHC to the other. > Doing this in the startup phase, we can guarantee that /dev/ptp0 and /dev/ptp1 is synchronized, but yes, PHC subsystem does not know that they are now actually equivalent. Aha, so you've implemented the extts API in the ocelot ptp driver? Do you plan to upstream that work? A pulse output from the ENETC PHC which is an input to the Felix PHC is not strictly necessary. Your way should be just fine - a GPIO output which is input both to ENETC and to Felix is equally fine, and ts2phc should be able to work with that. I guess you're looking at a "generic" source of 1-PPS signal, when you open up the ts2phc manual. > When later ptp4l wants to adjust the PHC according to an external PTP master, it will do this only on one of the two PHCs, therefore they will be no longer in sync. This is a similar reason to the one for which I modified ts2phc to monitor the direction of ptp4l's synchronization dynamically. If the slave port of the ptp4l BC is an ENETC port, then the Felix PHC gets synchronized to the ENETC PHC, otherwise the ENETC PHC gets synchronized to the Felix PHC. https://sourceforge.net/p/linuxptp/mailman/linuxptp-devel/thread/20200830234525.3311891-11-olteanv%40gmail.com/ I've only tried it with the "PHC" kind of sources of 1-PPS signals. If it doesn't work with a "generic" source, it probably isn't too hard to modify ts2phc to treat that case reasonably. > To avoid this, the idea was to create a vclock /dev/ptp2 based on /dev/ptp0. And to let /dev/ptp0 and /dev/ptp1 free running and in sync. > But because PHC subsystem does not know that /dev/ptp0 and /dev/ptp1 is actually equivalent, it forbids to bind /dev/ptp2 to the socket of swpX. It's not that the PHC subsystem doesn't know that /dev/ptp0 and /dev/ptp1 are "actually equivalent". They _aren't_ actually equivalent. They are completely independent clocks, independently adjustable. Synchronized once and then left alone, I don't see what will prevent them from starting to drift. The sync process needs to be continuous, like for any other independent hardware clocks. That, plus the fact that vclocks don't do what you think they do. Even if there were 2 PTP clocks which could be proven to be equivalent, a vclock only has a single PTP clock as parent, not 2. > If I understand your suggested options correctly, the ptp4l instance which handles the external front-facing interfaces, will just adjust one physical PHC, while the other PHC is re-adjusted by either internal ptp4l instance or ts2phc, but of course within some latency. Is this correct? Yes. > Back to our original problem: > We want to use ptp4l between all front-facing ports, while physical PHCs of eno0-eno3 and swp0-swp5 are already in sync - known by us, but not known by PHC subsystem. > For this, you have mentioned boundary_clock_jbod can be used. > I do not know what boundary_clock_jbod is doing in detail and if and how this could be used to provide a solution in this use case. > Could you please explain. man ptp4l boundary_clock_jbod When running as a boundary clock (that is, when more than one network interface is configured), ptp4l performs a sanity check to make sure that all of the ports share the same hardware clock device. This option allows ptp4l to work as a boundary clock using "just a bunch of devices" that are not synchronized to each other. For this mode, the collection of clocks must be synchronized by an external program, for example phc2sys(8) in "automatic" mode. The default is 0 (disabled). "physical PHCs of eno0-eno3 and swp0-swp5 are already in sync - known by us, but not known by PHC subsystem" -> TL;DR: this option tells ptp4l "trust me, the clocks are in sync, within an unknown tolerance, despite being different, you can make a boundary clock out of these ports". They'd better be in robust sync, though, because ptp4l can make an attempt to adjust any of those PHCs. |
|
From: Andre P. <and...@sr...> - 2023-11-20 12:49:39
|
Hi, I've tried three different ConnectX-3 NICs now and they all behave the same. To rule out any issues with the GM I tried a Intel i210 as well and that is spot on with excellent sync. However, the Mellanox is not. It's almost as if there is a frequency correction happening inside the NIC every so often. Then the rms values are bad out of a sudden, getting better as frequency is adjusted to the GM and then, again, really bad. ptp4l[447.094]: rms 1580 max 6078 freq +1598846 +/- 4029 delay 983 +/- 3 ptp4l[448.091]: rms 1608 max 6080 freq +1598430 +/- 4117 delay 971 +/- 2 ptp4l[449.089]: rms 111 max 244 freq +1598218 +/- 180 delay 977 +/- 2 ptp4l[450.086]: rms 25 max 39 freq +1598474 +/- 23 delay 983 +/- 2 ptp4l[451.084]: rms 30 max 57 freq +1598512 +/- 23 delay 984 +/- 1 ptp4l[452.081]: rms 17 max 28 freq +1598504 +/- 14 delay 984 +/- 1 ptp4l[453.078]: rms 13 max 24 freq +1598507 +/- 15 delay 985 +/- 2 ptp4l[454.076]: rms 14 max 43 freq +1598510 +/- 26 delay 984 +/- 1 ptp4l[455.073]: rms 7 max 16 freq +1598506 +/- 12 delay 985 +/- 1 ptp4l[456.071]: rms 11 max 18 freq +1598525 +/- 13 delay 983 +/- 1 ptp4l[457.068]: rms 7 max 15 freq +1598519 +/- 14 delay 983 +/- 1 ptp4l[458.066]: rms 6 max 14 freq +1598514 +/- 14 delay 984 +/- 1 ptp4l[459.063]: rms 6 max 13 freq +1598519 +/- 14 delay 985 +/- 0 ptp4l[460.061]: rms 1563 max 5997 freq +1598869 +/- 3991 delay 982 +/- 3 Thanks Andre On 20/11/23 10:27, Andre Puschmann wrote: > Hey, > > > How the GM side is configured? Are you writing system time to PHC > > every second? If so, you can try make the phc free run. Without 1PPS > > signal connecting to the phc or PTM enabled, it's not recommended to > > set pmc's time by software, the jitter is quite big. > > I am not writing any time to the PHC. I just start ptp4l. Shouldn't that > be enough to adjust to PHC to the GMs? > > > Is the GM and the client connected directly or through a switch? Try > > connect them directly with an utp or fiber. > > The GM is directly connected to port0 of the NIC. And the GM is GPS synced. > > > > Try the L2 transport. IIRC at least some Mellanox NICs performed > > worse with UDP transport for some reason. > > This is already with L2. > > > Meanwhile I tried with yet another ConnectX-3 card. This time a IBM > branded with FW 2.42.5032 but the results are similar. One new thing > I've observed is this: > > ptp4l[226.813]: rms 69 max 164 freq +1593151 +/- 131 delay 972 +/- 3 > ptp4l[227.811]: rms 31 max 40 freq +1593342 +/- 23 delay 977 +/- 1 > ptp4l[228.810]: rms 1607 max 6189 freq +1593762 +/- 4095 delay 979 > +/- 2 > ptp4l[229.816]: rms 23001617550970840 max 65058399023124016 freq > -11106166 +/- 33598711 delay 970 +/- 4 > ptp4l[230.695]: clockcheck: clock jumped backward or running slower than > expected! > ptp4l[230.695]: port 1 (enp1s0): SLAVE to UNCALIBRATED on > SYNCHRONIZATION_FAULT > ptp4l[230.821]: rms 65058399528662992 max 65058399969385488 freq > -100000000 +/- 0 delay 9404287 +/- 6628445 > ptp4l[231.825]: rms 65058400466045568 max 65058400899446072 freq > -100000000 +/- 0 delay 15392460 +/- 2718826 > ptp4l[232.828]: rms 65058401394850600 max 65058401833399432 freq > -100000000 +/- 0 delay 12181777 +/- 2190097 > ptp4l[233.831]: rms 65058402330812608 max 65058402771727544 freq > -100000000 +/- 0 delay 16575665 +/- 1701941 > > > RMS values were like before, but than suddenly increased and now don't > go back. > > Thanks > Andre > > > On 19/11/23 22:07, Andre Puschmann wrote: >> Hey, >> >> I've been able to get my hands on a ConnectX-3 Pro card and have done >> some initial testing. The card indeed has a shared PHC for both ports >> so running ptp4l as BC or TC does indeed work without the jbod option. >> >> However, sync performance (i.e. rms values) for the downstream OCs >> isn't great. And in fact, even the Mellanox as a OC isn't giving great >> results - rms values jump a lot (and I've tried various PI value >> combinations). >> >> Is anyone else seeing this with Mlx cards as well? Could it be my >> model or the firmware? >> >> Here is the output of a OC config with the card: >> >> $ sudo /opt/linuxptp/ptp4l -i enp1s0 -f ~/configs/ptp/oc.cfg -m -l6 >> ptp4l[12737.960]: selected /dev/ptp0 as PTP clock >> ptp4l[12738.012]: port 1 (enp1s0): INITIALIZING to LISTENING on >> INIT_COMPLETE >> ptp4l[12738.012]: port 0 (/var/run/ptp4l): INITIALIZING to LISTENING >> on INIT_COMPLETE >> ptp4l[12738.012]: port 0 (/var/run/ptp4lro): INITIALIZING to LISTENING >> on INIT_COMPLETE >> ptp4l[12738.060]: port 1 (enp1s0): new foreign master >> fcaf6a.fffe.02b447-1 >> ptp4l[12738.314]: selected best master clock fcaf6a.fffe.02b447 >> ptp4l[12738.314]: port 1 (enp1s0): LISTENING to UNCALIBRATED on RS_SLAVE >> ptp4l[12740.148]: port 1 (enp1s0): minimum delay request interval 2^-4 >> ptp4l[12740.512]: port 1 (enp1s0): UNCALIBRATED to SLAVE on >> MASTER_CLOCK_SELECTED >> ptp4l[12741.138]: rms 1450 max 1934 freq +270168 +/- 1641 delay 951 >> +/- 14 >> ptp4l[12742.139]: rms 129 max 179 freq +268843 +/- 296 delay 963 >> +/- 11 >> ptp4l[12743.140]: rms 241 max 490 freq +268455 +/- 452 delay 948 >> +/- 1 >> ptp4l[12744.141]: rms 135 max 180 freq +268381 +/- 25 delay 947 >> +/- 1 >> ptp4l[12745.142]: rms 1357 max 5277 freq +269064 +/- 3459 delay 950 >> +/- 1 >> ptp4l[12746.143]: rms 1397 max 5092 freq +268197 +/- 3539 delay 935 >> +/- 7 >> ptp4l[12747.144]: rms 210 max 417 freq +268048 +/- 243 delay 942 >> +/- 3 >> ptp4l[12748.145]: rms 15 max 32 freq +268415 +/- 29 delay 947 >> +/- 2 >> ptp4l[12749.146]: rms 1430 max 5594 freq +269126 +/- 3617 delay 950 >> +/- 1 >> ptp4l[12750.147]: rms 1391 max 5162 freq +268252 +/- 3543 delay 942 >> +/- 4 >> >> >> Thanks >> Andre >> >> >> >> >> >> On 2/11/23 17:37, Jacob Keller wrote: >>> >>> >>> On 11/2/2023 4:15 AM, Andre Puschmann wrote: >>>> Hi, >>>> >>>> On 2/11/23 4:11, James Clark wrote: >>>>> I have a dual-port Mellanox ConnectX-3 (specifically MCX312A-XCBT), >>>>> which has a shared PHC. You can get them for less than $50 on >>>>> eBay/AliExpress. I had to upgrade the firmware on mine to get PTP >>>>> support. I haven't yet tried it as a boundary clock. >>>> >>>> Excellent. This is very helpful James. I've ordered a MCX312A and B and >>>> will compare both here. I'll share my results here soon. If you have a >>>> chance please also share the firmware version you're currently using on >>>> your NIC. >>>> >>>> With my Intel NIC I could get the BC config working but I needed to set >>>> the twoStepFlag to 1. Otherwise I was getting this for both ports: >>>> >>>> ptp4l[1040.180]: ioctl SIOCSHWTSTAMP failed: Numerical result out of >>>> range >>>> >>> >>> Yep, that would indicate the device doesn't support one-step mode. >>> >>>> Sync quality wasn't great as expected though. I'll repeat with the >>>> Mellanox once I have them here. >>>> >>>> Thanks >>>> Andre >>>> >>> >>> For Intel NICs, the only products I am aware of which share PHC across >>> the device are the E800 series devices. Prior devices (E500, and E700, >>> as well as the gigabit products) do share the same internal oscillator >>> but due to the register interface each function has to setup its own >>> clock. >>> >>> Thanks, >>> Jake >>> >>> >>> _______________________________________________ >>> Linuxptp-users mailing list >>> Lin...@li... >>> https://lists.sourceforge.net/lists/listinfo/linuxptp-users >> > -- Andre Puschmann Software Radio Systems (SRS) https://www.srs.io an...@sr... PGP/GnuPG key: 0x204A85DFEA324D58 fingerprint: 3924 1C60 D52E 81A2 1F2E 0C9D 204A 85DF EA32 4D58 |
|
From: Andre P. <and...@sr...> - 2023-11-20 09:27:44
|
Hey, > How the GM side is configured? Are you writing system time to PHC > every second? If so, you can try make the phc free run. Without 1PPS > signal connecting to the phc or PTM enabled, it's not recommended to > set pmc's time by software, the jitter is quite big. I am not writing any time to the PHC. I just start ptp4l. Shouldn't that be enough to adjust to PHC to the GMs? > Is the GM and the client connected directly or through a switch? Try > connect them directly with an utp or fiber. The GM is directly connected to port0 of the NIC. And the GM is GPS synced. > Try the L2 transport. IIRC at least some Mellanox NICs performed > worse with UDP transport for some reason. This is already with L2. Meanwhile I tried with yet another ConnectX-3 card. This time a IBM branded with FW 2.42.5032 but the results are similar. One new thing I've observed is this: ptp4l[226.813]: rms 69 max 164 freq +1593151 +/- 131 delay 972 +/- 3 ptp4l[227.811]: rms 31 max 40 freq +1593342 +/- 23 delay 977 +/- 1 ptp4l[228.810]: rms 1607 max 6189 freq +1593762 +/- 4095 delay 979 +/- 2 ptp4l[229.816]: rms 23001617550970840 max 65058399023124016 freq -11106166 +/- 33598711 delay 970 +/- 4 ptp4l[230.695]: clockcheck: clock jumped backward or running slower than expected! ptp4l[230.695]: port 1 (enp1s0): SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT ptp4l[230.821]: rms 65058399528662992 max 65058399969385488 freq -100000000 +/- 0 delay 9404287 +/- 6628445 ptp4l[231.825]: rms 65058400466045568 max 65058400899446072 freq -100000000 +/- 0 delay 15392460 +/- 2718826 ptp4l[232.828]: rms 65058401394850600 max 65058401833399432 freq -100000000 +/- 0 delay 12181777 +/- 2190097 ptp4l[233.831]: rms 65058402330812608 max 65058402771727544 freq -100000000 +/- 0 delay 16575665 +/- 1701941 RMS values were like before, but than suddenly increased and now don't go back. Thanks Andre On 19/11/23 22:07, Andre Puschmann wrote: > Hey, > > I've been able to get my hands on a ConnectX-3 Pro card and have done > some initial testing. The card indeed has a shared PHC for both ports so > running ptp4l as BC or TC does indeed work without the jbod option. > > However, sync performance (i.e. rms values) for the downstream OCs isn't > great. And in fact, even the Mellanox as a OC isn't giving great results > - rms values jump a lot (and I've tried various PI value combinations). > > Is anyone else seeing this with Mlx cards as well? Could it be my model > or the firmware? > > Here is the output of a OC config with the card: > > $ sudo /opt/linuxptp/ptp4l -i enp1s0 -f ~/configs/ptp/oc.cfg -m -l6 > ptp4l[12737.960]: selected /dev/ptp0 as PTP clock > ptp4l[12738.012]: port 1 (enp1s0): INITIALIZING to LISTENING on > INIT_COMPLETE > ptp4l[12738.012]: port 0 (/var/run/ptp4l): INITIALIZING to LISTENING on > INIT_COMPLETE > ptp4l[12738.012]: port 0 (/var/run/ptp4lro): INITIALIZING to LISTENING > on INIT_COMPLETE > ptp4l[12738.060]: port 1 (enp1s0): new foreign master fcaf6a.fffe.02b447-1 > ptp4l[12738.314]: selected best master clock fcaf6a.fffe.02b447 > ptp4l[12738.314]: port 1 (enp1s0): LISTENING to UNCALIBRATED on RS_SLAVE > ptp4l[12740.148]: port 1 (enp1s0): minimum delay request interval 2^-4 > ptp4l[12740.512]: port 1 (enp1s0): UNCALIBRATED to SLAVE on > MASTER_CLOCK_SELECTED > ptp4l[12741.138]: rms 1450 max 1934 freq +270168 +/- 1641 delay 951 > +/- 14 > ptp4l[12742.139]: rms 129 max 179 freq +268843 +/- 296 delay 963 > +/- 11 > ptp4l[12743.140]: rms 241 max 490 freq +268455 +/- 452 delay 948 > +/- 1 > ptp4l[12744.141]: rms 135 max 180 freq +268381 +/- 25 delay 947 > +/- 1 > ptp4l[12745.142]: rms 1357 max 5277 freq +269064 +/- 3459 delay 950 > +/- 1 > ptp4l[12746.143]: rms 1397 max 5092 freq +268197 +/- 3539 delay 935 > +/- 7 > ptp4l[12747.144]: rms 210 max 417 freq +268048 +/- 243 delay 942 > +/- 3 > ptp4l[12748.145]: rms 15 max 32 freq +268415 +/- 29 delay 947 > +/- 2 > ptp4l[12749.146]: rms 1430 max 5594 freq +269126 +/- 3617 delay 950 > +/- 1 > ptp4l[12750.147]: rms 1391 max 5162 freq +268252 +/- 3543 delay 942 > +/- 4 > > > Thanks > Andre > > > > > > On 2/11/23 17:37, Jacob Keller wrote: >> >> >> On 11/2/2023 4:15 AM, Andre Puschmann wrote: >>> Hi, >>> >>> On 2/11/23 4:11, James Clark wrote: >>>> I have a dual-port Mellanox ConnectX-3 (specifically MCX312A-XCBT), >>>> which has a shared PHC. You can get them for less than $50 on >>>> eBay/AliExpress. I had to upgrade the firmware on mine to get PTP >>>> support. I haven't yet tried it as a boundary clock. >>> >>> Excellent. This is very helpful James. I've ordered a MCX312A and B and >>> will compare both here. I'll share my results here soon. If you have a >>> chance please also share the firmware version you're currently using on >>> your NIC. >>> >>> With my Intel NIC I could get the BC config working but I needed to set >>> the twoStepFlag to 1. Otherwise I was getting this for both ports: >>> >>> ptp4l[1040.180]: ioctl SIOCSHWTSTAMP failed: Numerical result out of >>> range >>> >> >> Yep, that would indicate the device doesn't support one-step mode. >> >>> Sync quality wasn't great as expected though. I'll repeat with the >>> Mellanox once I have them here. >>> >>> Thanks >>> Andre >>> >> >> For Intel NICs, the only products I am aware of which share PHC across >> the device are the E800 series devices. Prior devices (E500, and E700, >> as well as the gigabit products) do share the same internal oscillator >> but due to the register interface each function has to setup its own >> clock. >> >> Thanks, >> Jake >> >> >> _______________________________________________ >> Linuxptp-users mailing list >> Lin...@li... >> https://lists.sourceforge.net/lists/listinfo/linuxptp-users > -- Andre Puschmann Software Radio Systems (SRS) https://www.srs.io an...@sr... PGP/GnuPG key: 0x204A85DFEA324D58 fingerprint: 3924 1C60 D52E 81A2 1F2E 0C9D 204A 85DF EA32 4D58 |
27 messages has been excluded from this view by a project administrator.
