Re: [Linuxptp-users] gPTP issues with ntpd

2022-07-21 Thread Miroslav Lichvar
On Thu, Jul 21, 2022 at 02:13:29PM +0200, Jakub Raczyński wrote: > My interpretation is based only on ntpshmmon tool - it clearly shows that > ntpshm servo is only fed when PTP portState is set to Slave. So it is used > only to write to the segment, but phc2sys clearly controls when it is done.

Re: [Linuxptp-users] gPTP issues with ntpd

2022-07-21 Thread Jakub Raczyński
> 21.07.2022 13:06 Miroslav Lichvar wrote: > > > On Thu, Jul 21, 2022 at 12:41:54PM +0200, Jakub Raczyński wrote: > > > 21.07.2022 10:20 Miroslav Lichvar wrote: > > > No, that's not correct. Try running the ntpshmmon tool from gpsd to > > > see that phc2sys is writing new samples in both direc

Re: [Linuxptp-users] gPTP issues with ntpd

2022-07-21 Thread Miroslav Lichvar
On Thu, Jul 21, 2022 at 12:41:54PM +0200, Jakub Raczyński wrote: > > 21.07.2022 10:20 Miroslav Lichvar wrote: > > No, that's not correct. Try running the ntpshmmon tool from gpsd to > > see that phc2sys is writing new samples in both directions. > > You are mistaken, I did try ntpshmmon and it do

Re: [Linuxptp-users] gPTP issues with ntpd

2022-07-21 Thread Jakub Raczyński
> 21.07.2022 10:20 Miroslav Lichvar wrote: > > > On Wed, Jul 20, 2022 at 05:57:57PM +0200, Jakub Raczyński wrote: > > So this setup seems to be correct and from the phc2sys log I sent > > previously it seems to be. So it seems that phc2sys is correctly writing > > timestamps to ntpshm only wh

Re: [Linuxptp-users] gPTP issues with ntpd

2022-07-21 Thread Miroslav Lichvar
On Wed, Jul 20, 2022 at 05:57:57PM +0200, Jakub Raczyński wrote: > So this setup seems to be correct and from the phc2sys log I sent previously > it seems to be. So it seems that phc2sys is correctly writing timestamps to > ntpshm only when it is Slave. No, that's not correct. Try running the nt

Re: [Linuxptp-users] gPTP issues with ntpd

2022-07-20 Thread Jakub Raczyński
wrote: > > > > 20.07.2022 15:23 Miroslav Lichvar write: > > > > > > On Wed, Jul 20, 2022 at 03:12:39PM +0200, Jakub Raczyński wrote: > > > phc2sys[2031.823]: lan1 sys offset 4870 s0 freq +0 delay 1875 > > > phc2sys[2032.824]: lan1 sys offset 4915 s0 freq +0 delay 187

Re: [Linuxptp-users] gPTP issues with ntpd

2022-07-20 Thread Jakub Raczyński
> 20.07.2022 15:23 Miroslav Lichvar write: > > > On Wed, Jul 20, 2022 at 03:12:39PM +0200, Jakub Raczyński wrote: > > phc2sys[2031.823]: lan1 sys offset 4870 s0 freq +0 delay 1875 > > phc2sys[2032.824]: lan1 sys offset 4915 s0 freq +0 delay 1875 > > phc2sys[2033.824]: la

Re: [Linuxptp-users] gPTP issues with ntpd

2022-07-20 Thread Miroslav Lichvar
On Wed, Jul 20, 2022 at 03:12:39PM +0200, Jakub Raczyński wrote: > phc2sys[2031.823]: lan1 sys offset 4870 s0 freq +0 delay 1875 > phc2sys[2032.824]: lan1 sys offset 4915 s0 freq +0 delay 1875 > phc2sys[2033.824]: lan1 sys offset 5011 s0 freq +0 delay 1750 > phc2

Re: [Linuxptp-users] gPTP issues with ntpd

2022-07-20 Thread Jakub Raczyński
wrote: > > > > 20.07.2022 13:33 Miroslav Lichvar wrote: > > > > > > On Wed, Jul 20, 2022 at 12:06:43PM +0200, Jakub Raczyński wrote: > > > I was trying to setup gPTP using linuxptp (ptp4l + phc2sys) that would > > > allow two way synchronization using ntpd. Setup without ntpd > > > (sync

Re: [Linuxptp-users] gPTP issues with ntpd

2022-07-20 Thread Jakub Raczyński
> 20.07.2022 13:33 Miroslav Lichvar wrote: > > > On Wed, Jul 20, 2022 at 12:06:43PM +0200, Jakub Raczyński wrote: > > I was trying to setup gPTP using linuxptp (ptp4l + phc2sys) that would > > allow two way synchronization using ntpd. Setup without ntpd (synchronizing > > CLOCK_REALTIME) see

Re: [Linuxptp-users] gPTP issues with ntpd

2022-07-20 Thread Miroslav Lichvar
On Wed, Jul 20, 2022 at 12:06:43PM +0200, Jakub Raczyński wrote: > I was trying to setup gPTP using linuxptp (ptp4l + phc2sys) that would allow > two way synchronization using ntpd. Setup without ntpd (synchronizing > CLOCK_REALTIME) seems to be working perfectly. > However with ntpd is that wh