public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Suspend, followed by immediate resume
Date: Sun, 4 May 2008 00:48:15 +0200	[thread overview]
Message-ID: <200805040048.15856.rjw@sisk.pl> (raw)
In-Reply-To: <20080503083514.0b62638e@osprey.hogchain.net>

On Saturday, 3 of May 2008, Jay Cliburn wrote:
> On Sat, 3 May 2008 15:09:01 +0200
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
> > Set your BIOS setting to "Auto" and boot the kernel with
> > init=/bin/bash. You should get a root shell as a result of this.
> > From this shell run:
> > 
> > # mount /proc
> > # mount /sys
> > # echo 8 > /proc/sys/kernel/printk
> > # eche mem > /sys/power/state
> > 
> > and see if it suspends.  If it does, try to wake it up and see what
> > happens.
> 
> The system suspends and does not spontaneously resume.  That's an
> improvement.
> 
> Unfortunately I can't awaken it.  It's a desktop system and pressing
> keys, shaking the mouse, or momentarily pressing the power switch has no
> effect, despite setting these things in BIOS.  (There are some APM
> settings in there that selectively enable waking on various events.)
> 
> Ctrl-alt-del actually did cause a reboot, though.
> 
> As an aside, I finally got wake-on-lan working, so the reason I came to
> linux-pm in the first place has been satisfied.  I don't *need*
> suspend/resume to work on this system, however, if you think
> the suspend issue I'm having is worth pursuing, I'm perfectly willing
> to press on.  Your call.

Well, I'm afraid we'd end up debugging your ACPI tables, so it's probably
better to give up if the feature is not really needed.

Thanks,
Rafael

  reply	other threads:[~2008-05-03 22:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02  2:44 Suspend, followed by immediate resume Jay Cliburn
2008-05-02 15:00 ` Alan Stern
2008-05-02 16:39   ` Jay Cliburn
2008-05-02 16:47     ` Alan Stern
2008-05-02 16:49     ` Rafael J. Wysocki
2008-05-02 16:57       ` Jay Cliburn
2008-05-02 16:59         ` Rafael J. Wysocki
2008-05-02 17:29           ` Jay Cliburn
2008-05-02 17:41             ` Rafael J. Wysocki
2008-05-02 18:10               ` Jay Cliburn
2008-05-02 23:49                 ` Rafael J. Wysocki
2008-05-03  2:05                   ` Jay Cliburn
2008-05-03 12:32                     ` Rafael J. Wysocki
2008-05-03 12:50                       ` Rafael J. Wysocki
2008-05-03 12:58                         ` Jay Cliburn
2008-05-03 13:09                           ` Rafael J. Wysocki
2008-05-03 13:35                             ` Jay Cliburn
2008-05-03 22:48                               ` Rafael J. Wysocki [this message]
2008-05-14 19:19                               ` Pavel Machek
2008-05-14 14:43                 ` Pavel Machek
2008-05-14 14:42 ` Pavel Machek
2008-05-15  2:04   ` Zhang Rui

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=200805040048.15856.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=jacliburn@bellsouth.net \
    --cc=linux-pm@lists.linux-foundation.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