From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "pavel@ucw.cz" <pavel@ucw.cz>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Zhang, Rui" <rui.zhang@intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"ibm-acpi-devel@lists.sourceforge.net"
<ibm-acpi-devel@lists.sourceforge.net>,
"ibm-acpi@hmh.eng.br" <ibm-acpi@hmh.eng.br>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: v4.8-rc1: thinkpad x60: running at low frequency even during kernel build
Date: Sat, 5 Nov 2016 13:55:22 +0000 [thread overview]
Message-ID: <1478354115.19557.17.camel@intel.com> (raw)
In-Reply-To: <20161105133719.GA3933@amd>
On Sat, 2016-11-05 at 14:37 +0100, Pavel Machek wrote:
> Hi!
>
> >
> > [...]
> >
> > >
> > > So we seem to have thermal or ACPI regression in v4.9-rc3.
> > >
> > It is possible. Can you add either add printk
> > in acpi_processor_ppc_has_changed() or use ftrace and see do you
> > get to
> > these functions
> >
> > acpi_processor_ppc_init()
> > acpi_processor_ppc_has_changed()
> > acpi_processor_ppc_notifier()
> >
> > ?
>
> Yes, these seem to be called. Here's the log:
Try this
1. Either enable dyndebug or add
#define DEBUG 1
at the top of acpi-cpufreq.c
2.
diff --git a/drivers/acpi/processor_perflib.c
b/drivers/acpi/processor_perflib.c
index bb01dea..6074995 100644
--- a/drivers/acpi/processor_perflib.c
+++ b/drivers/acpi/processor_perflib.c
@@ -94,9 +94,14 @@ static int acpi_processor_ppc_notifier(struct
notifier_block *nb,
ppc = (unsigned int)pr->performance_platform_limit;
+ printk(KERN_ERR "ppc = %d\n", ppc);
+
if (ppc >= pr->performance->state_count)
goto out;
+ printk(KERN_ERR "ppc = %d freq-limit %d\n", ppc, pr-
>performance->states[ppc].
+ core_frequency * 1000);
+
cpufreq_verify_within_limits(policy, 0,
pr->performance->states[ppc].
core_frequency * 1000);
Thanks,
Srinivas
next prev parent reply other threads:[~2016-11-05 13:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 8:38 v4.8-rc1: thinkpad x60: running at low frequency even during kernel build Pavel Machek
2016-11-04 8:58 ` Pavel Machek
2016-11-04 9:10 ` Viresh Kumar
2016-11-04 9:26 ` Pavel Machek
2016-11-04 9:31 ` Viresh Kumar
2016-11-05 18:21 ` Henrique de Moraes Holschuh
2016-11-05 19:24 ` Thinkpad power management (was Re: v4.8-rc1: thinkpad x60: running at low frequency even during kernel build) Pavel Machek
2016-11-04 14:05 ` v4.8-rc1: thinkpad x60: running at low frequency even during kernel build Pandruvada, Srinivas
2016-11-04 20:44 ` Pavel Machek
2016-11-04 21:13 ` Pandruvada, Srinivas
2016-11-05 8:42 ` Pavel Machek
2016-11-05 17:46 ` Henrique de Moraes Holschuh
2016-11-05 19:36 ` Pavel Machek
2016-11-06 3:45 ` Henrique de Moraes Holschuh
2016-11-04 22:16 ` Pavel Machek
2016-11-04 23:20 ` Pandruvada, Srinivas
2016-11-05 13:20 ` Pavel Machek
2016-11-05 13:33 ` Pandruvada, Srinivas
2016-11-05 13:53 ` Pavel Machek
2016-11-05 14:04 ` Pavel Machek
2016-11-05 14:19 ` Pandruvada, Srinivas
2016-11-05 15:34 ` Pavel Machek
2016-11-05 13:37 ` Pavel Machek
2016-11-05 13:55 ` Pandruvada, Srinivas [this message]
2016-11-05 14:21 ` Pavel Machek
2016-11-05 20:31 ` Pavel Machek
2016-11-09 11:34 ` thinkpad x60, T40p: overheat with v4.9-rc4 (was Re: v4.8-rc1: thinkpad x60: running at low frequency even during kernel build) Pavel Machek
2016-11-14 19:03 ` 6ea8c546f3655 breaks thermal management on thinkpad x60 and t40p Pavel Machek
2016-11-14 19:54 ` Rafael J. Wysocki
2016-11-05 18:04 ` v4.8-rc1: thinkpad x60: running at low frequency even during kernel build Henrique de Moraes Holschuh
2016-11-05 19:56 ` Pavel Machek
2016-11-05 11:21 ` Zhang Rui
2016-11-05 13:10 ` Pavel Machek
2016-11-05 12:22 ` Pavel Machek
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=1478354115.19557.17.camel@intel.com \
--to=srinivas.pandruvada@intel.com \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=viresh.kumar@linaro.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).