Hello, Just for reference: after making sure all config files were identical and upgrading all machines to linuxptp 2.0, the issue is gone and i can leave the utc_offset on its default value. Thanks for the help !
Frank On Tue, Feb 12, 2019 at 10:01 PM Richard Cochran <richardcoch...@gmail.com> wrote: > On Tue, Feb 12, 2019 at 09:09:28AM +0100, Frank Dekervel wrote: > > I worked around the issue now by setting utc_offset to 0. that's not a > > proper fix, so i'm still trying to find out where the UTC time comes > from, > > i'm going to review all configfiles now. > > You got me worried, and so I tried a similar setup here: > > - PC master clock with i210 (HW timestamping) > - netbook slave with r8169 (SW timestamping) > > Turned off NTP on the netbook. > > On the PC: > > phc2sys -a -r -r -m -q > ptp4l -m -q -i eth6 > > On the netbook: > > ptp4l -m -q -S -s -i eth0 > > The initial 2.5 millisecond offset corrected within about 60 seconds > run time. So try these commands (without config files). It should > just work. > > Thanks, > Richard > >
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
