From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: Martin Lorenz <martin-2WKW0nu+7nMiq3RsQ1AnAw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: sleep states - maybe a dumb question...
Date: Sun, 28 Mar 2004 15:31:51 +0200 [thread overview]
Message-ID: <20040328133150.GC1453@openzaurus.ucw.cz> (raw)
In-Reply-To: <40642CDA.6070007-2WKW0nu+7nMiq3RsQ1AnAw@public.gmane.org>
Hi!
> maybe this is a very dumb question, but I did not find an answer in
> the docs. (or I was not looking at the right place)
>
> I see two different sleep-state capabilities on my laptop (run by a
> transmeta cursoe CPU) running 2.6.4 vanilla kernel and a debian
> unstable system.
>
> # cat /proc/acpi/sleep
> S0 S3 S4 S5
>
> # cat /sys/power/state
> standby mem disk
>
> as I understand 'standby' is synonymous to 'S1', which is not showing
> up in the /proc version...
>
> when issuing echo -n standby > /sys/power/state the system acts as if
> it would go to standby (switch to console, some output saying so,
> etc.) but resumes immediately.
>
> what does that mean?
> does my laptop lack S1/standby capability?
Bug in Patricks code. It should not announce standby when
no S1 is available. Oh and it indeed is very igly to have
2 interfaces for same thing; hopefully that will get fixed, too.
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
prev parent reply other threads:[~2004-03-28 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 13:15 sleep states - maybe a dumb question Martin Lorenz
[not found] ` <40642CDA.6070007-2WKW0nu+7nMiq3RsQ1AnAw@public.gmane.org>
2004-03-28 13:31 ` Pavel Machek [this message]
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=20040328133150.GC1453@openzaurus.ucw.cz \
--to=pavel-alswssmvlrq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=martin-2WKW0nu+7nMiq3RsQ1AnAw@public.gmane.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