From: Ron Rechenmacher <ron@fnal.gov>
To: linux-acpi@vger.kernel.org
Cc: ron@fnal.gov
Subject: 2.6.24 Temperature/speed _not_ normal - no thermal throttling?
Date: Wed, 20 Feb 2008 00:18:15 -0600 [thread overview]
Message-ID: <47BBC627.8020907@fnal.gov> (raw)
Hi,
I believe I am having a critical thermal problem. I do not know if it
is limited to the 2.6.24.2 kernel which I am running. I do see there has
been some discussion about thermal zones and throttling on the list,
but I can not tell if it means that thermal throttling is not working in
2.6.24.2
When I try to build several kernel source rpms, my dell d830 laptop
seems to over heat and hang. It's happened 3 times now and I would like
to learn what's going on and not let it happen again.
I'm a newbie (and have had problems trying to post :), so I do apologize
if I've missing something relatively simple or if this is post is not
appropriate in any way.
I'm running a Scientific Linux 5 (based on RHEL5) distribution and am
just running a cpuspeed user space utility --- and therefor do not
believe I have any user space process watching temperature. However, in
the earlier kernels, I use to be able to (manually) write to
/proc/acpi/processor/CPU0/throttling and see a change when read back,
but now the write does not seem to do anything. This might be OK as I 'm
thinking the kernel and/or the hardware itself might now suppose to be
doing the throttling?
Anyway, in 3 windows, I run:
win1: stress --cpu 8 --io 4 --vm 2 --vm-bytes 128M --timeout 180s
win2: while sleep 1;do cat /proc/acpi/thermal_zone/THM/temperature;done
win3: tail -f /var/log/messages
win4; while sleep 1;do cat /proc/acpi/processor/CPU0/throttling;done
In win2, I see the temperature go from 50 C to over 86 C.
In win3, before, the temp in win2 reaches 70 C, I see "kernel: CPU0:
Temperature/speed normal" (and also CPU1) and "kernel: Machine check
events logged"
The temperature would probably just continue to climb if I ran the test
for longer that 180 seconds (the kernel rpms take much longer and do not
complete before the system hangs :(
In /var/log/mcelog, (running mcelog-0.8pre), I only see "Processor core
below trip temperature. Throttling disabled" messages. This is strange
because it seems to be being disabling after never being enabled. (Is
there a newer mcelog I should be running?)
The fan speed does increase, but the throttling state indication never
changes (it's always "T0: 100%"). It seems that when I build the kernel
rpms, the increased fan speed is not enough to keep the temperature form
running away. It seems that thermal throttling would be required and is
not happening.
Should I be doing something from user space? Can I do something from
user space?
Thanks,
Ron
next reply other threads:[~2008-02-20 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 6:18 Ron Rechenmacher [this message]
2008-02-20 9:27 ` 2.6.24 Temperature/speed _not_ normal - no thermal throttling? Alexey Starikovskiy
2008-02-23 4:33 ` Len Brown
2008-02-25 19:36 ` Chuck Ebbert
2008-02-26 12:31 ` Thomas Renninger
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=47BBC627.8020907@fnal.gov \
--to=ron@fnal.gov \
--cc=linux-acpi@vger.kernel.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