linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
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 14:20:49 +0100	[thread overview]
Message-ID: <20161105132049.GC10310@amd> (raw)
In-Reply-To: <1478301649.7947.3.camel@intel.com>

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

On Fri 2016-11-04 23:20:53, Pandruvada, Srinivas wrote:
> On Fri, 2016-11-04 at 23:16 +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()
> 
> ?

Ok, can do, let me recompile and reboot.

> When temperature limit is reached acpi_processor_ppc_notifier() should
> be called.

No, that's not correct for ACPI passive trip points, is it? If I
recall correctly, those should be monitored even when temperature is
below them so that it does not reach them...?

								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-11-05 13:20 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 [this message]
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
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=20161105132049.GC10310@amd \
    --to=pavel@ucw.cz \
    --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=platform-driver-x86@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=srinivas.pandruvada@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).