On Mon, Dec 21, 2015 at 12:10 AM, Jon Masters <[email protected]> wrote: > On 12/2/15, 6:55 PM, John Stultz wrote: >> >> On Wed, Dec 2, 2015 at 3:42 PM, Andy Lutomirski <[email protected]> wrote: > > >>>> On a hunch, are you running chrony instead of ntpd? >>> >>> >>> Yes, this is indeed chrony. >> >> >> Ok. I'll have to look closer. The last time that message came up it >> was in a report of a bug that chrony uncovered with the internal >> correction being too slow. I know chrony is much more aggressive >> compared to ntpd in tweaking the freq value for the initial converging >> correction at startup, so maybe that along with something else is >> causing us to get out of spec. > > > Can you copy me on followup? I'm seeing similar behavior with chrony on > recent kernels on a couple of different ARM server prototype systems.
A patch for this just landed in tip/timers/core and is pending for 4.5 http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=ec02b076ceab63f99e5b3d80fd223d777266c236 thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
