public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Derek Broughton <dbroughton-F3m4/jXepmf3fQ9qLvQP4Q@public.gmane.org>
To: ACPI Development - Sourceforge
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH][2.4] acpi S5 poweroff fix
Date: Wed, 30 Apr 2003 09:09:19 -0300	[thread overview]
Message-ID: <03ea01c30f11$53ec94a0$3746028e@bio.dfo.ca> (raw)
In-Reply-To: 20030429181518.96485.qmail@web41601.mail.yahoo.com

From: "willy tarreau" <wtarreau-Qt13gs6zZMY@public.gmane.org>

> Although I'm not sure that the second case affects everybody, because it might
> be caused by side-effects, but from what I've understood from the code, I'm
> pretty sure that nobody can power off by echoing 5 to /proc/acpi/sleep !

Mostly we wouldn't want to.  iirc, there was some discussion here about not even
permitting "echo 5 >/proc/acpi/sleep".  If I am forced to recover from the (too
frequent) situation where my laptop freezes and ignores the keyboard, I have to
hold down the power button for 4 or 5 seconds, as you mention.  But that, like
S5, is an abrupt power-off.  Generally, I'd want to go through init and do it
gracefully.  Pushing the power button once is enough to generate a power button
event in acpi, and then acpid shuts the machine down using '/sbin/init 0'



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-04-30 12:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 18:15 [PATCH][2.4] acpi S5 poweroff fix willy tarreau
2003-04-30 12:09 ` Derek Broughton [this message]
     [not found]   ` <03ea01c30f11$53ec94a0$3746028e-dP0OE4Ef7fWw5LPnMra/2Q@public.gmane.org>
2003-04-30 13:42     ` Ducrot Bruno
     [not found] ` <20030429181518.96485.qmail-NXgsjPK8tUaA/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2003-04-30 14:29   ` Markus Gaugusch
2003-04-30 15:02     ` Derek Broughton
     [not found]     ` <Pine.LNX.4.53.0304301628010.4213-sxQ525G0OhRQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
2003-04-30 19:38       ` Karol Kozimor
     [not found]         ` <20030430193855.GA21497-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-05-02  8:44           ` Ducrot Bruno
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12  8:35 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F842722F6-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-05-13 12:43   ` Ducrot Bruno

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='03ea01c30f11$53ec94a0$3746028e@bio.dfo.ca' \
    --to=dbroughton-f3m4/jxepmf3fq9qlvqp4q@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