HP/Compaq nx6325 clock "jumping around"
brde at optusnet.com.au
Sat Jul 5 02:12:15 UTC 2008
On Fri, 4 Jul 2008, Nate Lawson wrote:
>> On Wed, 2 Jul 2008, Joerg Wunsch wrote:
> Bruce Evans wrote:
>> I know of the following bugs in time on nx6325:
> This reminds me -- the algorithm for estimating the cpu frequency needs
> improvement. You had a patch you sent me that reduced its error by a lot.
> Would you commit it?
I'm further than ever from committing this, since I'm not set up for svn.
I never merged this to the kernel. Running it in userland on more SMP
machines shows the expected problems from the CPU not being pinnable in
>> dev.cpu.0.freq: 1985
>> dev.cpu.0.freq_levels: 1985/-1 1736/-1 1488/-1 1240/-1 992/-1 744/-1 496/-1
>> Once I used some performance/power-reduction config and got a list like
>> 1985 actually gives 1995 MHz.
> Your freq estimation patch does better than this.
Aren't the above frequencies just read from acpi read-only data?
I forgot to mention another MI problem with cpu_ticker frequency
recalibration: its sanity checks don't detect even the enormous transient
garbage caused by stopping clocks. Apparently all the clocks used in
the sanity checks are stopped too synchronously. Otherwise, the
recalibration is very accurate.
More information about the freebsd-acpi