Re: [chrony-users] How to avoid oversteering

[Ariel Garcia <a.garcia@xxxxxxxxxx>]

> > i am trying to get Chrony 3.2 running without stepping the clock, but i
> > find that it oversteers by a huge amount.  I observe that it starts
> > driving
> > the system clock to the right value, but then moves it more that the
> > initial offset in the opposite direction, and starts "oscillating".
> 
> This looks like a broken system clock. chronyd is telling the kernel
> to slow down or speed up the clock, but it doesn't happen.
> 
> What kernel version is the board running? There was a bug which caused
> issues like that and it was fixed few years ago. IIRC it was specific
> to 32-bit platforms.

Thanks for you feedback!
You probably mean this one?
	https://bugzilla.redhat.com/show_bug.cgi?id=1188074

I'm running 4.2.8 32bit (embedded device...)
I will recompile chrony adding some debugging for the frequency it tries to 
set,  my impression is also that the clock stays always at plus or minus the 
max frequency drift, once chrony starts to touch it.

On the other hand, i already tried Bill Unruh's hint:

> Alternatively it could be a severe hardware issue, or you could be running
> the system on a tickless clock.
 
i recompiled the kernel with ticks (and without power governors/frequency 
drivers, just performance) but it did not help.

Thanks!


-- 
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.