mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Charles Lepple" <clepple@ghz.cc>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [REPOST] "apm: suspend: Unable to enter requested state"  after2.5.31 (incl. 2.6.0testX)
Date: Wed, 30 Jul 2003 12:48:03 -0400 (EDT)	[thread overview]
Message-ID: <54974.216.12.38.216.1059583683.squirrel@www.ghz.cc> (raw)
In-Reply-To: <20030730122145.77592840.sfr@canb.auug.org.au>

Stephen Rothwell said:
> If you get no OOPS from running the above, then you could try the second
> patch below. If your machine still behaves the same way, then you have
> completely ruled out that change to the apm code ... so we need to look
> elsewhere.

I guess it wasn't using that descriptor. The machine behaved the same way
as before when I tested each patch ("unable to enter requested state", and
system comes back to normal).

While experimenting, I noticed something else: in the cases where a system
suspend failed ('apm -s', closing the lid, or activating IBM's hibernate
mode), a 'system standby' request worked. Trying to transition from
standby to suspend does not work, however-- the laptop wakes up, and
eventually prints the same error message as for a normal suspend.

thanks for the patch,

-- 
Charles Lepple <clepple@ghz.cc>
http://www.ghz.cc/charles/

  reply	other threads:[~2003-07-30 16:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 14:50 [REPOST] "apm: suspend: Unable to enter requested state" after 2.5.31 " Charles Lepple
2003-07-29 15:07 ` Alan Cox
2003-07-29 16:05   ` Charles Lepple
2003-07-29 18:10     ` Alan Cox
2003-07-30  1:05       ` Stephen Rothwell
2003-07-30  1:38         ` Charles Lepple
2003-07-30  2:21           ` Stephen Rothwell
2003-07-30 16:48             ` Charles Lepple [this message]
2003-07-30 14:43         ` Alan Cox
2003-07-30 15:16           ` Stephen Rothwell

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=54974.216.12.38.216.1059583683.squirrel@www.ghz.cc \
    --to=clepple@ghz.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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

all inboxes | Powered by JetHome®