All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nils Faerber <nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
To: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: /proc/acpi/sleep behaviour?
Date: Tue, 4 Mar 2003 18:40:35 +0100	[thread overview]
Message-ID: <20030304184035.6ace16db.nils@kernelconcepts.de> (raw)
In-Reply-To: <20030304172226.GD7861-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>

On Tue, 4 Mar 2003 18:22:26 +0100
Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> wrote:
> On Tue, Mar 04, 2003 at 05:54:46PM +0100, Nils Faerber wrote:
> > Just a short question:
> > 	How is sleep supposed to work?
> > When I do a 
> > 	echo -n 4 > /proc/acpi/sleep
> > on recent ACPI kernels (2.4.21-pre4 with ACPI 20030228 + swsusp beta
> > 19) everything works quite fine but the "echo" never returns. After
> > resume I have to kill "echo".
> Last time I checked, the swsusp support is not well integrated.
> I can not tell though for recent swsusp patches.

I can't judge this either but the same in my eyes misbehaviour is IMHO
also true for 2.5.6x kernels without directly involved swsusp so I would
suspect this to be more of an ACPI problem...

> please use /proc/sys/kernel/suspend instead.
Err... /proc/sys/kernel/swsusp you ment, right?

> Forgot to say also that you should bug report to swsusp mailing list.
That's true, sorry!

> Ducrot Bruno
CU
  nils faerber

-- 
kernel concepts          Tel: +49-271-771091-12
Dreisbachstr. 24         Fax: +49-271-771091-19
D-57250 Netphen          D1 : +49-170-2729106
--


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

  parent reply	other threads:[~2003-03-04 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04 16:54 /proc/acpi/sleep behaviour? Nils Faerber
     [not found] ` <20030304175446.3930bcb7.nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
2003-03-04 17:22   ` Ducrot Bruno
     [not found]     ` <20030304172226.GD7861-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-03-04 17:40       ` Nils Faerber [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-18  5:45 Yu, Luming

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=20030304184035.6ace16db.nils@kernelconcepts.de \
    --to=nils-t93ne7xhvje5bsectf/tx7nah6klmebb@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@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 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.