public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Éric Brunet" <Eric.Brunet-l5PIGlIYzrxGWvitb5QawA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: swsuspend in linux 2.6.0-pre4
Date: Tue, 26 Aug 2003 17:34:38 +0200	[thread overview]
Message-ID: <20030826153437.GA13129@lps.ens.fr> (raw)

Hello all,

I associate software suspend with ACPI, so I send this message on this
list, but maybe this is the wrong place...

I tried 2.6.0-pre4 on my computer.  First I was surprised to see that
/proc/acpi/sleep disapeared. Ok, there is probably a good reason, it is
not my place to contest anything.

To try to suspend my computer, I read the documentation, mounted
/sys and looked in /sys/power/state. Second surprise, the file only
contains an empty line. If I believe Documentation/power/interface.txt,
this file should contain "standby mem disk". Or does the kernel claim
that my computer is completely unable of any kind of suspend ? Is that
even possible ? On boot, the acpi subsystem proudly claims that my
computer supports S0 S1 S4 S5. (Ok, maybe sys/power/state should only
contain "standby disk".)

If I try to echo something to /sys/power/state (anything... Not just
standby, mem or disk), the screen goes blank a second and goes back to
normal, the computer fully alive. In the logs, two lines:
	Stopping tasks: =================================================|
	Restarting tasks... done

In 2.6.0-pre1 (the last kernel I compiled before the present one), when I
echoed 1 or 4 to /proc/acpi/sleep, the computer did at least tried
something. For S1, after 5 seconds of putting task in the refrigerator,
the computer was back to normal operation. For S4, the computer achieved
suspend to disk sometimes (but never resumed) or oopsed trying. It was
comforting to know that, even if it was suicide for the computer, at
least it tried to suspend, and there was some hope that it would improve
in time. But now, nothing.

I tried also to boot 2.6.0-pre4 with acpi=off. /sys/power/state is still
empty, but I had a oops and a complete hang of the computer when I tried
to echo disk (I think, I will try again) to it. Encouraging, in some way,
but is ACPI an obstacle to suspending ? Weird. (I didn't have enough
energy to copy the oops by hand. I'll do it, if you believe it is worth
it.)

The kernel is compiled with CONFIG_SOFTWARE_SUSPEND, CONFIG_ACPI,
CONFIG_ACPI_SLEEP and CONFIG_ACPI_DEBUG.

I have tried this with a kernel without APIC or IO-APIC and with
pci=noacpi, and again with a kernel with APIC and IO-APIC without the
command line option pci=acpi.

The full .config file, boot messages, dsdt and many other information is
available on http://perso.nerim.net/~tudia/bug-reports

Éric Brunet


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0

                 reply	other threads:[~2003-08-26 15:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030826153437.GA13129@lps.ens.fr \
    --to=eric.brunet-l5pigliyzrxgwvitb5qawa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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