On Sunday, March 24, 2013 07:59:35 PM Viresh Kumar wrote: > On 24 March 2013 19:41, Maciej Rutecki <maciej.rutecki@xxxxxxxxx> wrote: > > (long e-mail, sorry ;-)) > > Don't be, it was useful :) > > > Last known good: 3.8.0 > > > > Short description: > > 1. On -rc3, after s2ram cpufreq does not set CPU on max frequency on high > > load (on battery). > > Try attached patch for this. > > > 2. On -rc4 (this is not real regression because I change config between -rc3 > > and rc4), "ondemand" does not work. Current frequency is 'strange' (792 > > MHz). > > I don't really have a reason for that :( > But with your config it is clear that, your working setup has: > > # CONFIG_X86_INTEL_PSTATE is not set > # CONFIG_X86_PCC_CPUFREQ is not set > CONFIG_X86_ACPI_CPUFREQ=m > > and rc4 version has: > > CONFIG_X86_INTEL_PSTATE=y > CONFIG_X86_PCC_CPUFREQ=m > CONFIG_X86_ACPI_CPUFREQ=m > > So, i believe you are using another cpufreq driver this, try with same > configuration once. > > > 1. Kernel 3.8.0: > > > > Output (show only fisrt CPU, others are same): > > cpu0/cpufreq//affected_cpus:0 > > cpu0/cpufreq//related_cpus:0 1 2 3 > > > Kernel 3.9.0-rc1 > > > CASE 2 > > After boot: > > cpu0/cpufreq//affected_cpus:0 1 2 3 > > cpu0/cpufreq//related_cpus:0 1 2 3 > > My attached patch will restore 1. instead of CASE 2. > > > =============================================================================== > > Kernel 3.9.0-rc4 > > > > CASE 7 > > (normal boot) > > cpu0/cpufreq//affected_cpus:0 > > cpu0/cpufreq//related_cpus:0 > > This must be related to your different driver. Yes, intel_pstate is not really a cpufreq driver. It just overtakes the whole subsystem. Dirk, can you please check if this is as intended? Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- 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
