Re: [Linuxptp-users] clockcheck - need to filter large spurious phase jumps?

[Miroslav L. <mli...@re...>]

On Wed, Nov 06, 2013 at 12:13:57AM +0000, Keller, Jacob E wrote:
> On Tue, 2013-11-05 at 18:50 -0500, Rich Schmidt wrote:
> > Well, it is a jump of 19.55 hours in the last example that you note.
> > We would notice that on the GrandMaster.    These jumps happen four or
> > 5 times per hour at random times.  I am using a newer e1000e driver
> > than the sourceforge driver (oh, oh).  From the Intel site,
> > 2.5.4-NAPI. I will try the sourceforge version next. 

> If the Grand Master is having these jumps, there's no way to filter
> them.. that is the remote clock simply being jumped, and we can't
> "filter" it, because what we do is reset the servo, and then relock on
> the new target. It looks like a "you should filter this out" but in
> reality the values you see are the time offset from the master, not the
> current time.

It's not the Grand Master jumping as the sanity check includes the
corrections made by the local servo. If there is a warning it means
something else is touching the synchronized clock or the clock/driver
is broken.

-- 
Miroslav Lichvar