From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [BUG] [linux-pm] Commit "Hibernation: Enter platform hibernation state in a consistent way)" makes my system to resume instantly from S4
Date: Sun, 28 Oct 2007 21:23:15 +0100 [thread overview]
Message-ID: <200710282123.15653.rjw@sisk.pl> (raw)
In-Reply-To: <200710282200.53910.maximlevitsky@gmail.com>
On Sunday, 28 October 2007 21:00, Maxim Levitsky wrote:
> On Saturday 27 October 2007 23:46:45 Rafael J. Wysocki wrote:
> > On Saturday, 27 October 2007 14:05, Maxim Levitsky wrote:
> > > Hi,
> > >
> > > Recently I noticed that my system resumes just after suspend to disk.
> > >
> > > I traced this to commit 9cd9a0058dd35268b24fa16795a92c800f4086d4.
> > >
> > > Note:
> > >
> > > This happens only if I enable WOL using /proc/acpi/wakeup
> > > (echo "ILAN" > /proc/acpi/wakeup)
> >
> > What happens after a suspend to RAM?
> I do more testing tomorrow, but what I remember is that,
> I had no issues with suspend-to-ram.
> (And take into account the fact that _all_ wakeup devices were enabled always,
> the rc.local does that for me, and still I did quite a lot of suspends, but I
> got the immediate resume, only and always after suspend to disk.
Hm, can you please retest with the above commit applied, but with
device_suspend() in hibernation_platform_enter() replaced by device_shutdown()?
> > > and have
> > > "ACPI-Hibernate-erroneously-disabled-Suspend-wakeup" applied, since otherwise
> > > all wake-up sources are disabled in S4.
> > >
> > >
> > > Clearly the above commit confuses the BIOS.
> > > Using latest -git with the above patch reverted makes everything work again fine.
> >
> > Well, this patch is needed to make wakeup from peripherals (eg. RTC alarm) work
> > on some boxes.
> >
> > The symptom that you describe is similar to what I'm observing after a suspend
> > to RAM on one test box.
> >
> > Can you produce a log of kernel messages printed before powering off the
> > system?
> How :-)
>
> (I will try to set up netconsole, and turn on acpi debugging, maybe this will help)
Yes, I meant something like this.
Greetings,
Rafael
next prev parent reply other threads:[~2007-10-28 20:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 12:05 [BUG] [linux-pm] Commit "Hibernation: Enter platform hibernation state in a consistent way)" makes my system to resume instantly from S4 Maxim Levitsky
2007-10-27 21:46 ` Rafael J. Wysocki
2007-10-28 20:00 ` Maxim Levitsky
2007-10-28 20:23 ` Rafael J. Wysocki [this message]
2007-10-29 6:45 ` Maxim Levitsky
2007-10-29 20:37 ` Rafael J. Wysocki
2007-10-29 22:36 ` Maxim Levitsky
2007-10-29 23:31 ` Rafael J. Wysocki
2007-11-01 15:25 ` Maxim Levitsky
2007-11-01 17:03 ` Rafael J. Wysocki
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=200710282123.15653.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=maximlevitsky@gmail.com \
/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