From: Dominik Brodowski <linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
To: Damien Elmes <damien-voeRRA98qc6eZLLa646FqQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Cardbus + ACPI weirdness on a Compaq laptop
Date: Wed, 21 Apr 2004 17:14:39 +0200 [thread overview]
Message-ID: <20040421151439.GD7389@dominikbrodowski.de> (raw)
In-Reply-To: <86y8oph3pw.fsf-oYM03kX4ec6+8CgqdUn7AQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2209 bytes --]
Hi,
On Wed, Apr 21, 2004 at 10:15:23PM +0900, Damien Elmes wrote:
> The actual events seem strange (to me at least, an ACPI newbie) - I
> imagine "PWRB" is the power button and "PCIB" is the PCI bus? Both
> events are generated about 350 times a second:
These names are not standardized, IIRC, but most likely they mean PCI Bus
and PoWeR Button in your case.
> 22:12:53 Execute Method: [\_GPE._L0B] (Node c12c5208)
> 22:12:53 evmisc-0135 [442] ev_queue_notify_reques: Dispatching Notify(2) on node c12d4528
> 22:12:53 evmisc-0139 [442] ev_queue_notify_reques: Notify value: Device Wake
> 22:12:53 evmisc-0200 [442] ev_queue_notify_reques: No notify handler for [PCIB] node c12d4528
> 22:12:53 evmisc-0135 [442] ev_queue_notify_reques: Dispatching Notify(2) on node c12d8528
> 22:12:53 evmisc-0139 [442] ev_queue_notify_reques: Notify value: Device Wake
> 22:12:53 evmisc-0200 [442] ev_queue_notify_reques: No notify handler for [PWRB] node c12d8528
> 22:12:53 acpi_bus-0494 [435] acpi_bus_notify : Received DEVICE WAKE notification for device [PCIB]
> 22:12:53 acpi_bus-0494 [435] acpi_bus_notify : Received DEVICE WAKE notification for device [PWRB]
> 22:12:53 Execute Method: [\_GPE._L0B] (Node c12c5208)
> 22:12:53 evmisc-0135 [442] ev_queue_notify_reques: Dispatching Notify(2) on node c12d4528
> 22:12:53 evmisc-0139 [442] ev_queue_notify_reques: Notify value: Device Wake
> 22:12:53 evmisc-0200 [442] ev_queue_notify_reques: No notify handler for [PCIB] node c12d4528
> 22:12:53 evmisc-0135 [442] ev_queue_notify_reques: Dispatching Notify(2) on node c12d8528
> 22:12:53 evmisc-0139 [442] ev_queue_notify_reques: Notify value: Device Wake
> 22:12:53 evmisc-0200 [442] ev_queue_notify_reques: No notify handler for [PWRB] node c12d8528
> 22:12:53 acpi_bus-0494 [435] acpi_bus_notify : Received DEVICE WAKE notification for device [PCIB]
> 22:12:53 acpi_bus-0494 [435] acpi_bus_notify : Received DEVICE WAKE notification for device [PWRB]
Try passing acpi_leave_gpes_disabled to the kernel command line.
The handling of Wake GPEs has been a cause of trouble in the past few weeks,
but soon the ACPI Core Architecture will handle GPEs better.
Dominik
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-21 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 4:10 Cardbus + ACPI weirdness on a Compaq laptop Damien Elmes
[not found] ` <864qrem0mm.fsf-oYM03kX4ec6+8CgqdUn7AQ@public.gmane.org>
2004-04-21 13:15 ` Damien Elmes
[not found] ` <86y8oph3pw.fsf-oYM03kX4ec6+8CgqdUn7AQ@public.gmane.org>
2004-04-21 15:14 ` Dominik Brodowski [this message]
[not found] ` <20040421151439.GD7389-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-04-22 7:54 ` Damien Elmes
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=20040421151439.GD7389@dominikbrodowski.de \
--to=linux-x3ehhduj6siigcdfoqap7bvvk+yq3zxh@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=damien-voeRRA98qc6eZLLa646FqQ@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