linux-kernel - Re: [REGRESSION] [CPUFREQ] 3.9.0-rcX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKohpokBySA5uaTTAwF5tmUr-_+W04Ki_f6cWTLu7n1C3Tcqog@mail.gmail.com>
Date:	Sun, 24 Mar 2013 19:59:35 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Maciej Rutecki <maciej.rutecki@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, cpufreq@...r.kernel.org,
	linux-pm@...r.kernel.org
Subject: Re: [REGRESSION] [CPUFREQ] 3.9.0-rcX

On 24 March 2013 19:41, Maciej Rutecki <maciej.rutecki@...il.com> 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.

> Config, dmesg:
> http://mrutecki.pl/download/kernel/3.9.0-rc4/cpufreq/

These were very important and helpful.

Download attachment "0001-cpufreq-acpi-cpufreq-Don-t-set-policy-related_cpus-f.patch" of type "application/octet-stream" (1935 bytes)