On Sat, Nov 12, 2016 at 10:36:55AM -0800, Denny Page wrote:
> Here is a reasonable visual representation of what I am seeing. The section
> on the left (before 8:00) is with hardware timestamping, while the section on
> the right is with software timestamping. maxdelaydevratio of 4 in both cases.
> I think I have a kernel/driver problem.
I think I see something similar. Occasional spikes that are causing
resets of the HW clock instance. It looks like a chrony bug.
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe"
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the
Trouble? Email listmas...@chrony.tuxfamily.org.