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: Fri, 2 May 2008 19:41:07 +0200	[thread overview]
Message-ID: <200805021941.08003.rjw@sisk.pl> (raw)
In-Reply-To: <20080502122910.429312a7@osprey.hogchain.net>

On Friday, 2 of May 2008, Jay Cliburn wrote:
> On Fri, 2 May 2008 18:59:56 +0200
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
> > On Friday, 2 of May 2008, Jay Cliburn wrote:
> > > On Fri, 2 May 2008 18:49:13 +0200
> > > "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > > 
> > > > Can you try to comment out acpi_enable_wakeup_device(acpi_state)
> > > > in drivers/acpi/sleep/main.c:acpi_suspend_enter() and see if that
> > > > helps?
> > > 
> > > I'm working with 2.6.25.1, which doesn't have acpi_suspend_enter(),
> > > but I'll hop over to current git and give it a try.
> > 
> > This function is called acpi_pm_enter() in 2.6.25.1.
> 
> No change.  I rebooted the modified kernel, then executed this command
> sequence.
> 
> jcliburn@osprey:~$ su -
> Password: 
> [root@osprey ~]# echo 8 > /proc/sys/kernel/printk
> [root@osprey ~]# ethtool -s eth0 wol g
> [root@osprey ~]# echo mem > /sys/power/state
> 
> 
> [root@osprey ~]# 
> [root@osprey ~]# 
> [root@osprey ~]# 
> 
> It spontaneously resumed.  Serial console log attached.

Does it suspend if you don't activate the WOL?

If it doesn't, please restore acpi_pm_enter(), boot the kernel with
init=/bin/bash and try to suspend (you'll need to mount /proc and /sys
manually after booting).

Thanks,
Rafael

  reply	other threads:[~2008-05-02 17:41 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 [this message]
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
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=200805021941.08003.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