Yo Miroslav!
On Fri, 6 Mar 2015 12:45:50 +0100
Miroslav Lichvar <mlich...@redhat.com> wrote:
> On Wed, Mar 04, 2015 at 12:16:48PM -0800, Gary E. Miller wrote:
> > Which still leaves me with slave PHC clocks that either go crazy or
> > have huge offsets...
>
> Another thought, is it possible that the PTP master is using HW
> timestamping with a PTP clock that is not synchronized to anything?
Nope. My master is PPS controlled, and only running in SW timestamping
mode.
I have other PPS NTP servers on the same net dboule checking each
other and I get Icinga alerts if any lose lock.
> If
> it was set on driver initialization from the system clock which is set
> on boot from the RTC with one second resolution, it would explain the
> offsets up to 1 second nicely.
I reboot my master about every 6 months.
My offset errors occasionally go way past 1 second.
On one test slave I have the PTP HW set to noselect, but it will still
get selected occasionally, then boom, time races to 30, 60, 90 seconds
off before chrony deslects the device.
On another PTP HW slave, different NIC type, the offset from PHC time
to PPS time wanders +/- 800 mSec.
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
g...@rellim.com Tel:+1(541)382-8588
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
