I have also stopped chronyd and the clocks still drift appart. On Fri, 12 Oct 2018 at 11:54, Joanna <ozi...@gmail.com> wrote: > > Thanks Miroslav. I appreciate the help. > Below is the log afterp phc2sys restart (/usr/sbin/phc2sys -a -r -r -u > 60). Log includes output from testptp -k1 where the offset beteen phc > and system got from 6373992ns to 13611908ns (7237916ns) in ca 4.h min. > Please let me know if I can provide more information. > Oct 12 09:37:47 nfltest phc2sys: [796.112] reconfiguring after port state > change > Oct 12 09:37:47 nfltest phc2sys: [796.113] selecting eth1 for synchronization > Oct 12 09:37:47 nfltest phc2sys: [796.113] selecting CLOCK_REALTIME as > the master clock > Oct 12 09:38:46 nfltest phc2sys: [855.123] rms 2255 max 10593 freq > +15526 +/- 1496 delay 4882 +/- 17 > Oct 12 09:39:46 nfltest phc2sys: [915.132] rms 660 max 3155 freq > +18638 +/- 822 delay 4871 +/- 29 > Oct 12 09:40:46 nfltest phc2sys: [975.142] rms 129 max 639 freq > +18252 +/- 226 delay 4877 +/- 19 > Oct 12 09:41:46 nfltest phc2sys: [1035.152] rms 61 max 277 freq > +18399 +/- 121 delay 4872 +/- 25 > Oct 12 09:42:47 nfltest phc2sys: [1095.163] rms 555 max 2744 freq > +20438 +/- 1261 delay 4881 +/- 19 > Fri Oct 12 09:43:29 UTC 2018 > system and phc clock time offset request okay > system time: 1539337409.533893155 > phc time: 1539337446.540269592 > system time: 1539337409.533898045 > system/phc clock time offset is -37006373992 ns > system clock time delay is 4890 ns > Oct 12 09:43:47 nfltest phc2sys: [1155.173] rms 16 max 34 freq > +21174 +/- 14 delay 4881 +/- 17 > Oct 12 09:44:47 nfltest phc2sys: [1215.183] rms 51 max 225 freq > +21045 +/- 116 delay 4880 +/- 22 > Oct 12 09:45:47 nfltest phc2sys: [1275.193] rms 17 max 47 freq > +20949 +/- 15 delay 4875 +/- 21 > Oct 12 09:46:47 nfltest phc2sys: [1335.203] rms 1034 max 5190 freq > +23152 +/- 2651 delay 4883 +/- 18 > Oct 12 09:47:47 nfltest phc2sys: [1395.214] rms 15 max 39 freq > +26143 +/- 13 delay 4880 +/- 24 > Fri Oct 12 09:48:48 UTC 2018 > system and phc clock time offset request okay > system time: 1539337728.128369907 > phc time: 1539337765.141984280 > system time: 1539337728.128374837 > system/phc clock time offset is -37013611908 ns > system clock time delay is 4930 ns > On Fri, 12 Oct 2018 at 09:35, Miroslav Lichvar <mlich...@redhat.com> wrote: > > > > On Thu, Oct 11, 2018 at 09:53:37PM +0200, Joanna wrote: > > > Hi, > > > I am having a Centos server that is a PTP grandmaster for systems in my > > > network. > > > The server is getting the time using NTP (chrony) from interface eth0 > > > and acts as a PTP grandmaster on interface eth1. The requirement is > > > that the server and other systems on eth1 network are in sync (phc and > > > sys time). I am using ptp4l for PTP syncronization and phc2sys to sync > > > clocks. The problem is that the sys time and phc time on the server > > > are drifting apart by around 70ms per hour. > > > > That suggests phc2sys is not working as expected. Can you please > > post its output? > > > > > I am setting the phc to UTC with 37 seconds offset after boot: > > > testptp -s > > > testptp -t 37 > > > PTP and phc2sys options are as follows: > > > ptp4l -f /etc/ptp4l.conf -i eth1 > > > phc2sys -a -r -r > > > > -- > > Miroslav Lichvar
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
