From: Theodore Tso <tytso@mit.edu>
To: Luca Capello <luca@pca.it>
Cc: Thomas Renninger <trenn@suse.de>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
ak@linux.intel.com, linux-acpi@vger.kernel.org,
ibm-acpi-devel@lists.sourceforge.net, lenb@kernel.org
Subject: Re: Critical temp shutdowns on ThinkPad X60 1706-GMG
Date: Thu, 31 Jul 2008 10:06:02 -0400 [thread overview]
Message-ID: <20080731140602.GB11632@mit.edu> (raw)
In-Reply-To: <87od4etc6k.fsf@gismo.pca.it>
On Thu, Jul 31, 2008 at 03:28:51PM +0200, Luca Capello wrote:
> OK, if you want to give a try to my test case:
>
> $ [install darcs]
> $ darcs get http://alioth.debian.org/~gismo/darcs-pull-bug/parenscript.upstream/
> $ darcs get http://alioth.debian.org/~gismo/darcs-pull-bug/parenscript/
> $ cd parenscript
> $ darcs pull ../parenscript.upstream/
> [choose to apply only the first patch]
>
> At that point, darcs takes 100% of the CPU and temperature starts to
> rise :-(
Hmm.... darcs is not impressing me as a good choice of version control
systems. I mean, yes I'm spoiled with git being able to merge
hundreds of patches is seconds, but this is rediculous! :-)
I've tried running for it for a while, and THM0 and THM1 are in the
80-83 degree range, but it's not going above that. According to THM1
has a passive trip point at 96 degrees, and a critical trip point at
100 degrees, but with your test case I'm not going anywhere near that
level.
Just for yucks I tried running a second copy of your test case (since
I hae a dual-core processor), and with the second core also busy 100%,
I was able to drive the temperature up another degree or two, but that
was about it.
Regards,
- Ted
next prev parent reply other threads:[~2008-07-31 14:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 13:56 Avoid critical temp shutdowns on specific ThinkPad T4x(p) and R50p Thomas Renninger
2008-07-30 16:17 ` Andi Kleen
[not found] ` <4890942C.3080007-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2008-07-30 16:46 ` Thomas Renninger
[not found] ` <200807301556.01815.trenn-l3A5Bk7waGM@public.gmane.org>
2008-07-30 17:52 ` Henrique de Moraes Holschuh
[not found] ` <20080730175227.GA13850-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org>
2008-07-30 19:03 ` Thomas Renninger
2008-07-30 20:39 ` [ibm-acpi-devel] " Chris Hanson
[not found] ` <f62196f50807301339r10bbb17do4bb2345b688011a3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-31 13:19 ` Henrique de Moraes Holschuh
2008-07-31 9:44 ` Critical temp shutdowns on ThinkPad X60 1706-GMG (was Re: [ibm-acpi-devel] Avoid critical temp shutdowns on specific ThinkPad T4x(p) and R50p) Luca Capello
[not found] ` <87zlnyv14h.fsf_-_-vpnYUZh4Q8kL5bzFcGmneg@public.gmane.org>
2008-07-31 12:39 ` Critical temp shutdowns on ThinkPad X60 1706-GMG (was " Thomas Renninger
2008-07-31 13:04 ` Critical temp shutdowns on ThinkPad X60 1706-GMG Luca Capello
2008-07-31 13:15 ` Theodore Tso
[not found] ` <20080731131512.GI5347-3s7WtUTddSA@public.gmane.org>
2008-07-31 13:21 ` Henrique de Moraes Holschuh
2008-07-31 13:28 ` Luca Capello
2008-07-31 14:06 ` Theodore Tso [this message]
[not found] ` <20080731140602.GB11632-3s7WtUTddSA@public.gmane.org>
2008-07-31 14:15 ` Henrique de Moraes Holschuh
2008-07-31 1:02 ` Avoid critical temp shutdowns on specific ThinkPad T4x(p) and R50p Zhang Rui
2008-08-01 11:18 ` Thomas Renninger
2008-08-11 11:30 ` Andi Kleen
[not found] ` <48A022BD.2040908-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2008-08-11 12:33 ` Thomas Renninger
[not found] ` <200808111433.25275.trenn-l3A5Bk7waGM@public.gmane.org>
2008-08-11 12:55 ` Matthew Garrett
[not found] ` <20080811125519.GA26308-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2008-08-11 14:14 ` Thomas Renninger
2008-08-11 14:15 ` Matthew Garrett
2008-08-12 8:00 ` Andi Kleen
2008-08-12 8:02 ` Matthew Garrett
2008-08-12 8:20 ` Zhang Rui
2008-08-12 9:32 ` Andi Kleen
2008-08-12 1:27 ` Zhang Rui
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=20080731140602.GB11632@mit.edu \
--to=tytso@mit.edu \
--cc=ak@linux.intel.com \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=luca@pca.it \
--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