Re: powernow-k8: transition frequency failed

[Jay Wineinger <jay.wineinger@xxxxxxxxx>]

Hi again,

I believe I've been able to resolve this by performing a BIOS update
on my motherboard.  I confess ignorance about how all of this works,
but it would appear that my motherboard didn't know enough about my
CPU to use it correctly.  Before the BIOS update, /proc/cpuinfo and
other tools would just tell me that I was using an unknown or generic
(I can't remember the wording) AMD processor; after the update, it
correctly identifies my "AMD Phenom(tm) II X6 1055T Processor". Also,
before the update only 3 frequency steps were available: 2.80 GHz,
2.20 GHz, 800 MHz;  Now a fourth is available and all of them are
being used: 2.80 GHz, 2.20 GHz, 1.50 GHz, 800 MHz.  And finally, I am
not receiving the mentioned messages in me kern.log anymore.

Jay

On Sat, Mar 17, 2012 at 4:15 PM, Jay Wineinger <jay.wineinger@xxxxxxxxx> wrote:
> Hi,
>
> My kern.log is getting spammed with about 20 "powernow-k8: transition
> frequency failed" messages per second. Is there a fix for this?  I've got a
> AMD Phenom II X6 1055T (2.8GHz).
>
> thanks!
> Jay Wineinger
>
>
> Here is some info about my system. I'm happy to provide more, I just don't
> know what would be useful.  Ubuntu 11.10 system.
>
> Linux black-tower 3.0.0-16-generic-pae #28-Ubuntu SMP Fri Jan 27 19:24:01
> UTC 2012 i686 athlon i386 GNU/Linux
>
> cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
> Report errors and bugs to cpufreq@xxxxxxxxxxxxxxx, please.
> analyzing CPU 0:
>   driver: powernow-k8
>   CPUs which run at the same hardware frequency: 0
>   CPUs which need to have their frequency coordinated by software: 0
>   maximum transition latency: 8.0 us.
>   hardware limits: 800 MHz - 2.80 GHz
>   available frequency steps: 2.80 GHz, 2.20 GHz, 800 MHz
>   available cpufreq governors: conservative, ondemand, userspace, powersave,
> performance
>   current policy: frequency should be within 800 MHz and 2.80 GHz.
>                   The governor "ondemand" may decide which speed to use
>                   within this range.
>   current CPU frequency is 2.20 GHz (asserted by call to hardware).
>   cpufreq stats: 2.80 GHz:10.26%, 2.20 GHz:89.74%, 800 MHz:0.00%  (57485)
> analyzing CPU 1:
>   driver: powernow-k8
>   CPUs which run at the same hardware frequency: 1
>   CPUs which need to have their frequency coordinated by software: 1
>   maximum transition latency: 8.0 us.
>   hardware limits: 800 MHz - 2.80 GHz
>   available frequency steps: 2.80 GHz, 2.20 GHz, 800 MHz
>   available cpufreq governors: conservative, ondemand, userspace, powersave,
> performance
>   current policy: frequency should be within 800 MHz and 2.80 GHz.
>                   The governor "ondemand" may decide which speed to use
>                   within this range.
>   current CPU frequency is 2.20 GHz (asserted by call to hardware).
>   cpufreq stats: 2.80 GHz:11.12%, 2.20 GHz:88.88%, 800 MHz:0.00%  (52929)
> analyzing CPU 2:
>   driver: powernow-k8
>   CPUs which run at the same hardware frequency: 2
>   CPUs which need to have their frequency coordinated by software: 2
>   maximum transition latency: 8.0 us.
>   hardware limits: 800 MHz - 2.80 GHz
>   available frequency steps: 2.80 GHz, 2.20 GHz, 800 MHz
>   available cpufreq governors: conservative, ondemand, userspace, powersave,
> performance
>   current policy: frequency should be within 800 MHz and 2.80 GHz.
>                   The governor "ondemand" may decide which speed to use
>                   within this range.
>   current CPU frequency is 2.80 GHz (asserted by call to hardware).
>   cpufreq stats: 2.80 GHz:21.62%, 2.20 GHz:78.38%, 800 MHz:0.00%  (36056)
> analyzing CPU 3:
>   driver: powernow-k8
>   CPUs which run at the same hardware frequency: 3
>   CPUs which need to have their frequency coordinated by software: 3
>   maximum transition latency: 8.0 us.
>   hardware limits: 800 MHz - 2.80 GHz
>   available frequency steps: 2.80 GHz, 2.20 GHz, 800 MHz
>   available cpufreq governors: conservative, ondemand, userspace, powersave,
> performance
>   current policy: frequency should be within 800 MHz and 2.80 GHz.
>                   The governor "ondemand" may decide which speed to use
>                   within this range.
>   current CPU frequency is 2.20 GHz (asserted by call to hardware).
>   cpufreq stats: 2.80 GHz:23.84%, 2.20 GHz:76.16%, 800 MHz:0.00%  (46789)
> analyzing CPU 4:
>   driver: powernow-k8
>   CPUs which run at the same hardware frequency: 4
>   CPUs which need to have their frequency coordinated by software: 4
>   maximum transition latency: 8.0 us.
>   hardware limits: 800 MHz - 2.80 GHz
>   available frequency steps: 2.80 GHz, 2.20 GHz, 800 MHz
>   available cpufreq governors: conservative, ondemand, userspace, powersave,
> performance
>   current policy: frequency should be within 800 MHz and 2.80 GHz.
>                   The governor "ondemand" may decide which speed to use
>                   within this range.
>   current CPU frequency is 2.80 GHz (asserted by call to hardware).
>   cpufreq stats: 2.80 GHz:39.87%, 2.20 GHz:60.13%, 800 MHz:0.00%  (73006)
> analyzing CPU 5:
>   driver: powernow-k8
>   CPUs which run at the same hardware frequency: 5
>   CPUs which need to have their frequency coordinated by software: 5
>   maximum transition latency: 8.0 us.
>   hardware limits: 800 MHz - 2.80 GHz
>   available frequency steps: 2.80 GHz, 2.20 GHz, 800 MHz
>   available cpufreq governors: conservative, ondemand, userspace, powersave,
> performance
>   current policy: frequency should be within 800 MHz and 2.80 GHz.
>                   The governor "ondemand" may decide which speed to use
>                   within this range.
>   current CPU frequency is 2.20 GHz (asserted by call to hardware).
>   cpufreq stats: 2.80 GHz:25.12%, 2.20 GHz:74.88%, 800 MHz:0.00%  (51039)
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html