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 09:42:49 +0100	[thread overview]
Message-ID: <20161105084248.GA664@amd> (raw)
In-Reply-To: <1478293976.1268.15.camel@intel.com>

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

Hi!

> > 4.9-rc2 has bios_limit:
> > 
> > pavel@duo:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/bios_limit
> > 1833000
> > 
> > and it has thermal zones:
> > 
> > /sys/devices/virtual/thermal/thermal_zone0/trip_point_0_temp 127000
> > /sys/devices/virtual/thermal/thermal_zone0/trip_point_0_type critical
> > /sys/devices/virtual/thermal/thermal_zone1/trip_point_0_temp 97000
> > /sys/devices/virtual/thermal/thermal_zone1/trip_point_0_type critical
> > /sys/devices/virtual/thermal/thermal_zone1/trip_point_1_temp 92500
> > /sys/devices/virtual/thermal/thermal_zone1/trip_point_1_type passive
> > 
> It will not act if there is no binding information. Do you have more
> files in this folder?
> 
> grep -r . * in /sys/class/thermal will be helpful.

Yes, I do. Here you go:

pavel@duo:/data/l/linux$ sudo grep -ri . /sys/class/thermal/*
/sys/class/thermal/cooling_device0/cur_state:0
/sys/class/thermal/cooling_device0/power/runtime_active_kids:0
/sys/class/thermal/cooling_device0/power/runtime_suspended_time:0
grep: /sys/class/thermal/cooling_device0/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/cooling_device0/power/runtime_enabled:disabled
/sys/class/thermal/cooling_device0/power/runtime_active_time:0
/sys/class/thermal/cooling_device0/power/control:auto
/sys/class/thermal/cooling_device0/power/async:disabled
/sys/class/thermal/cooling_device0/power/runtime_usage:0
/sys/class/thermal/cooling_device0/power/runtime_status:unsupported
/sys/class/thermal/cooling_device0/type:LCD
/sys/class/thermal/cooling_device0/max_state:7
/sys/class/thermal/cooling_device1/cur_state:0
/sys/class/thermal/cooling_device1/power/runtime_active_kids:0
/sys/class/thermal/cooling_device1/power/runtime_suspended_time:0
grep: /sys/class/thermal/cooling_device1/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/cooling_device1/power/runtime_enabled:disabled
/sys/class/thermal/cooling_device1/power/runtime_active_time:0
/sys/class/thermal/cooling_device1/power/control:auto
/sys/class/thermal/cooling_device1/power/async:disabled
/sys/class/thermal/cooling_device1/power/runtime_usage:0
/sys/class/thermal/cooling_device1/power/runtime_status:unsupported
/sys/class/thermal/cooling_device1/type:Processor
/sys/class/thermal/cooling_device1/max_state:10
/sys/class/thermal/cooling_device2/cur_state:0
/sys/class/thermal/cooling_device2/power/runtime_active_kids:0
/sys/class/thermal/cooling_device2/power/runtime_suspended_time:0
grep: /sys/class/thermal/cooling_device2/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/cooling_device2/power/runtime_enabled:disabled
/sys/class/thermal/cooling_device2/power/runtime_active_time:0
/sys/class/thermal/cooling_device2/power/control:auto
/sys/class/thermal/cooling_device2/power/async:disabled
/sys/class/thermal/cooling_device2/power/runtime_usage:0
/sys/class/thermal/cooling_device2/power/runtime_status:unsupported
/sys/class/thermal/cooling_device2/type:Processor
/sys/class/thermal/cooling_device2/max_state:10
/sys/class/thermal/thermal_zone0/passive:0
/sys/class/thermal/thermal_zone0/available_policies:step_wise
/sys/class/thermal/thermal_zone0/policy:step_wise
/sys/class/thermal/thermal_zone0/mode:enabled
grep: /sys/class/thermal/thermal_zone0/offset: Input/output error
grep: /sys/class/thermal/thermal_zone0/integral_cutoff: Input/output
error
/sys/class/thermal/thermal_zone0/power/runtime_active_kids:0
/sys/class/thermal/thermal_zone0/power/runtime_suspended_time:0
grep: /sys/class/thermal/thermal_zone0/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/thermal_zone0/power/runtime_enabled:disabled
/sys/class/thermal/thermal_zone0/power/runtime_active_time:0
/sys/class/thermal/thermal_zone0/power/control:auto
/sys/class/thermal/thermal_zone0/power/async:disabled
/sys/class/thermal/thermal_zone0/power/runtime_usage:0
/sys/class/thermal/thermal_zone0/power/runtime_status:unsupported
grep: /sys/class/thermal/thermal_zone0/k_d: Input/output error
/sys/class/thermal/thermal_zone0/trip_point_0_type:critical
/sys/class/thermal/thermal_zone0/type:acpitz
grep: /sys/class/thermal/thermal_zone0/slope: Input/output error
grep: /sys/class/thermal/thermal_zone0/k_po: Input/output error
grep: /sys/class/thermal/thermal_zone0/k_i: Input/output error
grep: /sys/class/thermal/thermal_zone0/sustainable_power: Input/output
error
/sys/class/thermal/thermal_zone0/trip_point_0_temp:127000
grep: /sys/class/thermal/thermal_zone0/k_pu: Input/output error
/sys/class/thermal/thermal_zone0/temp:58000
/sys/class/thermal/thermal_zone1/available_policies:step_wise
/sys/class/thermal/thermal_zone1/policy:step_wise
/sys/class/thermal/thermal_zone1/mode:enabled
/sys/class/thermal/thermal_zone1/trip_point_1_type:passive
grep: /sys/class/thermal/thermal_zone1/offset: Input/output error
grep: /sys/class/thermal/thermal_zone1/integral_cutoff: Input/output
error
/sys/class/thermal/thermal_zone1/power/runtime_active_kids:0
/sys/class/thermal/thermal_zone1/power/runtime_suspended_time:0
grep: /sys/class/thermal/thermal_zone1/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/thermal_zone1/power/runtime_enabled:disabled
/sys/class/thermal/thermal_zone1/power/runtime_active_time:0
/sys/class/thermal/thermal_zone1/power/control:auto
/sys/class/thermal/thermal_zone1/power/async:disabled
/sys/class/thermal/thermal_zone1/power/runtime_usage:0
/sys/class/thermal/thermal_zone1/power/runtime_status:unsupported
grep: /sys/class/thermal/thermal_zone1/k_d: Input/output error
/sys/class/thermal/thermal_zone1/trip_point_0_type:critical
/sys/class/thermal/thermal_zone1/type:acpitz
/sys/class/thermal/thermal_zone1/cdev1_weight:0
/sys/class/thermal/thermal_zone1/trip_point_1_temp:92500
grep: /sys/class/thermal/thermal_zone1/slope: Input/output error
grep: /sys/class/thermal/thermal_zone1/k_po: Input/output error
grep: /sys/class/thermal/thermal_zone1/k_i: Input/output error
/sys/class/thermal/thermal_zone1/cdev0_weight:0
grep: /sys/class/thermal/thermal_zone1/sustainable_power: Input/output
error
/sys/class/thermal/thermal_zone1/trip_point_0_temp:97000
/sys/class/thermal/thermal_zone1/cdev0_trip_point:1
grep: /sys/class/thermal/thermal_zone1/k_pu: Input/output error
/sys/class/thermal/thermal_zone1/temp:80000
/sys/class/thermal/thermal_zone1/cdev1_trip_point:1


> > Hmm. bios_limit does not seem to change, even when the temperature is
> > clearly above the trip point. (It is also interestng that acpi/ibm
> > reports bigger temperatures than
> > /sys/devices/virtual/thermal/thermal_zone1/temp . I have seen 103C
> > there.)
> Probably they are showing package and core temperature or have a
> different sampling interval.
> 
> Try enabling thermald service in Debian. it has access to more knobs to
> control thermals.

Hmm, thanks for the pointer. But it seems like I'll have to build my
own, as /proc/acpi/ibm does not follow the usual infrastructure...

Best regards,
									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  8:42 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 [this message]
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
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=20161105084248.GA664@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).