[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091202153536.GA20324@lst.de>
Date: Wed, 2 Dec 2009 16:35:36 +0100
From: Christoph Hellwig <hch@....de>
To: Thomas Renninger <trenn@...e.de>
Cc: Christoph Hellwig <hch@....de>,
Henrique de Moraes Holschuh <hmh@....eng.br>,
Zhang Rui <rui.zhang@...el.com>, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: regression: 2.6.32-rc8 shuts down after reaching critical temperature
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..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists