From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
Pavel Machek <pavel@suse.cz>, Ingo Molnar <mingo@elte.hu>
Subject: Re: ACPI: S4 disappeared [mmotm 2009-02-10-16-35]
Date: Wed, 11 Feb 2009 16:43:09 +0100 [thread overview]
Message-ID: <200902111643.10191.rjw@sisk.pl> (raw)
In-Reply-To: <4992A59F.5090502@gmail.com>
On Wednesday 11 February 2009, Jiri Slaby wrote:
> On 02/11/2009 09:51 AM, Jiri Slaby wrote:
> > On 02/11/2009 01:36 AM, akpm@linux-foundation.org wrote:
> >> The mm-of-the-moment snapshot 2009-02-10-16-35 has been uploaded
> >
> > Hi,
> >
> > I've found out, that S4 disappeared in this release, in comparison to mmotm
> > based on 2.6.29-rc2:
> > -ACPI: (supports S0 S1 S3 S4 S5)
> > +ACPI: (supports S0 S1 S3 S5)
> >
> > Any ideas what could have caused this?
>
> I think this one
> ARCH_HIBERNATION_POSSIBLE=n
> because
> SMP=y
> since
> config ARCH_HIBERNATION_POSSIBLE
> def_bool y
> - depends on !SMP || !X86_VOYAGER
> + depends on !SMP
>
> The condition was wrong, ok, anyway it worked. Would
> depends on !SMP || EXPERIMENTAL
> make sense? The smp is handled in disable_nonboot_cpus manner, right?
Ah, someone removed X86_VOYAGER and left this gem. I guess that went in
through -tip (Ingo CCed).
After removing X86_VOYAGER, ARCH_HIBERNATION_POSSIBLE should always be set
on x86. Just make it
config ARCH_HIBERNATION_POSSIBLE
def_bool y
Thanks,
Rafael
next prev parent reply other threads:[~2009-02-11 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200902110036.n1B0aBZs013975@imap1.linux-foundation.org>
2009-02-11 8:51 ` ACPI: S4 disappeared [mmotm 2009-02-10-16-35] Jiri Slaby
2009-02-11 10:17 ` Jiri Slaby
2009-02-11 15:43 ` Rafael J. Wysocki [this message]
2009-02-11 16:22 ` Ingo Molnar
2009-02-11 21:22 ` Rafael J. Wysocki
2009-02-13 9:37 ` Pavel Machek
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=200902111643.10191.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=jirislaby@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=pavel@suse.cz \
/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