On Wed, Aug 13, 2008 at 4:33 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
quoted text
>
> Things really _have_ calmed down, and hopefully we've also resolved a lot
> of the regressions in -rc3.

I found a new one in -rc3 vs. -rc2.
Only one of my cpus seems to powered down by cpufreq, because the
topology gets filled out wrong:

correct with -rc2:
#grep . /sys/devices/system/cpu/cpu*/cpufreq/affected_cpus
/sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0 1
/sys/devices/system/cpu/cpu1/cpufreq/affected_cpus:0 1
/sys/devices/system/cpu/cpu2/cpufreq/affected_cpus:2 3
/sys/devices/system/cpu/cpu3/cpufreq/affected_cpus:2 3
(The system has 2 dual core Opterons)

wrong with -rc3:
#grep . /sys/devices/system/cpu/cpu*/cpufreq/affected_cpus
/sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0 1
/sys/devices/system/cpu/cpu1/cpufreq/affected_cpus:0 1
/sys/devices/system/cpu/cpu2/cpufreq/affected_cpus:0 1
/sys/devices/system/cpu/cpu3/cpufreq/affected_cpus:0 1

I bisected this bug down to these commits:
quoted text
> Mark Langsdorf (2):
>      [CPUFREQ][1/2] whitespace fix for powernow-k8
>      [CPUFREQ][2/2] preregister support for powernow-k8

HTH

Torsten
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/