From: "Christopher N. Deckard" <cnd@ecn.purdue.edu>
To: Karol Kozimor <sziwan@hell.org.pl>
Cc: Jon Olson <morph@damogran.org>,
Software Suspend Mailing List
<swsusp-devel@lists.sourceforge.net>,
acpi-devel@lists.sourceforge.net
Subject: Re: cpu temp probs?
Date: Mon, 17 May 2004 19:41:06 -0500 [thread overview]
Message-ID: <40A95BA2.5050008@ecn.purdue.edu> (raw)
In-Reply-To: <20040518000603.GA28576@hell.org.pl>
Karol Kozimor wrote:
> Thus wrote Christopher N. Deckard:
>
>>>>I don't close the screen while suspending. I have been waiting for
>>>>a complete power off just to make sure it's doing it's thing...
>>>
>>>What does /proc/acpi/processor/*/* say before and after suspend (cat it
>>>several times at least)?
>>
>>After a normal boot, I seem to stay mostly in C2, but every now and
>>then I see it jump to C1. Jumps back to C2 almost immediately.
>>After a suspend and resume I stay in C1.
>
> That's odd. Are you sure it's not due to a run-away process or kernel
> thread such as keventd? If it's not, could you try reloading the processor
> module, or possibly unloading it before suspend and loading back after?
> Best regards,
>
In /etc/suspend.conf I have this:
SWSUSP_REMOVEMODS="thermal fan button processor ac battery nvidia"
When acpid is started on resume, it reloads those modules. You can
see output from dmesg after a resume here:
http://globalfoo.net/Linux/Laptop/DellD800/20040512_suspend_resume.log
This is kernel 2.6.6 + swsusp2 2.0.0.72. I don't see any runaway
processes or kernel threads, or at least top isn't seeing any.
-Chris
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
prev parent reply other threads:[~2004-05-18 0:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40A8D431.9090506@ecn.purdue.edu>
[not found] ` <1084824054.23442.6.camel@localhost>
[not found] ` <40A9272D.7040405@ecn.purdue.edu>
[not found] ` <20040517211849.GB24480@hell.org.pl>
[not found] ` <40A937F4.8090601@ecn.purdue.edu>
[not found] ` <40A937F4.8090601-UGcGKVkOO5s4WbhGE/lxQQ@public.gmane.org>
2004-05-18 0:06 ` [Swsusp-devel] cpu temp probs? Karol Kozimor
2004-05-18 0:41 ` Christopher N. Deckard [this message]
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=40A95BA2.5050008@ecn.purdue.edu \
--to=cnd@ecn.purdue.edu \
--cc=acpi-devel@lists.sourceforge.net \
--cc=morph@damogran.org \
--cc=swsusp-devel@lists.sourceforge.net \
--cc=sziwan@hell.org.pl \
/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