From: Christoph Hellwig <hch@lst.de>
To: Thomas Renninger <trenn@suse.de>
Cc: Christoph Hellwig <hch@lst.de>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Zhang Rui <rui.zhang@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: regression: 2.6.32-rc8 shuts down after reaching critical temperature
Date: Wed, 2 Dec 2009 16:35:36 +0100 [thread overview]
Message-ID: <20091202153536.GA20324@lst.de> (raw)
In-Reply-To: <200912021607.53237.trenn@suse.de>
On Wed, Dec 02, 2009 at 04:07:52PM +0100, Thomas Renninger wrote:
> Some more hints you may want to try:
>
> - Does cpufreq work at all?
> Does this dir exist: /sys/devices/system/cpu/cpu*/cpufreq
Yes.
> If temp of:
> watch -n1 cat /proc/acpi/thermal_zone/THM1/temperature
> goes beyond 96 C
> an ACPI processor event must get thrown and this:
> /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq
> will get limited (lower than ../cpufreq/cpuinfo_max_freq).
The speeds change quite constantly under a kernel compile workload, but
most of the time it's at 2240800 vs cpuinfo_max_freq which is 2801000
> echo xy >/sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq
> may be bad workaround.
echo 2240800 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 2240800 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
made it survive a kernel compile for me, with an observed maximum
temperature of 87 C.
More later..
next prev parent reply other threads:[~2009-12-02 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 10:28 regression: 2.6.32-rc8 shuts down after reaching critical temperature Christoph Hellwig
2009-11-25 21:56 ` Len Brown
2009-11-25 22:13 ` Christoph Hellwig
2009-11-25 23:07 ` Len Brown
2009-11-26 10:17 ` Christoph Hellwig
2009-11-26 10:35 ` Christoph Hellwig
2009-12-02 15:14 ` Christoph Hellwig
2009-11-26 2:23 ` Henrique de Moraes Holschuh
2009-11-26 9:52 ` Christoph Hellwig
2009-12-02 11:56 ` Thomas Renninger
2009-12-02 13:30 ` Christoph Hellwig
2009-12-02 15:07 ` Thomas Renninger
2009-12-02 15:35 ` Christoph Hellwig [this message]
2009-12-11 6:49 ` Len Brown
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=20091202153536.GA20324@lst.de \
--to=hch@lst.de \
--cc=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=trenn@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox