public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Petros Kolyvas <pkolyvas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Suspend to RAM issus on a Dell 700m
Date: Sun, 26 Jun 2005 23:11:07 +0200	[thread overview]
Message-ID: <20050626211107.GA1315@elf.ucw.cz> (raw)
In-Reply-To: <42BED9A0.9050803-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Hi!

> I finally got the "mem" state to function on my laptop (a state which I 
> use extensively in that "other" OS when I'm working.)
> 
> A few issues though... my cpu, upon return, powers up to full-speed 
> making it impossible to truly conserve power, sort of defeating the 
> whole process.
> 
> It seems a rogue process (one which I can't kill)... listed only as 'sh 
> -i" is using ~99% of the available CPU cycles. I have no idea where it's 
> coming from.
> 
> Additionally the system gets less and less responsive with each return 
> from the "mem" state. Probably due to many of these rogue processes 
> building up and bogging the system down.
> 
> Below is the script I used, which I found online and modified (very 
> little) as needed. Any insight would be greatly appreciated. Oh, I'm 
> using FC4 w/ 2.6.12 (unpatched.)

Are you using preempt by chance? See wchan where the sh -i is
running... then debug it :-).
								Pavel
-- 
teflon -- maybe it is a trademark, but it should not be.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

      parent reply	other threads:[~2005-06-26 21:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42BED9A0.9050803@gmail.com>
2005-06-26 16:36 ` Suspend to RAM issus on a Dell 700m Petros Kolyvas
     [not found]   ` <BAYC1-PASMTP01AF878251E9C0DF5ECA1BD6EF0-vCQSkuYnZQ8@public.gmane.org>
2005-06-26 19:25     ` Benedek Frank
     [not found]       ` <20050626212536.1345f132.linux-mmCHBaZtUya2oZ/6fjIToQ@public.gmane.org>
     [not found]         ` <42BF1955.5090200@gmail.com>
2005-06-26 21:08           ` Petros Kolyvas
     [not found]             ` <BAYC1-PASMTP010E8549F3ADA61D5271E4D6EF0-vCQSkuYnZQ8@public.gmane.org>
2005-06-26 21:20               ` Benedek Frank
     [not found]                 ` <20050626232019.4d0197de.linux-mmCHBaZtUya2oZ/6fjIToQ@public.gmane.org>
     [not found]                   ` <42BF822A.8030601@gmail.com>
2005-06-27  4:35                     ` Petros Kolyvas
     [not found]                       ` <BAYC1-PASMTP04FCE0511F69E3625E9638D6EE0-vCQSkuYnZQ8@public.gmane.org>
2005-06-27  5:57                         ` Benedek Frank
     [not found] ` <42BED9A0.9050803-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2005-06-26 21:11   ` Pavel Machek [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=20050626211107.GA1315@elf.ucw.cz \
    --to=pavel-+zi9xunit7i@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=pkolyvas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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