From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Chad LeClair <sesca256-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI events generated on PCI usage.
Date: 09 Feb 2004 23:03:58 -0500 [thread overview]
Message-ID: <1076385838.4105.495.camel@dhcppc4> (raw)
In-Reply-To: <20040207224901.34064.qmail-D/IqPAlx7LewAeGFf/znCBupM2+RrINj@public.gmane.org>
Chad,
Please file a bug and attach the output of acpidmp with full dmesg.
thanks,
-Len
On Sat, 2004-02-07 at 17:49, Chad LeClair wrote:
> Since upgrading to the 2.6 series of kernel I have
> noticed the events/0 process consuming processor time
> any time I use a PCI device. For example, when I play
> sound on my SB Live, the events/0 consumes ~15% of my
> processor. It doesn't effect AGP, or onboard devices.
> I turned ACPI debugging on and found that when these
> devies are in use a constant stream of DEVICE WAKE
> events are generated.
>
> Is there any way to prevent or ignore these events to
> avoid wasting processor time on them?
>
> Debug log with debug_level=0xff:
>
...
> acpi_bus-0492 [15] acpi_bus_notify : Received
> DEVICE WAKE notification for device [PCI0]
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-10 4:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 22:49 ACPI events generated on PCI usage Chad LeClair
[not found] ` <20040207224901.34064.qmail-D/IqPAlx7LewAeGFf/znCBupM2+RrINj@public.gmane.org>
2004-02-10 4:03 ` Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-09 18:26 Chad LeClair
2004-02-11 5:41 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=1076385838.4105.495.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sesca256-/E1597aS9LQAvxtiuMwx3w@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.