linuxptp-users Mailing List for linuxptp (Page 9)
PTP IEEE 1588 stack for Linux
Brought to you by:
rcochran
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-05-12 00:43:20
|
On Thu, May 11, 2023 at 01:01:54PM -0300, Elder Costa wrote: > The master offset increases, non monotonically but with a very definite > trend, whether with or without the step_threshold parameter. > What am I missing? Maybe you have ntpd or systemd timesync or chrony running on the client and/or the server? IIRC Ubuntu enables systemd thing by default, and it is hard to get rid of. Thanks, Richard |
|
From: Elder C. <eld...@ti...> - 2023-05-11 16:02:10
|
I had already notice this while trying to solve the clock sync issue of the other thread. Test setup is two Fitlet PCs, connected point-to-point. The master offset increases, non monotonically but with a very definite trend, whether with or without the step_threshold parameter. $ uname -srvm Linux 5.15.0-70-generic #77~20.04.1-Ubuntu SMP Wed Apr 5 09:38:34 UTC 2023 x86_64 $ ptp4l -v 3.1-00246-g5498f74 What am I missing? $ sudo ptp4l -S -m -q --clientOnly=1 --step_threshold=0.01 -i enp3s0 ptp4l[17804.187]: port 1 (enp3s0): INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[17804.188]: port 0 (/var/run/ptp4l): INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[17804.188]: port 0 (/var/run/ptp4lro): INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[17805.578]: port 1 (enp3s0): new foreign master 0001c0.fffe.1a3e8e-1 ptp4l[17809.579]: selected best master clock 0001c0.fffe.1a3e8e ptp4l[17809.579]: foreign master not using PTP timescale ptp4l[17809.579]: port 1 (enp3s0): LISTENING to UNCALIBRATED on RS_SLAVE ptp4l[17810.584]: master offset 159453 s0 freq +100000000 path delay 216530 ptp4l[17811.584]: master offset 204915 s0 freq +100000000 path delay 216530 ptp4l[17812.585]: master offset 253667 s0 freq +100000000 path delay 210875 ptp4l[17813.585]: master offset 216052 s0 freq +100000000 path delay 222827 ptp4l[17814.585]: master offset 218133 s0 freq +100000000 path delay 222827 ptp4l[17815.585]: master offset 238977 s0 freq +100000000 path delay 218369 ptp4l[17816.585]: master offset 243903 s0 freq +100000000 path delay 218369 ptp4l[17817.585]: master offset 161090 s0 freq +100000000 path delay 218369 ptp4l[17818.585]: master offset 243281 s0 freq +100000000 path delay 218369 ptp4l[17819.585]: master offset 252487 s0 freq +100000000 path delay 218369 ptp4l[17820.585]: master offset 243551 s0 freq +100000000 path delay 215088 ptp4l[17821.586]: master offset 253522 s0 freq +100000000 path delay 216985 ptp4l[17822.586]: master offset 254771 s0 freq +100000000 path delay 216985 ptp4l[17823.586]: master offset 236767 s0 freq +100000000 path delay 216985 ptp4l[17824.586]: master offset 260883 s0 freq +100000000 path delay 215088 ptp4l[17825.586]: master offset 231376 s0 freq +100000000 path delay 215088 ptp4l[17826.586]: master offset 279783 s1 freq +100000000 path delay 208463 ptp4l[17827.586]: master offset -4948 s2 freq +99999500 path delay 208463 ptp4l[17827.586]: port 1 (enp3s0): UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED ptp4l[17828.586]: master offset -26034 s2 freq +99997366 path delay 208463 ptp4l[17829.586]: master offset 9262 s2 freq +100000000 path delay 196545 ptp4l[17830.587]: master offset -64129 s2 freq +99993492 path delay 196545 ptp4l[17831.587]: master offset 8086 s2 freq +100000000 path delay 180968 ptp4l[17832.587]: master offset 19802 s2 freq +100000000 path delay 180968 ptp4l[17833.587]: master offset 25994 s2 freq +100000000 path delay 196545 ptp4l[17834.587]: master offset 33958 s2 freq +100000000 path delay 180968 ptp4l[17835.587]: master offset -43154 s2 freq +99995546 path delay 187560 ptp4l[17836.587]: master offset 24553 s2 freq +100000000 path delay 187560 ptp4l[17837.587]: master offset 22863 s2 freq +100000000 path delay 209257 ptp4l[17838.588]: master offset -6513 s2 freq +99999204 path delay 214778 ptp4l[17839.588]: master offset 25468 s2 freq +100000000 path delay 212728 ptp4l[17840.588]: master offset 31602 s2 freq +100000000 path delay 206895 ptp4l[17841.588]: master offset 31784 s2 freq +100000000 path delay 206895 ptp4l[17842.588]: master offset 14909 s2 freq +100000000 path delay 211621 ptp4l[17843.588]: master offset 25457 s2 freq +100000000 path delay 211621 ptp4l[17844.588]: master offset 5632 s2 freq +100000000 path delay 211621 ptp4l[17845.589]: master offset 43463 s2 freq +100000000 path delay 208242 ptp4l[17846.589]: master offset 42612 s2 freq +100000000 path delay 208242 ptp4l[17847.589]: master offset 22200 s2 freq +100000000 path delay 211621 ptp4l[17848.589]: master offset 26093 s2 freq +100000000 path delay 211507 ptp4l[17849.589]: master offset -67089 s2 freq +99993079 path delay 211507 ptp4l[17850.589]: master offset 18941 s2 freq +100000000 path delay 211507 ptp4l[17851.589]: master offset 53578 s2 freq +100000000 path delay 211507 ptp4l[17852.589]: master offset 41217 s2 freq +100000000 path delay 212352 ptp4l[17853.589]: master offset -29075 s2 freq +99996852 path delay 212352 ptp4l[17854.590]: master offset 63911 s2 freq +100000000 path delay 212352 ptp4l[17855.590]: master offset 48070 s2 freq +100000000 path delay 213941 ptp4l[17856.590]: master offset -15308 s2 freq +99998213 path delay 211507 ptp4l[17857.590]: master offset 52932 s2 freq +100000000 path delay 211507 ptp4l[17858.590]: master offset 72178 s2 freq +100000000 path delay 210398 ptp4l[17859.590]: master offset -25048 s2 freq +99997214 path delay 211507 ptp4l[17860.590]: master offset 59028 s2 freq +100000000 path delay 210398 ptp4l[17861.591]: master offset 83153 s2 freq +100000000 path delay 210398 ptp4l[17862.591]: master offset -15561 s2 freq +99998147 path delay 209111 ptp4l[17863.591]: master offset 87904 s2 freq +100000000 path delay 206645 ptp4l[17864.591]: master offset 14074 s2 freq +100000000 path delay 206645 ptp4l[17865.591]: master offset 110231 s2 freq +100000000 path delay 194703 ptp4l[17866.591]: master offset 23757 s2 freq +100000000 path delay 194703 ptp4l[17867.591]: master offset 20245 s2 freq +100000000 path delay 179716 ptp4l[17868.591]: master offset 18863 s2 freq +100000000 path delay 179716 ptp4l[17869.591]: master offset 95764 s2 freq +100000000 path delay 174219 ptp4l[17870.591]: master offset 49927 s2 freq +100000000 path delay 174219 ptp4l[17871.592]: master offset 140161 s2 freq +100000000 path delay 172870 ptp4l[17872.592]: master offset 26294 s2 freq +100000000 path delay 174498 ptp4l[17873.592]: master offset 34713 s2 freq +100000000 path delay 172870 ptp4l[17874.592]: master offset 24618 s2 freq +100000000 path delay 172870 ptp4l[17875.592]: master offset 152488 s2 freq +100000000 path delay 171713 ptp4l[17876.592]: master offset 32740 s2 freq +100000000 path delay 174498 ptp4l[17877.592]: master offset 118871 s2 freq +100000000 path delay 171713 ptp4l[17878.592]: master offset 160898 s2 freq +100000000 path delay 170332 ptp4l[17879.593]: master offset 157665 s2 freq +100000000 path delay 171767 ptp4l[17880.593]: master offset 19963 s2 freq +100000000 path delay 217720 ptp4l[17881.593]: master offset 93649 s2 freq +100000000 path delay 217720 ptp4l[17882.593]: master offset 108074 s2 freq +100000000 path delay 220966 ptp4l[17883.593]: master offset 87514 s2 freq +100000000 path delay 220966 ptp4l[17884.593]: master offset 77271 s2 freq +100000000 path delay 215470 ptp4l[17885.593]: master offset 114914 s2 freq +100000000 path delay 215470 ptp4l[17886.593]: master offset 98124 s2 freq +100000000 path delay 215470 ptp4l[17887.593]: master offset 129160 s2 freq +100000000 path delay 215470 ptp4l[17888.594]: master offset 100582 s2 freq +100000000 path delay 215470 ptp4l[17889.594]: master offset 125095 s2 freq +100000000 path delay 215110 ptp4l[17890.594]: master offset 124738 s2 freq +100000000 path delay 215110 ptp4l[17891.594]: master offset 106051 s2 freq +100000000 path delay 215500 ptp4l[17892.594]: master offset 126470 s2 freq +100000000 path delay 215500 ptp4l[17893.594]: master offset 131971 s2 freq +100000000 path delay 215500 ptp4l[17894.594]: master offset 48569 s2 freq +100000000 path delay 215500 ptp4l[17895.594]: master offset 134499 s2 freq +100000000 path delay 215500 ptp4l[17896.595]: master offset 134927 s2 freq +100000000 path delay 215771 ptp4l[17897.595]: master offset 57682 s2 freq +100000000 path delay 219586 ptp4l[17898.595]: master offset 137885 s2 freq +100000000 path delay 214427 ptp4l[17899.595]: master offset 141448 s2 freq +100000000 path delay 213856 ptp4l[17900.595]: master offset 157021 s2 freq +100000000 path delay 208183 ptp4l[17901.595]: master offset 127072 s2 freq +100000000 path delay 212943 ptp4l[17902.595]: master offset 153837 s2 freq +100000000 path delay 206355 ptp4l[17903.595]: master offset 86728 s2 freq +100000000 path delay 212943 ptp4l[17904.595]: master offset 53300 s2 freq +100000000 path delay 197715 ... ptp4l[18856.714]: master offset 1642006 s2 freq +100000000 path delay 210466 ptp4l[18857.714]: master offset 1638704 s2 freq +100000000 path delay 210466 ptp4l[18858.714]: master offset 1562520 s2 freq +100000000 path delay 209583 ptp4l[18859.715]: master offset 1658159 s2 freq +100000000 path delay 205885 ptp4l[18860.715]: master offset 1658522 s2 freq +100000000 path delay 196826 ptp4l[18861.715]: master offset 1548773 s2 freq +100000000 path delay 196826 ptp4l[18862.715]: master offset 1661950 s2 freq +100000000 path delay 185949 ptp4l[18863.715]: master offset 1671314 s2 freq +100000000 path delay 185949 ptp4l[18864.715]: master offset 1674822 s2 freq +100000000 path delay 185949 ptp4l[18865.715]: master offset 1596681 s2 freq +100000000 path delay 185949 ptp4l[18866.716]: master offset 1666690 s2 freq +100000000 path delay 185949 ptp4l[18867.716]: master offset 1670159 s2 freq +100000000 path delay 185949 ptp4l[18868.716]: master offset 1649541 s2 freq +100000000 path delay 196826 ptp4l[18869.716]: master offset 1558798 s2 freq +100000000 path delay 196826 ptp4l[18870.716]: master offset 1688908 s2 freq +100000000 path delay 185949 ptp4l[18871.716]: master offset 1666295 s2 freq +100000000 path delay 185949 ptp4l[18872.716]: master offset 1668525 s2 freq +100000000 path delay 185635 ptp4l[18873.717]: master offset 1673801 s2 freq +100000000 path delay 200040 |
|
From: Elder C. <eld...@ti...> - 2023-05-11 13:48:55
|
Hello, Miroslav, thank you very much. It worked. I stopped using the "--" because some options generated an error. For example: cve@cve-sbc-flt2:~/work/linuxptp-3.1.1$ sudo ptp4l -4 -S -m -q --clientOnly=1 --step_threshold=0.001 -i enp3s0 ptp4l: unrecognized option '--clientOnly=1' As ptp4l did not complain about the lack of --, I assumed (wrongly) it was all OK. I just learned it has been corrected in the latest version cloned from git so I will use it for further tests. Once again, thank you very much. Em qui., 11 de mai. de 2023 às 09:26, Miroslav Lichvar <mli...@re...> escreveu: > > On Thu, May 11, 2023 at 08:45:02AM -0300, Elder Costa wrote: > > Hello, Richard, thank you for the explanation. It confirms my initial > > understanding of the > > parameter. But I must be doing something wrong as I am not getting > > this clock step. > > > cve@cve-sbc-flt2:~$ sudo ptp4l -4 -S -s -m -q step_threshold=0.001 -i enp3s0 > > step_threshold is an option. If specified on command line, it needs to > have the "--" prefix: --step_threshold=0.001 > > -- > Miroslav Lichvar > |
|
From: Miroslav L. <mli...@re...> - 2023-05-11 12:26:16
|
On Thu, May 11, 2023 at 08:45:02AM -0300, Elder Costa wrote: > Hello, Richard, thank you for the explanation. It confirms my initial > understanding of the > parameter. But I must be doing something wrong as I am not getting > this clock step. > cve@cve-sbc-flt2:~$ sudo ptp4l -4 -S -s -m -q step_threshold=0.001 -i enp3s0 step_threshold is an option. If specified on command line, it needs to have the "--" prefix: --step_threshold=0.001 -- Miroslav Lichvar |
|
From: Elder C. <eld...@ti...> - 2023-05-11 12:11:47
|
Em qua., 10 de mai. de 2023 às 19:25, Richard Cochran <ric...@gm...> escreveu: > <snipped> > But if you set --step_threshold=X, the program will use method #1 > whenever the estimated offset exceeds X. Hello, Richard, thank you for the explanation. It confirms my initial understanding of the parameter. But I must be doing something wrong as I am not getting this clock step. I have run a test on two Fitlet SBCs, Ubuntu Mate 20.04 LTS, directly connected with each other. I changed the master's system clock with date midway in the test. Wasn't the slave supposed to update its system clock after a few steps? Versions: cve@cve-sbc-flt2:~$ uname -srvpi Linux 5.15.0-71-generic #78~20.04.1-Ubuntu SMP Wed Apr 19 11:26:48 UTC 2023 x86_64 x86_64 cve@cve-sbc-flt2:~$ ptp4l -v 3.1.1 Here is the log on the master side: cve@cve-sbc-flt1:~$ sudo ptp4l -4 -S -m -q -i enp3s0 [sudo] password for cve: ptp4l[5260.670]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[5260.671]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[5267.046]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES ptp4l[5267.046]: selected local clock 0001c0.fffe.1a3e8e as best master ptp4l[5267.046]: port 1: assuming the grand master role Here is the log on the slave side: cve@cve-sbc-flt2:~$ sudo ptp4l -4 -S -s -m -q step_threshold=0.001 -i enp3s0 ptp4l[5616.149]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[5616.149]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[5617.961]: port 1: new foreign master 0001c0.fffe.1a3e8e-1 ptp4l[5621.961]: selected best master clock 0001c0.fffe.1a3e8e ptp4l[5621.961]: foreign master not using PTP timescale ptp4l[5621.961]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE ptp4l[5623.963]: master offset 13926354 s0 freq +100000000 path delay 194691 ptp4l[5624.963]: master offset 13857950 s0 freq +100000000 path delay 208774 ptp4l[5625.963]: master offset 13940749 s0 freq +100000000 path delay 173620 ptp4l[5626.963]: master offset 13935717 s0 freq +100000000 path delay 194691 ptp4l[5627.964]: master offset 13933208 s0 freq +100000000 path delay 194691 ptp4l[5628.964]: master offset 13930547 s0 freq +100000000 path delay 206909 ptp4l[5629.964]: master offset 13803831 s0 freq +100000000 path delay 219127 ptp4l[5630.964]: master offset 13857327 s0 freq +100000000 path delay 219127 ptp4l[5631.964]: master offset 13917423 s0 freq +100000000 path delay 206909 ptp4l[5632.964]: master offset 13918655 s0 freq +100000000 path delay 214912 ptp4l[5633.964]: master offset 13917644 s0 freq +100000000 path delay 216194 ptp4l[5634.964]: master offset 13925743 s0 freq +100000000 path delay 215361 ptp4l[5635.964]: master offset 13917830 s0 freq +100000000 path delay 215361 ptp4l[5636.964]: master offset 13912677 s0 freq +100000000 path delay 215361 ptp4l[5637.965]: master offset 13921067 s0 freq +100000000 path delay 214761 ptp4l[5638.965]: master offset 13934802 s0 freq +100000000 path delay 213895 ptp4l[5639.965]: master offset 13926352 s1 freq +100000000 path delay 210569 ptp4l[5640.965]: master offset 7550 s2 freq +100000000 path delay 210569 ptp4l[5640.965]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED ptp4l[5641.965]: master offset 3335 s2 freq +100000000 path delay 209862 ptp4l[5642.965]: master offset 29048 s2 freq +100000000 path delay 198419 ptp4l[5643.965]: master offset -6089 s2 freq +99999385 path delay 198419 ptp4l[5644.965]: master offset 27372 s2 freq +100000000 path delay 194745 ptp4l[5645.966]: master offset 41165 s2 freq +100000000 path delay 180458 ptp4l[5646.966]: master offset 67436 s2 freq +100000000 path delay 180458 ptp4l[5647.966]: master offset 52707 s2 freq +100000000 path delay 180458 ptp4l[5648.966]: master offset 45178 s2 freq +100000000 path delay 195554 ptp4l[5649.966]: master offset 29094 s2 freq +100000000 path delay 195554 ptp4l[5650.966]: master offset -40457 s2 freq +99995908 path delay 203668 ptp4l[5651.966]: master offset 61863 s2 freq +100000000 path delay 189220 ptp4l[5652.966]: master offset -30990 s2 freq +99996823 path delay 203668 ptp4l[5653.967]: master offset 35655 s2 freq +100000000 path delay 203668 ptp4l[5654.967]: master offset 54452 s2 freq +100000000 path delay 203668 ptp4l[5655.967]: master offset -14750 s2 freq +99998433 path delay 203668 ptp4l[5656.967]: master offset 46659 s2 freq +100000000 path delay 197680 ptp4l[5657.967]: master offset -31081 s2 freq +99996768 path delay 193387 ptp4l[5658.967]: master offset 78940 s2 freq +100000000 path delay 193387 ptp4l[5659.967]: master offset 72995 s2 freq +100000000 path delay 188131 ptp4l[5660.968]: master offset 87009 s2 freq +100000000 path delay 188035 ptp4l[5661.968]: master offset 69708 s2 freq +100000000 path delay 189077 ptp4l[5662.968]: master offset 13182 s2 freq +100000000 path delay 189077 ptp4l[5663.968]: master offset 102075 s2 freq +100000000 path delay 189077 ptp4l[5664.968]: master offset 95211 s2 freq +100000000 path delay 189077 ptp4l[5665.968]: master offset 21393 s2 freq +100000000 path delay 189077 ptp4l[5666.968]: master offset 88257 s2 freq +100000000 path delay 189077 ptp4l[5667.968]: master offset 102154 s2 freq +100000000 path delay 189077 ptp4l[5668.968]: master offset 97624 s2 freq +100000000 path delay 189364 ptp4l[5669.968]: master offset 30572 s2 freq +100000000 path delay 189268 ptp4l[5670.969]: master offset 105652 s2 freq +100000000 path delay 189268 ptp4l[5671.969]: master offset 87663 s2 freq +100000000 path delay 189268 ptp4l[5672.969]: master offset -9329 s2 freq +99998934 path delay 200527 ptp4l[5673.969]: master offset 32310 s2 freq +100000000 path delay 187668 ptp4l[5674.969]: master offset -1504500840665 s2 freq -100000000 path delay 187668 ptp4l[5676.191]: master offset -1503498828645 s2 freq -100000000 path delay 187668 ptp4l[5677.414]: master offset -1503276540145 s2 freq -100000000 path delay 172311 ptp4l[5678.636]: master offset -1503054281517 s2 freq -100000000 path delay 172311 ptp4l[5679.859]: master offset -1502831998290 s2 freq -100000000 path delay 148551 ptp4l[5681.081]: master offset -1502592391017 s2 freq -100000000 path delay -17222716 ptp4l[5682.303]: master offset -1502337842414 s2 freq -100000000 path delay -49505012 ptp4l[5683.526]: master offset -1502099177098 s2 freq -100000000 path delay -65942473 ptp4l[5684.748]: master offset -1501876912775 s2 freq -100000000 path delay -65942473 ptp4l[5685.970]: master offset -1501661138297 s2 freq -100000000 path delay -59498317 ptp4l[5687.193]: master offset -1501435506311 s2 freq -100000000 path delay -62944579 ptp4l[5688.415]: master offset -1501213173765 s2 freq -100000000 path delay -62944579 ptp4l[5689.637]: master offset -1500990924540 s2 freq -100000000 path delay -62944579 ptp4l[5690.860]: master offset -1500775085926 s2 freq -100000000 path delay -56542343 ptp4l[5692.082]: master offset -1500550454220 s2 freq -100000000 path delay -59017651 ptp4l[5693.304]: master offset -1500323595017 s2 freq -100000000 path delay -63532925 ptp4l[5694.527]: master offset -1500101323891 s2 freq -100000000 path delay -63532925 ptp4l[5695.749]: master offset -1499877252874 s2 freq -100000000 path delay -65385477 ptp4l[5696.972]: master offset -1499658928642 s2 freq -100000000 path delay -61458549 ptp4l[5698.194]: master offset -1499436676168 s2 freq -100000000 path delay -61458549 ptp4l[5699.416]: master offset -1499214443160 s2 freq -100000000 path delay -61458549 ptp4l[5700.639]: master offset -1498992192859 s2 freq -100000000 path delay -61458549 ptp4l[5701.861]: master offset -1498771148926 s2 freq -100000000 path delay -60241977 ptp4l[5703.083]: master offset -1498548935865 s2 freq -100000000 path delay -60241977 ptp4l[5704.306]: master offset -1498326670561 s2 freq -100000000 path delay -60241977 ptp4l[5705.528]: master offset -1498103941548 s2 freq -100000000 path delay -60729906 ptp4l[5706.750]: master offset -1497881691115 s2 freq -100000000 path delay -60729906 ptp4l[5707.972]: master offset -1497660321226 s2 freq -100000000 path delay -59919762 ptp4l[5709.195]: master offset -1497434446001 s2 freq -100000000 path delay -63476816 ptp4l[5710.417]: master offset -1497207655400 s2 freq -100000000 path delay -68049885 ptp4l[5711.640]: master offset -1496985382189 s2 freq -100000000 path delay -68049885 ptp4l[5712.862]: master offset -1496744819952 s2 freq -100000000 path delay -86396769 ptp4l[5714.084]: master offset -1496527418428 s2 freq -100000000 path delay -81507676 ptp4l[5715.307]: master offset -1496314631014 s2 freq -100000000 path delay -72051250 ptp4l[5716.529]: master offset -1496092356776 s2 freq -100000000 path delay -72051250 ptp4l[5717.752]: master offset -1495866685965 s2 freq -100000000 path delay -75475651 ptp4l[5718.974]: master offset -1495659636081 s2 freq -100000000 path delay -60369227 ptp4l[5720.196]: master offset -1495422196903 s2 freq -100000000 path delay -75475651 ptp4l[5721.419]: master offset -1495212294793 s2 freq -100000000 path delay -63151399 ptp4l[5722.641]: master offset -1494995684534 s2 freq -100000000 path delay -57501401 ptp4l[5723.863]: master offset -1494773429201 s2 freq -100000000 path delay -57501401 ptp4l[5725.086]: master offset -1494536830363 s2 freq -100000000 path delay -71843099 ptp4l[5726.308]: master offset -1494314686157 s2 freq -100000000 path delay -71843099 ^Ccve@cve-sbc-flt2:~$ |
|
From: Richard C. <ric...@gm...> - 2023-05-10 22:25:15
|
On Wed, May 10, 2023 at 05:10:10PM -0300, Elder Costa wrote:
> Yes, I did read it. Several times. Unfortunately it is still not clear
> what it really means. That line was exactly the reason why I thought
> there would be some sort of clock resynchronization if there were a
> bigger than threshold difference between the local and the master's
> clock, in the first place. So, could you elaborate a little for mine
> and maybe other novice users? Or point to a more detailed reference?
step_threshold
The maximum offset the servo will correct by changing the clock
frequency (phase when using nullf servo) instead of stepping the
clock. When set to 0.0, the servo will never step the clock ex‐
cept on start. It's specified in seconds. The default is 0.0.
The ptp4l program estimates the client/server time offset by using the
PTP. Once the offset estimate is obtained, an action is taken to
correct the client's clock. There are two possible corrective
actions:
1. Set (aka step aka jump) the client clock to match the server's clock.
2. Slew the client clock (by changing the frequency to make it run
faster or slower) until it matches the server's clock.
By default, the ptp4l program uses method #2.
But if you set --step_threshold=X, the program will use method #1
whenever the estimated offset exceeds X.
HTH,
Richard
|
|
From: Elder C. <eld...@ti...> - 2023-05-10 20:15:39
|
Yes, I did read it. Several times. Unfortunately it is still not clear what it really means. That line was exactly the reason why I thought there would be some sort of clock resynchronization if there were a bigger than threshold difference between the local and the master's clock, in the first place. So, could you elaborate a little for mine and maybe other novice users? Or point to a more detailed reference? Em qua., 10 de mai. de 2023 às 16:11, Richard Cochran <ric...@gm...> escreveu: > > On Wed, May 10, 2023 at 02:35:01PM -0300, Elder Costa wrote: > > > I think I am misusing the step_threshold parameter. What exactly this > > parameter does? > > See the man page (ptp4l.8) > > Thanks, > Richard |
|
From: Richard C. <ric...@gm...> - 2023-05-10 19:11:52
|
On Wed, May 10, 2023 at 02:35:01PM -0300, Elder Costa wrote: > I think I am misusing the step_threshold parameter. What exactly this > parameter does? See the man page (ptp4l.8) Thanks, Richard |
|
From: Elder C. <eld...@ti...> - 2023-05-10 17:59:58
|
@Chris Caudle, kernel update is in the development queue. The design this one is derived from is not exposed to a network, so system stability (it is not broken, does not fix) was privileged over keeping it up to date. This new design's requirement is different and the kernel will have to be updated. I think I am misunderstanding a few t. So I have some questions to ask to clarify some points. First question is what does the freq figure means? ptp4l[11303.293]: master offset -578 s2 freq +64977 path delay 78053 ptp4l[11304.294]: master offset 425 s2 freq +65077 path delay 77958 ptp4l[11305.294]: master offset -4653 s2 freq +64565 path delay 77985 ptp4l[11306.294]: master offset -2948 s2 freq +64732 path delay 77985 What could explain its big values in the run I posted in my OP? > ptp4l[23785.675]: master offset 2215 s2 freq +99998938 path delay 66680 > ptp4l[23786.675]: master offset 1182 s2 freq +99998836 path delay 66749 > ptp4l[23787.676]: master offset 3788 s2 freq +99999100 path delay 66749 > ptp4l[23788.676]: master offset 2412 s2 freq +99998965 path delay 66749 Sometimes, when I start the slave and there is a big difference between its clock and the master's, the offset starts big: ~$ sudo ptp4l -i eth0 -S -s -m -q step_threshold=0.00001 ptp4l[11836.182]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[11836.182]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[11838.868]: port 1: new foreign master aabbcc.fffe.ddee66-1 ptp4l[11843.269]: selected best master clock aabbcc.fffe.ddee66 ptp4l[11843.269]: foreign master not using PTP timescale ptp4l[11843.269]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE ptp4l[11845.469]: master offset -3536460389269 s0 freq -100000000 path delay -29979969 ptp4l[11846.569]: master offset -3536360300857 s0 freq -100000000 path delay -29979969 ptp4l[11847.669]: master offset -3536274698933 s0 freq -100000000 path delay -15493484 ptp4l[11848.769]: master offset -3536181043684 s0 freq -100000000 path delay -9059394 ... ptp4l[11861.972]: master offset -3534976041966 s1 freq -1062624 path delay -13065167 ptp4l[11862.975]: master offset 2772202 s2 freq -782632 path delay -13065167 ptp4l[11862.975]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED ptp4l[11863.976]: master offset -6087691 s2 freq -1674709 path delay -3354109 ptp4l[11864.977]: master offset -5337010 s2 freq -1604978 path delay -2385342 ptp4l[11865.979]: master offset -4294068 s2 freq -1504978 path delay -1756173 ptp4l[11866.981]: master offset -3994368 s2 freq -1479002 path delay -486776 ptp4l[11867.983]: master offset -2451261 s2 freq -1327143 path delay -486776 ptp4l[11868.984]: master offset -1054808 s2 freq -1188552 path delay -486776 ptp4l[11869.986]: master offset 155097 s2 freq -1067407 path delay -444443 ptp4l[11870.987]: master offset 1291473 s2 freq -952478 path delay -444443 .... ptp4l[11900.000]: master offset 9506432 s2 freq +95385 path delay 77000 ptp4l[11901.000]: master offset 9478411 s2 freq +102062 path delay 77000 ptp4l[11902.001]: master offset 9442138 s2 freq +107877 path delay 77766 ptp4l[11903.001]: master offset 9397344 s2 freq +112795 path delay 78496 I think I am misusing the step_threshold parameter. What exactly this parameter does? Is there an ideal value or I should just leave it alone (just use the default)? Is there a way to force the slave's system clock to resynchronize with the master's if it changes? Assume when powered up, the grandmaster (diagram in my OP) is not connected, the clock of the Embedded PC is off and the Custom Board's system clock synchronizes with it. When the GM is connected, the EPC's will synchronize with the GM's and then I have my CB totally off. Will I need to restart ptp4l on the CB? |
|
From: Chris C. <ch...@ch...> - 2023-05-10 13:40:23
|
On Wed, May 10, 2023 7:10 am, lin...@li... wrote: > Both the Embedded PC is running kernel 4.14.30 and the Custom board, > kernel 4.14.0, both 32-bits. I compiled linuxptp 3.1.1 for both. 4.14.0 was released 5-1/2 years ago. There have been 314 bug and security fix releases since then. The latest release in that series is 4.14.314 from 26 Apr 2023. Running a kernel that old is just asking for problems and is not a sensible thing to do. -- Chris Caudle |
|
From: Elder C. <eld...@ti...> - 2023-05-09 21:36:54
|
I am evaluating linuxptp for use in an embedded system. The basic architecture is as follows: +-------------+ +-------------+ +-------------+ | | | | | | | | | | | | | GRANDMASTER |<--->| Embedded PC |<-->| Custom board| | (PC) | | (Intel) | | | | | | | | | +-------------+ +-------------+ +-------------+ The Embedded system is constituted by an embedded PC (Intel based) and a custom board both running Linux and it is intended to be connected to an external PC (also Linux) Both the Embedded PC is running kernel 4.14.30 and the Custom board, kernel 4.14.0, both 32-bits. I compiled linuxptp 3.1.1 for both. As the custom board does not support hardware timestamp, I am experimenting with the software timestamp. I forced the custom board to client mode: sudo ptp4l -i eth0 -S -s -m -q step_threshold=0.00001 And the Embedded PC works as grandmaster for the Custom board: sudo ptp4l -i eth_am -S -m -q step_threshold=0.00001 I noticed that sometimes the master offset starts increasing as if the clock was no longer being updated. Unfortunately I did not save an instance of the log when this anomaly happened. I saved a sample of the log after running similar commands on two Fitlet PCs running Ubuntu Mate 20.04LTS (kernel 5.4.0, 64-bits OS), also running linuxptp 3.1.1 compiled in. I noticed what looks like an important difference between both configurations. This is the log of the custom board: custom_board:~$ sudo ptp4l -i eth0 -S -s -m -q step_threshold=0.00001 ptp4l[23715.187]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[23715.187]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[23721.896]: selected local clock 000a35.fffe.000122 as best master ptp4l[23728.111]: selected local clock 000a35.fffe.000122 as best master ptp4l[23735.085]: selected local clock 000a35.fffe.000122 as best master ptp4l[23742.999]: selected local clock 000a35.fffe.000122 as best master ptp4l[23749.230]: selected local clock 000a35.fffe.000122 as best master ptp4l[23755.780]: selected local clock 000a35.fffe.000122 as best master ptp4l[23761.675]: port 1: new foreign master aabbcc.fffe.ddee66-1 ptp4l[23762.677]: selected local clock 000a35.fffe.000122 as best master ptp4l[23765.675]: selected best master clock aabbcc.fffe.ddee66 ptp4l[23765.675]: foreign master not using PTP timescale ptp4l[23765.675]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE ptp4l[23767.674]: master offset -519361 s0 freq +100000000 path delay 64850 ptp4l[23768.674]: master offset -519678 s0 freq +100000000 path delay 64850 ptp4l[23769.674]: master offset -523460 s0 freq +100000000 path delay 65099 ptp4l[23770.674]: master offset -521308 s0 freq +100000000 path delay 65275 ptp4l[23771.674]: master offset -525323 s0 freq +100000000 path delay 65275 ptp4l[23772.674]: master offset -528631 s0 freq +100000000 path delay 65318 ptp4l[23773.675]: master offset -527435 s0 freq +100000000 path delay 65318 ptp4l[23774.675]: master offset -528132 s0 freq +100000000 path delay 65451 ptp4l[23775.675]: master offset -533678 s0 freq +100000000 path delay 65972 ptp4l[23776.675]: master offset -531624 s0 freq +100000000 path delay 65972 ptp4l[23777.675]: master offset -534432 s0 freq +100000000 path delay 66493 ptp4l[23778.675]: master offset -534855 s0 freq +100000000 path delay 65988 ptp4l[23779.675]: master offset -537967 s0 freq +100000000 path delay 66572 ptp4l[23780.675]: master offset -539110 s0 freq +100000000 path delay 66572 ptp4l[23781.675]: master offset -538102 s0 freq +100000000 path delay 65988 ptp4l[23782.675]: master offset -540316 s0 freq +100000000 path delay 66572 ptp4l[23783.675]: master offset -542282 s1 freq +99998711 path delay 66680 ptp4l[23784.675]: master offset 3549 s2 freq +99999069 path delay 66680 ptp4l[23784.675]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED ptp4l[23785.675]: master offset 2215 s2 freq +99998938 path delay 66680 ptp4l[23786.675]: master offset 1182 s2 freq +99998836 path delay 66749 ptp4l[23787.676]: master offset 3788 s2 freq +99999100 path delay 66749 ptp4l[23788.676]: master offset 2412 s2 freq +99998965 path delay 66749 ptp4l[23789.676]: master offset 1775 s2 freq +99998903 path delay 66749 ptp4l[23790.676]: master offset 4067 s2 freq +99999136 path delay 66680 ptp4l[23791.676]: master offset 824 s2 freq +99998813 path delay 66749 ptp4l[23792.676]: master offset 3687 s2 freq +99999103 path delay 66749 ptp4l[23793.676]: master offset 3373 s2 freq +99999075 path delay 66749 ptp4l[23794.676]: master offset 6239 s2 freq +99999368 path delay 66749 ptp4l[23795.676]: master offset 9323 s2 freq +99999686 path delay 66838 ptp4l[23796.676]: master offset 8212 s2 freq +99999583 path delay 66838 ptp4l[23797.676]: master offset 6440 s2 freq +99999412 path delay 67000 ptp4l[23798.676]: master offset 10252 s2 freq +99999803 path delay 67602 ptp4l[23799.676]: master offset 6070 s2 freq +99999391 path delay 67602 ptp4l[23800.676]: master offset 5183 s2 freq +99999308 path delay 67602 ptp4l[23801.676]: master offset 6810 s2 freq +99999477 path delay 67602 ptp4l[23802.676]: master offset 7300 s2 freq +99999533 path delay 68151 ptp4l[23803.676]: master offset 7303 s2 freq +99999541 path delay 68151 ptp4l[23804.676]: master offset 8433 s2 freq +99999663 path delay 68151 ptp4l[23805.677]: master offset 8715 s2 freq +99999699 path delay 68151 ptp4l[23806.677]: master offset 6014 s2 freq +99999435 path delay 68151 The important difference between the above and the test with the Fitlets is on the clock column, all values are +100000000 or close to it, all positive values, whereas on the Fitlets, the values are much lower and alternate between positive and negative values as well as the offsets. So it occurred there could be some software issue in this fairly old kernel version that may have been fixed in more recent kernels. Or maybe it is has to do with 32-bits vs 64-bits OS. Or I am simply doing something very wrong. Any help to help me to identify and fix this problem is welcome. TIA. |
|
From: 黄艮燕 <gen...@di...> - 2023-05-09 05:48:34
|
Hello,
We are currently trying to run ptp4l without announce messages.
However, the runtime encountered some problems, such as slave not sending delay_req messages.
So I wonder if ptp4l supports not sending announce messages? If so, how to configure it.
Thanks
gen...@di...
|
|
From: Saurav K. <s.k...@si...> - 2023-04-19 11:35:22
|
Hi All, I have been facing "received SYNC without timestamp" issue whlie running PTP slave. I have also attached output of cat /sys/kernel/debug/tracing/trace_pipe | grep -C3 i40e in trace_pipe_i40e.txt We are using Intel XXV710 series ethernet controller. Following are the information of PTP slave machine. Please let me know if you need anything. root# ptp4l -m -s -f /root/oru-sim/config/ptp_slave.conf -l 7 -2 -H ptp4l[12624.712]: config item (null).assume_two_step is 0 ptp4l[12624.712]: config item (null).check_fup_sync is 0 ptp4l[12624.712]: config item (null).tx_timestamp_timeout is 500 ptp4l[12624.712]: config item (null).hwts_filter is 0 ptp4l[12624.712]: config item (null).clock_servo is 0 ptp4l[12624.712]: config item (null).clock_type is 32768 ptp4l[12624.712]: config item (null).clock_servo is 0 ptp4l[12624.712]: config item (null).clockClass is 248 ptp4l[12624.712]: config item (null).clockAccuracy is 254 ptp4l[12624.712]: config item (null).offsetScaledLogVariance is 65535 ptp4l[12624.712]: config item (null).productDescription is ';;' ptp4l[12624.712]: config item (null).revisionData is ';;' ptp4l[12624.712]: config item (null).userDescription is ';' ptp4l[12624.712]: config item (null).manufacturerIdentity is '00:00:00' ptp4l[12624.712]: config item (null).domainNumber is 24 ptp4l[12624.712]: config item (null).slaveOnly is 1 ptp4l[12624.712]: config item (null).gmCapable is 1 ptp4l[12624.712]: config item (null).gmCapable is 1 ptp4l[12624.712]: config item (null).G.8275.defaultDS.localPriority is 128 ptp4l[12624.712]: config item (null).maxStepsRemoved is 255 ptp4l[12624.712]: config item (null).time_stamping is 1 ptp4l[12624.712]: config item (null).twoStepFlag is 1 ptp4l[12624.712]: config item (null).twoStepFlag is 1 ptp4l[12624.712]: config item (null).time_stamping is 1 ptp4l[12624.712]: config item (null).priority1 is 128 ptp4l[12624.712]: config item (null).priority2 is 128 ptp4l[12624.712]: interface index 4 is up ptp4l[12624.712]: config item (null).free_running is 0 ptp4l[12624.712]: selected /dev/ptp3 as PTP clock ptp4l[12624.712]: config item (null).clockIdentity is '000000.0000.000000' ptp4l[12624.712]: config item (null).uds_address is '/var/run/ptp4l' ptp4l[12624.712]: section item /var/run/ptp4l.announceReceiptTimeout now 0 ptp4l[12624.712]: section item /var/run/ptp4l.delay_mechanism now 0 ptp4l[12624.712]: section item /var/run/ptp4l.network_transport now 0 ptp4l[12624.712]: section item /var/run/ptp4l.delay_filter_length now 1 ptp4l[12624.712]: config item (null).free_running is 0 ptp4l[12624.712]: config item (null).freq_est_interval is 1 ptp4l[12624.712]: config item (null).write_phase_mode is 0 ptp4l[12624.712]: config item (null).gmCapable is 1 ptp4l[12624.712]: config item (null).kernel_leap is 1 ptp4l[12624.712]: config item (null).utc_offset is 37 ptp4l[12624.712]: config item (null).timeSource is 160 ptp4l[12624.712]: config item (null).pi_proportional_const is 0.000000 ptp4l[12624.712]: config item (null).pi_integral_const is 0.000000 ptp4l[12624.712]: config item (null).pi_proportional_scale is 0.000000 ptp4l[12624.712]: config item (null).pi_proportional_exponent is -0.300000 ptp4l[12624.712]: config item (null).pi_proportional_norm_max is 0.700000 ptp4l[12624.712]: config item (null).pi_integral_scale is 0.000000 ptp4l[12624.712]: config item (null).pi_integral_exponent is 0.400000 ptp4l[12624.712]: config item (null).pi_integral_norm_max is 0.300000 ptp4l[12624.712]: config item (null).step_threshold is 0.000000 ptp4l[12624.712]: config item (null).first_step_threshold is 0.000020 ptp4l[12624.712]: config item (null).max_frequency is 900000000 ptp4l[12624.712]: config item (null).servo_offset_threshold is 0 ptp4l[12624.712]: config item (null).servo_num_offset_values is 10 ptp4l[12624.712]: config item (null).dataset_comparison is 0 ptp4l[12624.712]: config item (null).delay_filter_length is 10 ptp4l[12624.712]: config item (null).delay_filter is 1 ptp4l[12624.712]: config item (null).tsproc_mode is 0 ptp4l[12624.712]: config item (null).initial_delay is 0 ptp4l[12624.712]: config item (null).summary_interval is 0 ptp4l[12624.712]: config item (null).sanity_freq_limit is 200000000 ptp4l[12624.712]: PI servo: sync interval 1.000 kp 0.700 ki 0.300000 ptp4l[12624.712]: config item /var/run/ptp4l.boundary_clock_jbod is 0 ptp4l[12624.712]: config item /var/run/ptp4l.network_transport is 0 ptp4l[12624.712]: config item /var/run/ptp4l.masterOnly is 0 ptp4l[12624.712]: config item /var/run/ptp4l.BMCA is 0 ptp4l[12624.712]: config item /var/run/ptp4l.delayAsymmetry is 0 ptp4l[12624.712]: config item /var/run/ptp4l.follow_up_info is 0 ptp4l[12624.712]: config item /var/run/ptp4l.freq_est_interval is 1 ptp4l[12624.712]: config item /var/run/ptp4l.msg_interval_request is 0 ptp4l[12624.712]: config item /var/run/ptp4l.net_sync_monitor is 0 ptp4l[12624.712]: config item /var/run/ptp4l.path_trace_enabled is 0 ptp4l[12624.712]: config item /var/run/ptp4l.tc_spanning_tree is 0 ptp4l[12624.712]: config item /var/run/ptp4l.ingressLatency is 0 ptp4l[12624.712]: config item /var/run/ptp4l.egressLatency is 0 ptp4l[12624.712]: config item /var/run/ptp4l.delay_mechanism is 0 ptp4l[12624.712]: config item /var/run/ptp4l.hybrid_e2e is 0 ptp4l[12624.712]: config item /var/run/ptp4l.fault_badpeernet_interval is 16 ptp4l[12624.712]: config item /var/run/ptp4l.fault_reset_interval is 4 ptp4l[12624.712]: config item /var/run/ptp4l.delay_filter_length is 1 ptp4l[12624.712]: config item /var/run/ptp4l.delay_filter is 1 ptp4l[12624.712]: config item /var/run/ptp4l.tsproc_mode is 0 ptp4l[12624.712]: config item (null).slave_event_monitor is '' ptp4l[12624.712]: config item ens5f0.boundary_clock_jbod is 0 ptp4l[12624.712]: config item ens5f0.network_transport is 3 ptp4l[12624.712]: config item ens5f0.masterOnly is 0 ptp4l[12624.712]: config item ens5f0.BMCA is 0 ptp4l[12624.712]: config item ens5f0.delayAsymmetry is 0 ptp4l[12624.712]: config item ens5f0.follow_up_info is 0 ptp4l[12624.712]: config item ens5f0.freq_est_interval is 1 ptp4l[12624.712]: config item ens5f0.msg_interval_request is 0 ptp4l[12624.712]: config item ens5f0.net_sync_monitor is 0 ptp4l[12624.712]: config item ens5f0.path_trace_enabled is 0 ptp4l[12624.712]: config item ens5f0.tc_spanning_tree is 0 ptp4l[12624.712]: config item ens5f0.ingressLatency is 0 ptp4l[12624.712]: config item ens5f0.egressLatency is 0 ptp4l[12624.712]: config item ens5f0.delay_mechanism is 1 ptp4l[12624.712]: config item ens5f0.unicast_master_table is 0 ptp4l[12624.712]: config item ens5f0.unicast_listen is 0 ptp4l[12624.712]: config item ens5f0.hybrid_e2e is 0 ptp4l[12624.712]: config item ens5f0.fault_badpeernet_interval is 16 ptp4l[12624.712]: config item ens5f0.fault_reset_interval is 4 ptp4l[12624.712]: config item ens5f0.delay_filter_length is 10 ptp4l[12624.712]: config item ens5f0.delay_filter is 1 ptp4l[12624.712]: config item ens5f0.tsproc_mode is 0 ptp4l[12624.712]: config item ens5f0.logMinDelayReqInterval is 0 ptp4l[12624.712]: config item ens5f0.logAnnounceInterval is 1 ptp4l[12624.712]: config item ens5f0.inhibit_announce is 0 ptp4l[12624.712]: config item ens5f0.ignore_source_id is 0 ptp4l[12624.712]: config item ens5f0.announceReceiptTimeout is 5 ptp4l[12624.712]: config item ens5f0.syncReceiptTimeout is 0 ptp4l[12624.712]: config item ens5f0.transportSpecific is 0 ptp4l[12624.712]: config item ens5f0.ignore_transport_specific is 0 ptp4l[12624.712]: config item ens5f0.G.8275.portDS.localPriority is 128 ptp4l[12624.712]: config item ens5f0.logSyncInterval is 0 ptp4l[12624.712]: config item ens5f0.operLogSyncInterval is 0 ptp4l[12624.712]: config item ens5f0.logMinPdelayReqInterval is 0 ptp4l[12624.712]: config item ens5f0.operLogPdelayReqInterval is 0 ptp4l[12624.712]: config item ens5f0.neighborPropDelayThresh is 20000000 ptp4l[12624.713]: config item ens5f0.min_neighbor_prop_delay is -20000000 ptp4l[12624.713]: config item ens5f0.asCapable is 1 ptp4l[12624.713]: config item ens5f0.inhibit_delay_req is 0 ptp4l[12624.713]: config item ens5f0.ptp_dst_mac is '01:1B:19:00:00:00' ptp4l[12624.713]: config item ens5f0.p2p_dst_mac is '01:1B:19:00:00:00' ptp4l[12624.713]: config item global.socket_priority is 0 ptp4l[12624.781]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[12624.781]: config item /var/run/ptp4l.logMinDelayReqInterval is 0 ptp4l[12624.781]: config item /var/run/ptp4l.logAnnounceInterval is 1 ptp4l[12624.781]: config item /var/run/ptp4l.inhibit_announce is 0 ptp4l[12624.781]: config item /var/run/ptp4l.ignore_source_id is 0 ptp4l[12624.781]: config item /var/run/ptp4l.announceReceiptTimeout is 0 ptp4l[12624.781]: config item /var/run/ptp4l.syncReceiptTimeout is 0 ptp4l[12624.781]: config item /var/run/ptp4l.transportSpecific is 0 ptp4l[12624.781]: config item /var/run/ptp4l.ignore_transport_specific is 0 ptp4l[12624.781]: config item /var/run/ptp4l.G.8275.portDS.localPriority is 128 ptp4l[12624.781]: config item /var/run/ptp4l.logSyncInterval is 0 ptp4l[12624.781]: config item /var/run/ptp4l.operLogSyncInterval is 0 ptp4l[12624.781]: config item /var/run/ptp4l.logMinPdelayReqInterval is 0 ptp4l[12624.781]: config item /var/run/ptp4l.operLogPdelayReqInterval is 0 ptp4l[12624.781]: config item /var/run/ptp4l.neighborPropDelayThresh is 20000000 ptp4l[12624.781]: config item /var/run/ptp4l.min_neighbor_prop_delay is -20000000 ptp4l[12624.781]: config item /var/run/ptp4l.asCapable is 1 ptp4l[12624.781]: config item /var/run/ptp4l.inhibit_delay_req is 0 ptp4l[12624.781]: config item (null).uds_address is '/var/run/ptp4l' ptp4l[12624.781]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[12624.782]: port 1: received link status notification ptp4l[12624.782]: interface index 4 is up ptp4l[12625.708]: port 1: setting asCapable ptp4l[12625.708]: port 1: new foreign master 2cea7f.fffe.fff83d-1 ptp4l[12625.708]: port 1: received SYNC without timestamp ptp4l[12625.770]: port 1: received SYNC without timestamp ptp4l[12625.833]: port 1: received SYNC without timestamp ptp4l[12625.895]: port 1: received SYNC without timestamp ptp4l[12625.958]: selected best master clock 2cea7f.fffe.fff83d ptp4l[12625.958]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE ptp4l[12625.958]: port 1: received SYNC without timestamp ptp4l[12626.021]: port 1: received SYNC without timestamp ptp4l[12626.021]: port 1: have FOLLOW_UP 14938, expecting SYNC but got FOLLOW_UP 14939, dropping ptp4l[12626.083]: port 1: received SYNC without timestamp ptp4l[12626.083]: port 1: have FOLLOW_UP 14939, expecting SYNC but got FOLLOW_UP 14940, dropping ptp4l[12626.146]: port 1: received SYNC without timestamp =========== *root# uname -a* Linux admin *5.15.0-69-generic* #76~20.04.1-Ubuntu SMP Mon Mar 20 15:54:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root# ethtool -i ens5f0 driver: i40e version: 5.15.0-69-generic firmware-version: 8.40 0x8000b1fb 20.5.13 expansion-rom-version: bus-info: 0000:b1:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes Time stamping parameters: Capabilities: hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE) software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE) hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE) software-receive (SOF_TIMESTAMPING_RX_SOFTWARE) software-system-clock (SOF_TIMESTAMPING_SOFTWARE) hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE) PTP Hardware Clock: 0 Hardware Transmit Timestamp Modes: off (HWTSTAMP_TX_OFF) on (HWTSTAMP_TX_ON) Hardware Receive Filter Modes: none (HWTSTAMP_FILTER_NONE) all (HWTSTAMP_FILTER_ALL) ptpv1-l4-sync (HWTSTAMP_FILTER_PTP_V1_L4_SYNC) ptpv1-l4-delay-req (HWTSTAMP_FILTER_PTP_V1_L4_DELAY_REQ) ptpv2-l4-sync (HWTSTAMP_FILTER_PTP_V2_L4_SYNC) ptpv2-l4-delay-req (HWTSTAMP_FILTER_PTP_V2_L4_DELAY_REQ) ptpv2-l2-sync (HWTSTAMP_FILTE R_PTP_V2_L2_SYNC) ptpv2-l2-delay-req (HWTSTAMP_FILTER_PTP_V2_L2_DELAY_REQ) ptpv2-event (HWTSTAMP_FILTER_PTP_V2_EVENT) ptpv2-sync (HWTSTAMP_FILTER_PTP_V2_SYNC) ptpv2-delay-req (HWTSTAMP_FILTER_PTP_V2_DELAY_REQ) ================ ethtool -S <ptp_slave_interface> | grep tstamp port.tx_hwtstamp_timeouts: 0 port.rx_hwtstamp_cleared: 0 port.tx_hwtstamp_skipped: 0 Thanks Saurav |
|
From: Richard C. <ric...@gm...> - 2023-04-16 15:11:07
|
On Sun, Apr 16, 2023 at 01:54:20PM +0530, shashank varshney wrote: > *sfptpd supports PTP packets over bonded interfaces in an active/standby > mode. In addition, sfptpd also supports bonding over LACP (802.3ad) > bonding.* Looks like sfptpd is a hacked version of the old ptpd program. If that works for you, then great. > *Is there any plan to include a similar kind of working mechanism for PTP > over Linux Bonding for seamless switchover in case of failure of > active-slave port to passive-slave port when both slaves are on different > NICs with different PHCs?* I'm not aware of any plan for that. If you feel like adding it, then we'll look forward to your patches on the list... Thanks, Richard |
|
From: shashank v. <sha...@gm...> - 2023-04-16 08:24:39
|
Hi Miroslav, I Hope you are doing well and thanks a lot for the response. I was looking at Xillinx sfptpd utility and the following is the working mechanism of PTP over the Linux bonded interfaces: https://docs.xilinx.com/r/en-US/ug1602-ptp-user/PTP-over-Bonded-Interfaces *PTP over Bonded Interfaces* *sfptpd supports PTP packets over bonded interfaces in an active/standby mode. In addition, sfptpd also supports bonding over LACP (802.3ad) bonding.* *Bonding of interfaces on supported adapters employs the Linux bonding driver. Multiple ports can be included into a single bond where one port is selected as the active interface and all others are standby.* - *sfptpd will detect which port is active and which ports are passive in the bond.* - *sfptpd will discipline the high precision clock on the active port’s network adapter.* - *sfptpd will discipline the clocks of passive ports from the active adapter’s clock.* - *Via the bonding driver you can select the active port (and therefore clock).* - *A bond can include non-PTP capable ports on a supported adapter.* *sfptpd will switch to software time-stamping when a non-hardware time-stamping port becomes active.* - *A bond can include third party ports .* *sfptpd will switch to software time-stamping when a third party port becomes active.* - *A bond can include any number of ports.* *Is there any plan to include a similar kind of working mechanism for PTP over Linux Bonding for seamless switchover in case of failure of active-slave port to passive-slave port when both slaves are on different NICs with different PHCs?* Thanks and regards Shashank Varshney On Tue, Apr 11, 2023 at 12:50 PM Miroslav Lichvar <mli...@re...> wrote: > On Mon, Apr 10, 2023 at 10:49:45PM +0530, shashank varshney wrote: > > I have following queries related to functioning of PTP with > active-passive > > bonding: > > > > - Will passive/standby slave PHC synchronize itself with active slave > > PHC when active-passive NIC ports are on different PHCs? > > No, phc2sys doesn't know about the other interfaces in the bond. > > > - Does the passive NIC port's PHC is ready to take-over when the > current > > active slave NIC goes down or does this require the passive NIC's PHC > to > > synchronize first? > > The latter. It's not a seamless switch. > > -- > Miroslav Lichvar > > |
|
From: Aris T. <ar...@ma...> - 2023-04-14 02:18:01
|
> Could you provide the output of ethtool -i for the device and the lspci > -v info for the device? I'm curious if I can see what it claims to be… > Hi Jacob, For interest/curiosity here are the outputs: ethtool -I output: driver: igb version: 6.1.20-rt8 firmware-version: 3.25, 0x800005d1 expansion-rom-version: bus-info: 0000:03:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes lspci -v output: 03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 2 Memory at 9fb00000 (32-bit, non-prefetchable) [size=512K] Memory at 9fb80000 (32-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [70] MSI-X: Enable+ Count=5 Masked- Capabilities: [a0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 6c-b3-11-ff-ff-66-39-10 Capabilities: [1a0] Transaction Processing Hints Kernel driver in use: igb Kernel modules: igb |
|
From: Eric D. <eri...@to...> - 2023-04-13 22:30:00
|
Thank you, Richard! Eric Decker -----Original Message----- From: Richard Cochran <ric...@gm...> Sent: Thursday, April 13, 2023 6:17 PM To: Eric Decker <eri...@to...> Cc: lin...@li... Subject: Re: [Linuxptp-users] 802.1AS management On Thu, Apr 13, 2023 at 05:03:50PM +0000, Eric Decker wrote: > I am working on monitoring gPTP health for automotive products using 802.1AS. > According to 802.1AS-2020: > > 1. Section 10.6.1 "PTP Management Messages are not used in this standard. They are specified in IEEE Std 1588-2019." > * Does this means gPTP does not support PTP management messages? Seems like it. > * If ptp4l is configured to use 802.1AS will it support management messages? Yes. > 2. Section 15.1 "Managed objects are accessed via a virtual information store, termed the Management Information Base (MIB). MIB objects are generally accessed through the Simple Network Management Protocol (SNMP)." > * My understanding is that PTP management messages at not supported and MIBs and SNMP should be used instead. > * Does Linux PTP support MIBs and SNMP? From what I can tell from the code it does not. I looked at the mailing list and it appears SNMP support was removed around March 2020 because it was not complete. It does not appear it has been added back to the code base, at least not on the Git master branch. Are there plans to support MIBs and SNMP in the future? SNMP is not supported, and there are no plans to add that. > 3. Does Linux PTP support "reverse sync" for monitoring, or will it support it in the future? Yes, it supports the NetSync Monitor (NSM) protocol. See the 'nsm' program and its man page. Thanks, Richard CAUTION: This email originated from outside of TORC's email system. DO NOT click links or open attachments unless you recognize the sender and know the content is safe. Email is NOT a secure means of communication. Handle potentially sensitive information with care. Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. |
|
From: Richard C. <ric...@gm...> - 2023-04-13 22:16:47
|
On Thu, Apr 13, 2023 at 05:03:50PM +0000, Eric Decker wrote: > I am working on monitoring gPTP health for automotive products using 802.1AS. > According to 802.1AS-2020: > > 1. Section 10.6.1 "PTP Management Messages are not used in this standard. They are specified in IEEE Std 1588-2019." > * Does this means gPTP does not support PTP management messages? Seems like it. > * If ptp4l is configured to use 802.1AS will it support management messages? Yes. > 2. Section 15.1 "Managed objects are accessed via a virtual information store, termed the Management Information Base (MIB). MIB objects are generally accessed through the Simple Network Management Protocol (SNMP)." > * My understanding is that PTP management messages at not supported and MIBs and SNMP should be used instead. > * Does Linux PTP support MIBs and SNMP? From what I can tell from the code it does not. I looked at the mailing list and it appears SNMP support was removed around March 2020 because it was not complete. It does not appear it has been added back to the code base, at least not on the Git master branch. Are there plans to support MIBs and SNMP in the future? SNMP is not supported, and there are no plans to add that. > 3. Does Linux PTP support "reverse sync" for monitoring, or will it support it in the future? Yes, it supports the NetSync Monitor (NSM) protocol. See the 'nsm' program and its man page. Thanks, Richard |
|
From: Eric D. <eri...@to...> - 2023-04-13 21:37:02
|
Hello Linux PTP users,
Thanks for all the great work on Linux PTP.
I am working on monitoring gPTP health for automotive products using 802.1AS.
According to 802.1AS-2020:
1. Section 10.6.1 "PTP Management Messages are not used in this standard. They are specified in IEEE Std 1588-2019."
* Does this means gPTP does not support PTP management messages?
* If ptp4l is configured to use 802.1AS will it support management messages?
2. Section 15.1 "Managed objects are accessed via a virtual information store, termed the Management Information Base (MIB). MIB objects are generally accessed through the Simple Network Management Protocol (SNMP)."
* My understanding is that PTP management messages at not supported and MIBs and SNMP should be used instead.
* Does Linux PTP support MIBs and SNMP? From what I can tell from the code it does not. I looked at the mailing list and it appears SNMP support was removed around March 2020 because it was not complete. It does not appear it has been added back to the code base, at least not on the Git master branch. Are there plans to support MIBs and SNMP in the future?
3. Does Linux PTP support "reverse sync" for monitoring, or will it support it in the future?
Thank you,
[cid:image001.png@01D96E06.131BD2F0]
Eric Decker
TORC Robotics, Inc.
405 Partnership Drive, Blacksburg, VA 24060
Website: https://torc.ai<https://torc.ai/>
[cid:image002.png@01D96E06.131BD2F0]<https://www.facebook.com/torcrobotics/> [cid:image003.png@01D96E06.131BD2F0] <https://www.linkedin.com/company/torc-technologies/about/?viewAsMember=true> [cid:image004.png@01D96E06.131BD2F0] <https://twitter.com/torcrobotics> [cid:image005.png@01D96E06.131BD2F0] <https://www.youtube.com/channel/UCGKXBpisBMTJtshrr3KkOTg?view_as=subscriber> [cid:image006.png@01D96E06.131BD2F0] <https://www.instagram.com/torc_robotics/?hl=en> [cid:image007.jpg@01D96E06.131BD2F0] <https://www.glassdoor.com/Overview/Working-at-TORC-Robotics-EI_IE1027022.11,24.htm>
Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
|
|
From: Jacob K. <jac...@in...> - 2023-04-12 18:24:37
|
On 4/11/2023 7:24 AM, Aris Theocharides via Linuxptp-users wrote: > >> Also try a non RT kernel. > > I’ve tried the non-RT / generic/default kernel, and the behaviour remains unchanged as for the RT kernel. > >> FWIW I have a box with three 1-port i210 PCIe cards that runs fine on >> vanilla kernel. > > LR actually have a slew of Industrial Ethernet (all multiport) on their website. > > I could only buy these cards in pairs, hence I have two. I could send one over if it will help. > > Aris Could you provide the output of ethtool -i for the device and the lspci -v info for the device? I'm curious if I can see what it claims to be... Thanks, Jake |
|
From: Richard C. <ric...@gm...> - 2023-04-12 16:54:28
|
On Wed, Apr 12, 2023 at 02:56:31PM +1000, Aris Theocharides wrote: > > >> LR actually have a slew of Industrial Ethernet (all multiport) on their website. > >> > > Okay, so I guess this is not a true Intel i210 but some kind of > > strange clone. > > It would seem so, although I guess that some single port i210’s are also and they seem to work ok with LinuxPTP. I'm trying to tell you that there is no such thing as a 4-port i210. See: https://www.intel.com/content/www/us/en/products/details/ethernet/gigabit-controllers/i210-controllers.html So your 4-port card is not an i210 at all. Thanks, Richard |
|
From: Aris T. <ar...@ma...> - 2023-04-12 04:57:04
|
>> LR actually have a slew of Industrial Ethernet (all multiport) on their website. >> > Okay, so I guess this is not a true Intel i210 but some kind of > strange clone. It would seem so, although I guess that some single port i210’s are also and they seem to work ok with LinuxPTP. I’m using an i350 quad port at the moment but it doesn’t support hardware CBS and ETF offloading. Aris |
|
From: Richard C. <ric...@gm...> - 2023-04-12 00:08:10
|
On Wed, Apr 12, 2023 at 12:24:21AM +1000, Aris Theocharides wrote: > LR actually have a slew of Industrial Ethernet (all multiport) on their website. Okay, so I guess this is not a true Intel i210 but some kind of strange clone. Thanks, Richard |
|
From: Aris T. <ar...@ma...> - 2023-04-11 14:24:43
|
> Also try a non RT kernel. I’ve tried the non-RT / generic/default kernel, and the behaviour remains unchanged as for the RT kernel. > FWIW I have a box with three 1-port i210 PCIe cards that runs fine on > vanilla kernel. LR actually have a slew of Industrial Ethernet (all multiport) on their website. I could only buy these cards in pairs, hence I have two. I could send one over if it will help. Aris |
|
From: Miroslav L. <mli...@re...> - 2023-04-11 07:20:57
|
On Mon, Apr 10, 2023 at 10:49:45PM +0530, shashank varshney wrote: > I have following queries related to functioning of PTP with active-passive > bonding: > > - Will passive/standby slave PHC synchronize itself with active slave > PHC when active-passive NIC ports are on different PHCs? No, phc2sys doesn't know about the other interfaces in the bond. > - Does the passive NIC port's PHC is ready to take-over when the current > active slave NIC goes down or does this require the passive NIC's PHC to > synchronize first? The latter. It's not a seamless switch. -- Miroslav Lichvar |
27 messages has been excluded from this view by a project administrator.
