public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: cpufreq stops working after a while
Date: Fri, 11 Aug 2006 17:53:55 -0400	[thread overview]
Message-ID: <44DCFC73.7020103@rtr.ca> (raw)
In-Reply-To: <EB12A50964762B4D8111D55B764A84546F8F82@scsmsx413.amr.corp.intel.com>

Pallipadi, Venkatesh wrote:
>> Mark Lord wrote:
>> Yup, thermal.
>> Trips shortly after I see 66C in 
>> /proc/acpi/thermal_zone/THM/temperature
>>
>> If I stop number crunching for a bit, the temperature drops down to the
>> low 50's, and the max freq then gets set back to 1100.
>>
>> Mmmm.. is there a way to control the high/low thermostat values there?
..
> What is the "cooling mode" you have in
> /proc/acpi/thermal_zone/THM/cooling_mode.
> Output of all files in that directory will help.

/proc/acpi/thermal_zone/THM/cooling_mode:
	<setting not supported>
	cooling mode:   critical

/proc/acpi/thermal_zone/THM/polling_frequency:
	<polling disabled>

/proc/acpi/thermal_zone/THM/state:
	state:                   ok

/proc/acpi/thermal_zone/THM/temperature:
	temperature:             49 C

/proc/acpi/thermal_zone/THM/trip_points:
	critical (S5):           95 C

==========

This is a passively cooled notebook, so there's no fan
to control.  They probably self-limit the CPU speed when
the temperature gets high to prevent meltdown of the drive.

But I would like to raise the lower limit if possible,
allowing the speed to bump back up at, say 58C rather
than waiting for 52C as it currently does.

??


  reply	other threads:[~2006-08-11 21:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 21:38 cpufreq stops working after a while Pallipadi, Venkatesh
2006-08-11 21:53 ` Mark Lord [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-11 22:18 Pallipadi, Venkatesh
2006-08-11 21:08 Pallipadi, Venkatesh
2006-08-11 19:55 Pallipadi, Venkatesh
2006-08-11 20:29 ` Mark Lord
2006-08-11 20:39   ` Mark Lord
2006-08-11 21:01     ` Dave Jones
2006-08-11 21:09       ` Mark Lord
2006-08-11 21:15       ` Mark Lord
2006-08-11 21:17         ` Mark Lord
2006-08-11 21:25         ` Mark Lord
2006-08-18 15:11           ` Pavel Machek
2006-08-24 14:44             ` Mark Lord
2006-08-24 16:15               ` Matthew Garrett
2006-08-11 18:25 Mark Lord
2006-08-11 18:39 ` Dave Jones
2006-08-11 19:41   ` Mark Lord
2006-08-11 20:01     ` Mark Lord
2006-08-11 20:12       ` Dave Jones
2006-08-11 18:46 ` Andrew Morton
2006-08-11 19:01   ` Mark Lord
2006-08-11 19:10   ` Mark Lord
2006-08-11 19:18     ` Andrew Morton

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=44DCFC73.7020103@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    /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