On Sat, Aug 06, 2011 at 04:24:14PM +0200, Dominik Brodowski wrote: > Hey, > > On Fri, Aug 05, 2011 at 06:01:47PM -0400, Matt Turner wrote: > > On Sun, Jul 31, 2011 at 4:57 AM, Dominik Brodowski > > <linux@xxxxxxxxxxxxxxxxxxxx> wrote: > > > Hey, > > > > > > On Sun, Jul 31, 2011 at 12:46:31AM -0400, Matt Turner wrote: > > >> I've got a bug report about cpufreq-set -r not setting all related > > >> CPUs. It appears to be a problem with AMD CPUs only. > > >> > > >> https://bugs.gentoo.org/show_bug.cgi?id=376565 > > >> > > >> Any ideas what's going on? > > > > > > What's the output of cpufreq-info on these systems? Might it be that the > > > CPUs on this AMD system may be set to different frequencies? "-r" only sets > > > the governor on all _related_ CPUs, not on all CPUs found on the system. > > > > > > Best, > > > Dominik > > > > Hi Dominik, > > > > Juergen posted some output in > > https://bugs.gentoo.org/show_bug.cgi?id=376565 and I think also sent > > it to you. > > > > It looks to me like either the CPU isn't required to use the same > > frequency for all cores, or it's a kernel bug reporting incorrect > > information to cpufrequtils. What do you think? > > cpufreq assumes the former. If > > /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus and > /sys/devices/system/cpu/cpu0/cpufreq/related_cpus > > do report something else than "0", though, then there's a bug in > cpufrequtils. If more than one CPU is required to use the same frequency, > it's a kernel bug/regression... > > I tend to add an "-a" option to set all CPUs, though (cpupowerutils only). *doh* It is already available: $ cpupower -c all frequency-set -g powersave Best, Dominik -- 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
