From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Albert Schueller <schuelaw-23yYEaFFs4qVc3sceRu5cw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Thermal trip_points, raise them?
Date: Tue, 20 Jan 2004 21:49:09 +0100 [thread overview]
Message-ID: <20040120204909.GB9749@elf.ucw.cz> (raw)
In-Reply-To: <20040120002629.A21624-M+MqQPf49VVrC2pQ8WgM2De48wsgrGvP@public.gmane.org>
Hi!
> After a brief search of the archives on this subject, I have the
> following questions:
>
> (I'm running ACPI that's in the stock 2.6.1 kernel, this is a debian
> woody (mostly stable) machine, with, of course, the 2.6.1 kernel. )
>
> - Ever since I started running acpi on my Dell SmartStep 200N
> I've been getting thermal shutdowns. I suppose having them is
> better than not having them, but even in a well-ventilated,
> cool room, the machine will shutdown if I compile a kernel.
> This is a 2GHz P4 (mobile). It's clean inside, no dust.
> According to the specs at Intel the chip is safe upto 100°C
> (though maybe not the stuff around it, I don't know).
>
> In
>
> /proc/acpi/thermal_zone/THR1/trip_points = 72 C
> /proc/acpi/thermal_zone/THR2/trip_points = 78 C
>
> well shy of the 100°C on the Intel spec.
Heh, on my athlon omnibook xe3 they have critical at ~100C, but
hardware kills it at 83C. They obviously never tested it :-(
> I was planning to hack the acpi source and raise the trip
> points to something like 80 and 86, but I can't find where
> they're being set. This makes me think that they're being
> obtained from the BIOS somehow.
>
> Is it ok to just:
>
> cat "80 C" > /proc/acpi/thermal_zone/THR1/trip_points
> cat "86 C" > /proc/acpi/thermal_zone/THR2/trip_points
You should be able to
echo "critical:passive:active1:active2" > .../trip_points
. [Ouch, someone should write readme about this one. Do you
volunteer]?
> I'll take responsibility for any thermal damage, I'm just
> wondering if this will raise the trip_points for me.
With passive cooling, you should be able to keep it below trip
points...
> Alternatively, would removing the thermal module before a big
> job, like a kernel compile, and then reinserting it be ok?
> Or, would it break the ACPI that's currently running?
> (again I take responsibility for thermal damage).
You should not be able to cause thermal damage. If you hit it *real*
hard, hardware should hard-off it. [And it works on most machines].
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
prev parent reply other threads:[~2004-01-20 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 8:26 Thermal trip_points, raise them? Albert Schueller
[not found] ` <20040120002629.A21624-M+MqQPf49VVrC2pQ8WgM2De48wsgrGvP@public.gmane.org>
2004-01-20 20:49 ` Pavel Machek [this message]
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=20040120204909.GB9749@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=schuelaw-23yYEaFFs4qVc3sceRu5cw@public.gmane.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