From: yakui_zhao <yakui.zhao@intel.com>
To: Luca Capello <luca@pca.it>
Cc: ML Linux-ACPI <linux-acpi@vger.kernel.org>
Subject: Re: [BUG?] Critical temperature shutdowns on ThinkPad X60 1706-GMG
Date: Fri, 06 Feb 2009 09:31:53 +0800 [thread overview]
Message-ID: <1233883913.3625.14.camel@localhost.localdomain> (raw)
In-Reply-To: <878wokssga.fsf@gismo.pca.it>
On Fri, 2009-02-06 at 01:29 +0800, Luca Capello wrote:
> Hi there!
>
> In July 2008 I reported a problem about critical temperature shutdowns:
>
> http://news.gmane.org/find-root.php?message_id=%3c87zlnyv14h.fsf%5f%2d%5f%40gismo.pca.it%3e
>
> Since I was not the only one experiencing it, reading the mailing list I
> had the impression it had been solved since then.
>
> And indeed I do not remember I have experienced it again. However, the
> last week it reappeared, probably because in the meantime I have not
> used my laptop at full power :-(
>
> Anyway, here we are:
>
> - I got 6 "Critical temperature reached (128 C), shutting down"
> experiences since January 30th
The Critical shutdown threshold is 128. In fact it is quite high.
In fact only when the actual temperature is above 128, the following
message will be complained and the box will be shutdown.
>Critical temperature reached (128 C), shutting down
Will you please attach the output of acpidump? Let's check whether the
temperature is obtained by using EC.
Thanks.
>
> - when I know that temperature could rise (e.g. using QEMU to build
> Debian packages for armel), I usually set the fan at maximum speed
>
> $ echo -n "level full-speed" >/proc/acpi/ibm/fan
>
> However, the last time (10 minutes ago) happened even with that
> setting and my setup was:
>
> * my usual Emacs session
> * Conkeror
> * a git-buildpackage process (basically building a Debian package from
> a Git repository and inside a chroot)
> * the Openmoko FreeRunner was plugged to the left USB port and charging
> * on one of the right port there was an Eutronsec SIMReaderCombo,
> basically an OmniKey CardMan 6121 USB SIM-sized smartcard reader
> coupled with a 2GB flash memory (in my case this is SLC, more
> information at http://www.eutronsec.it/ )
> * the laptop is placed on a scientific laboratory desk and the airflow
> from the fan grid is free to circulate
> * the laptop is on AC power with no battery inserted
>
> - the last was on Debian kernel 2.6.28-1~experimental.1~snapshot.12674;
> since I am preparing for FOSDEM, I do not have time right now to test
> a vanilla kernel, but I will do starting from next Monday. Which
> kernel version should I test first, 2.6.28.3?
>
> That is all, I think. Feel free to ask for more inforation/test.
>
> Thx, bye,
> Gismo / Luca
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-06 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 17:29 [BUG?] Critical temperature shutdowns on ThinkPad X60 1706-GMG Luca Capello
2009-02-06 1:31 ` yakui_zhao [this message]
2009-02-06 1:59 ` Luca Capello
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=1233883913.3625.14.camel@localhost.localdomain \
--to=yakui.zhao@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=luca@pca.it \
/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