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 ntpshmmon tool from gpsd to see that phc2sys is writing new samples in both directions. > The only problem is caused by ntpd reset - it starts synchronizing to PTP > (ntpshm) even if it shouldn't as is it Master. If you have multiple sources configured for ntpd, it could be rejecting the SHM as a falseticker when the TAI-UTC correction in phc2sys flips. On a restart/reset and depending on the polling intervals, it could temporarily select the SHM source for synchronization and later reject it again. Try it with SHM as the only source. That should make it obvious that this cannot work. -- Miroslav Lichvar _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
