From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: (fwd) empty /sys/power/state?
Date: Sun, 20 May 2007 01:18:49 +0200 [thread overview]
Message-ID: <464F85D9.30707@s5r6.in-berlin.de> (raw)
In-Reply-To: <464F8395.4080300@s5r6.in-berlin.de>
I wrote:
> Rafael J. Wysocki wrote:
>> Can you please try to set CONFIG_SOFTWARE_SUSPEND and see if that helps?
>
> I will do so. BTW,
>
> config SOFTWARE_SUSPEND
> bool "Software Suspend (Hibernation)"
> depends on PM && SWAP && (((X86 || PPC64_SWSUSP) && (!SMP ||
> SUSPEND_SMP)) || ((FRV || PPC32) && !SMP))
>
> and
>
> config SUSPEND_SMP
> bool
> depends on HOTPLUG_CPU && (X86 || PPC64) && PM
>
> So, no HOTPLUG_CPU -> no SOFTWARE_SUSPEND. I don't expect a
> single-processor, dual-core PC to require CPU hotplugging support.
As a first step, I enabled HOTPLUG_CPU and SUSPEND_SMP, i.e. did not
enable SOFTWARE_SUSPEND yet.
# cat /sys/power/state
mem
# echo m >/sys/power/state
PC goes to sleep.
Thanks so far.
(Alas it doesn't wake up anymore. But that's another issue for another
day. I had all drivers loaded when I did this.)
--
Stefan Richter
-=====-=-=== -=-= =-=--
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-05-19 23:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <464F53C2.8070802@s5r6.in-berlin.de>
2007-05-19 19:55 ` (fwd) empty /sys/power/state? Stefan Richter
2007-05-19 20:07 ` Stefan Richter
2007-05-19 20:15 ` Stefan Richter
2007-05-19 21:15 ` Alan Stern
2007-05-19 21:39 ` Stefan Richter
2007-05-19 22:53 ` Rafael J. Wysocki
2007-05-19 23:09 ` Stefan Richter
2007-05-19 23:18 ` Stefan Richter [this message]
2007-05-19 23:20 ` Rafael J. Wysocki
2007-05-19 23:33 ` Stefan Richter
2007-05-19 23:49 ` Stefan Richter
2007-05-20 12:36 ` Rafael J. Wysocki
2007-05-20 13:19 ` Stefan Richter
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=464F85D9.30707@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.