Re: [Swsusp-devel] cpu temp probs?

Re: [Swsusp-devel] cpu temp probs?

[Karol Kozimor]

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,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
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

Re: cpu temp probs?

[Christopher N. Deckard]

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