From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
"Dirk Brandewie" <dirk.brandewie@gmail.com>,
linux-acpi@vger.kernel.org,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"Linux PM list" <linux-pm@vger.kernel.org>,
"Dirk Brandewie" <dirk.j.brandewie@intel.com>
Subject: Re: 3.9.0 + CONFIG_X86_INTEL_PSTATE=y -> ThinkPad T420 with i5 lost ACPI functionality
Date: Fri, 03 May 2013 14:10:44 -0700 [thread overview]
Message-ID: <518427D4.3050104@gmail.com> (raw)
In-Reply-To: <3715884.H8PIhhjRXL@vostro.rjw.lan>
On 05/03/2013 12:36 PM, Rafael J. Wysocki wrote:
> On Friday, May 03, 2013 06:55:37 PM Toralf Förster wrote:
>> The following file doesn't exists at my Gentoo Linux
>> /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load
>> in 3.9.0 if I activate CONFIG_X86_INTEL_PSTATE=y
>>
>> That means, that a command like
>>
>> $> echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load
>>
>> in /etc/rc.local is now no longer working.
>> A high fan + high temperature are the result, even if just the BOINC client
>> is run with low prio (nice 19) in the back ground.
>>
ignore_nice_load is a feature of the ondemand governor.
The intel_pstate driver is seeing the load presented by the BOINC client and
is adjusting the pstate accordingly.
>> Manually loading the missing module won't work too :
>>
>> $> modprobe acpi_cpufreq
>> modprobe: ERROR: could not insert 'acpi_cpufreq': Device or resource busy
>>
>> Is the behaviour a bug or a feature ?
The intel_pstate drive has already registered as a scaling driver so when
acpi_cpufreq tries to register as a scaling driver the registration fails
>
> The thermal management problem is not an intentional outcome, definitely.
>
>> In the later case: How can I achieve the previous behaviour back ?
>>
If you require the ondemand governor you can remove CONFIG_X86_INTEL_PSTATE
from your configuration or add "intel_pstate=disable" to your kernel command
line.
--Dirk
>> This issue might affect the RH EL kernel too [1] where I observed a similar behaviour.
>>
>>
>> [1] http://elrepo.org/bugs/view.php?id=379
>
> Dirk, is this the problem we were talking about recently or something else?
>
> Rafael
>
>
next prev parent reply other threads:[~2013-05-03 21:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 16:55 3.9.0 + CONFIG_X86_INTEL_PSTATE=y -> ThinkPad T420 with i5 lost ACPI functionality Toralf Förster
2013-05-03 19:36 ` Rafael J. Wysocki
2013-05-03 19:36 ` Rafael J. Wysocki
2013-05-03 21:10 ` Dirk Brandewie [this message]
2013-05-03 21:26 ` Toralf Förster
2013-05-03 21:43 ` Dirk Brandewie
[not found] ` <51842F6F.1050005-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-05-04 7:57 ` Toralf Förster
2013-05-04 7:57 ` Toralf Förster
2013-05-10 13:10 ` Rafael J. Wysocki
2013-05-10 13:10 ` Rafael J. Wysocki
2013-05-13 16:43 ` Dirk Brandewie
2013-05-13 16:43 ` Dirk Brandewie
2013-05-13 17:20 ` Toralf Förster
2013-05-13 17:57 ` Dirk Brandewie
2013-05-13 19:13 ` Toralf Förster
2013-05-13 19:24 ` Dirk Brandewie
2013-05-13 19:24 ` Dirk Brandewie
2013-05-28 18:11 ` Toralf Förster
2013-07-07 8:44 ` Toralf Förster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=518427D4.3050104@gmail.com \
--to=dirk.brandewie@gmail.com \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=toralf.foerster@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.