From: Pavel Machek <pavel@ucw.cz>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-pm@osdl.org, LKML <linux-kernel@vger.kernel.org>,
Suspend2-devel@lists.suspend2.net, ncunningham@linuxmail.org
Subject: Re: swsusp and suspend2 like to overheat my laptop
Date: Wed, 9 Aug 2006 01:53:52 +0200 [thread overview]
Message-ID: <20060808235352.GA4751@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.58.0608081612380.17442@gandalf.stny.rr.com>
Hi!
> A few months ago, I installed suspend2 on my laptop. It worked great for
> a few days, when suddenly my laptop started to get very hot and the fan
> costantly went off, and then I started getting these:
I take it as "if I keep it for a week powered off, it will not do
this".
> ---
> Message from syslogd@localhost at Tue Aug 8 16:08:53 2006 ...
> localhost kernel: CPU0: Temperature above threshold
>
> Message from syslogd@localhost at Tue Aug 8 16:08:53 2006 ...
> localhost kernel: CPU1: Temperature above threshold
>
>
> Message from syslogd@localhost at Tue Aug 8 16:08:53 2006 ...
> localhost kernel: CPU0: Running in modulated clock mode
>
> Message from syslogd@localhost at Tue Aug 8 16:08:53 2006 ...
> localhost kernel: CPU1: Running in modulated clock mode
> ---
P4 has thermal protection, so you are actually safe.
Nigel is right, this is acpi problem, but I guess we can help it. Do
you have /proc/acpi/fan? Do you have /proc/acpi/ibm/fan? Can you try
playing with them?
And yes, this should go into bugzilla.kernel.org.
> Recently, I've decided to try out swsusp. Well, it has been working fine
> for almost a week now. But unfortunately, I just started to have my fan
> go off constantly, and I'm getting the above messages again (hence why
> the date on the messages is today). Checking out the temp, it's going into
> the high 70C. That's not too bad, but it only happens when suspending
> every night instead of shutting down.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-08-08 23:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 21:40 swsusp and suspend2 like to overheat my laptop Steven Rostedt
2006-08-08 21:50 ` Nigel Cunningham
2006-08-08 23:31 ` Steven Rostedt
2006-08-08 23:35 ` Lee Revell
2006-08-08 23:42 ` Nigel Cunningham
2006-08-08 23:50 ` Steven Rostedt
2006-08-09 13:05 ` Mark Lord
2006-08-09 6:14 ` Ian Campbell
2006-08-08 23:53 ` Pavel Machek [this message]
2006-08-09 2:23 ` Steven Rostedt
2006-08-09 7:39 ` Pavel Machek
2006-08-09 11:45 ` Steven Rostedt
2006-08-09 11:54 ` Nigel Cunningham
2006-08-09 11:58 ` Pavel Machek
2006-08-09 12:15 ` Rafael J. Wysocki
2006-08-09 13:16 ` Steven Rostedt
2006-08-09 13:42 ` Andreas Mohr
2006-08-09 20:32 ` Rafael J. Wysocki
2006-08-09 13:35 ` Steven Rostedt
2006-08-09 13:37 ` Pavel Machek
2006-08-09 13:45 ` Brad Campbell
2006-08-09 12:04 ` Steven Rostedt
2006-08-09 12:08 ` Pavel Machek
2006-08-09 12:35 ` Steven Rostedt
2006-08-09 12:58 ` Pavel Machek
2006-08-11 0:14 ` Steven Rostedt
2006-08-09 12:14 ` Steven Rostedt
2006-08-09 12:07 ` Andreas Mohr
2006-08-09 12:38 ` Steven Rostedt
2006-08-09 13:03 ` Andreas Mohr
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=20060808235352.GA4751@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Suspend2-devel@lists.suspend2.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=ncunningham@linuxmail.org \
--cc=rostedt@goodmis.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