Building cpufreq modules into F16 kernel is it right or wrong?

alekcejk at alekcejk at
Tue Oct 18 20:52:21 UTC 2011

Adam Jackson wrote:

> 4.2.27 makestep
> ---------------
> Normally chronyd will cause the system to gradually correct any time
> offset, by slowing down or speeding up the clock as required.  In
> certain situations, the system clock may be so far adrift that this
> slewing process would take a very long time to correct the system clock.
>    This directive forces `chronyd' to step system clock if the
> adjustment is larger than a threshold value, but only if there were no
> more clock updates since `chronyd' was started than a specified limit
> (a negative value can be used to disable the limit).
>    This is particularly useful when using reference clocks, because the
> `initstepslew' directive (*note initstepslew directive::) works only
> with NTP sources.
>    An example of the use of this directive is
>      makestep 1000 10
>    This would step system clock if the adjustment is larger than 1000
> seconds, but only in the first ten clock updates.
> ---
> - ajax

Thanks, I will try makestep directive with F16 kernel.
This is workaround may work or may not because chrony not always available.
For example chrony can be not installed on Live images (not from Fedora) or
other systems which don't have chrony.

The real solution can be adding kernel parameter like cpufreq=disable
that can disable using built-in cpufreq modules.
Alexey Kurov <nucleo at>

More information about the devel mailing list