From: Albert Schueller <schuelaw-23yYEaFFs4qVc3sceRu5cw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Thermal trip_points, raise them?
Date: Tue, 20 Jan 2004 00:26:29 -0800 [thread overview]
Message-ID: <20040120002629.A21624@carrot.whitman.edu> (raw)
Tue Jan 20 00:23:44 PST 2004
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.
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
I'll take responsibility for any thermal damage, I'm just
wondering if this will raise the trip_points for me.
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).
- Just out of curiosity, what is the difference between the ACPI
code in the stock 2.6.1 kernel and, say, the 2.6.1 patch
provided on the acpi.sf.net page? (I know, I know, look at
the diffs.) Are there different development groups for ACPI?
One that's getting their stuff into the current kernels, and
this group that provides a patch replacement?
Sorry if these are FAQ's.
A
--
Albert Schueller Department of Mathematics
Office Phone: 509-527-5140 Whitman College
Public Key: http://carrot.whitman.edu/gpg.key Walla Walla, WA USA 99362
-------------------------------------------------------
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
next reply other threads:[~2004-01-20 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 8:26 Albert Schueller [this message]
[not found] ` <20040120002629.A21624-M+MqQPf49VVrC2pQ8WgM2De48wsgrGvP@public.gmane.org>
2004-01-20 20:49 ` Thermal trip_points, raise them? 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=20040120002629.A21624@carrot.whitman.edu \
--to=schuelaw-23yyeaffs4qvc3sceru5cw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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