Thanks Jake,
You are right on the money. I changed the time by a few seconds and it
worked.
On Wed, Jul 11, 2018 at 4:35 PM Keller, Jacob E <jacob.e.kel...@intel.com>
wrote:
> > -----Original Message-----
> > From: Maxime Lemonnier [mailto:maxime.lemonn...@gmail.com]
> > Sent: Wednesday, July 11, 2018 1:21 PM
> > To: linuxptp-users@lists.sourceforge.net
> > Subject: [Linuxptp-users] Fwd: Stuck in the 70s: Need Help with
> phc2sys/ptp4l
> >
> > Anyways, I rebooted the slave, and set the master on ntp, and now the
> slave is
> > back to the present.
> >
> > If I temporaly disable ntp, and change the clock on the master (e.g. -/+
> 3
> > minutes), the slave is not updated unless I restart:
> > - master's ptp4l
> > - slave's ptp4l
> > - slave's phc2sys
> >
> > Which kind defeat the point of using a time protocol.
> >
>
> The slave is going to use frequency tuning to syntonize with the master,
> rather than direct clock jumps. In practice, the masters are unlikely to
> have huge time jumps like this, and a stable monotonically increasing clock
> is more useful.
>
> There should be some configurations you can set so that it will do a clock
> jump when the difference is higher than some threshold. By default, I
> believe it only jumps at the start.
>
> Thanks,
> Jake
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
