public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: tierra.y.libertad-hi6Y0CQ0nG0@public.gmane.org
To: Linux ACPI Devel Mailing List
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Cc: Tony.Glader-cP9NhJtB8odr1ooMESYBxBZCeNDtXRbv@public.gmane.org
Subject: Re: No events when pressing power button
Date: Sat, 3 Aug 2002 21:44:06 +0200 (MEST)	[thread overview]
Message-ID: <20020803194522.357575086@marcos.python.subname.de> (raw)

On  2 Aug, Tony Glader wrote:
> On Fri, 2 Aug 2002, Aaron Gaudio wrote:
> 
>> If you want to read from /proc/acpi/event directly, kill acpid.
>> Otherwise, the event will be consumed by acpid and you'll never see
>> anything on
>> /proc/acpi/event.
> 
> Of course I killed acpid. Otherwise I just got something like 'Device
> or resource busy'.

Have you already tried an UP kernel without IOAPIC support?
My Dual PII board has the same problem but events are working without
IOAPIC interrupt routing.

> I also noticed that ACPI doesn't power off everytime my computer when
> I shutdown it. About in 50% shutdowns it powers off and 50% doesn't.

Same problem with my board. I posted it here several times, but it seems
that nobody has an idea about its solution.

-- 
Rüdiger
--------------------------------------------------
pgp/gpg public-key at
http://home.htp-tel.de/ruedigerotte/key.html



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

             reply	other threads:[~2002-08-03 19:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-03 19:44 tierra.y.libertad-hi6Y0CQ0nG0 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-15 15:00 No events when pressing power button Grover, Andrew
     [not found] ` <EDC461A30AC4D511ADE10002A5072CAD0236DD94-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-08-16  8:04   ` Ducrot Bruno
     [not found]     ` <20020816080416.GB10248-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2002-08-16 20:58       ` Andreas Koenecke
2002-08-13 18:33 Grover, Andrew
     [not found] ` <EDC461A30AC4D511ADE10002A5072CAD0236DD85-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-08-13 21:01   ` Arndt Schoenewald
2002-08-15 13:42     ` Martin Platter
     [not found]       ` <3D5BAFD5.2030500-hi6Y0CQ0nG0@public.gmane.org>
2002-08-15 15:12         ` Arndt Schoenewald
     [not found]           ` <20020815151250.GC21746-dzH3swnhYuu5cqaZGqYS/O8dC6aEkcuFVpNB7YpNyf8@public.gmane.org>
2002-08-15 20:23             ` tierra.y.libertad-hi6Y0CQ0nG0
2002-08-15  7:30   ` Tony Glader
2002-08-01 21:11 Tony Glader
     [not found] ` <Pine.LNX.4.44.0208020007200.7699-100000-cP9NhJtB8odr1ooMESYBxBZCeNDtXRbv@public.gmane.org>
2002-08-02  6:26   ` Aaron Gaudio
     [not found]     ` <20020802022638.A10668-2LEdZMXKCZJeeLb3ft/vUmD2FQJk+8+b@public.gmane.org>
2002-08-02  6:36       ` Tony Glader
2002-08-06  3:27 ` Sérgio Monteiro Basto

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=20020803194522.357575086@marcos.python.subname.de \
    --to=tierra.y.libertad-hi6y0cq0ng0@public.gmane.org \
    --cc=Tony.Glader-cP9NhJtB8odr1ooMESYBxBZCeNDtXRbv@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