From: Martin Aspeli <optilude@gmx.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: How can I trace ACPI events?
Date: Sat, 11 Oct 2003 16:52:24 +0100 [thread overview]
Message-ID: <oprwvydmtg9y0cdf@mail.gmx.net> (raw)
Hello,
I'm having trouble with ACPI on my Centrino notebook; if ACPI is disabled,
a lot of my PCI devices (e.g. onboard sound) don't get any IRQ. If ACPI is
enabled, the system boots fine, but about a minute after startup, for no
obvious reason keventd ("events/0", PID 3) starts chewing 99.9% CPU and
the fan starts spinning at maximum. This is with 2.6.0-test7, although
I've had the same problem in all kernels I've tried on this box (from
2.4.22-ac through from 2.6.0-test5 to -test7). Chris Wright suggested
runaway ACPI events could cause events/0 to chew CPU, which seems
consistent with what I'm seeing here.
If I am to diagnose it further, though, I'll have to figure out what ACPI
events (if any) are causing the massive spikes in CPU usage. How can I
trace this? I've had acpid running, but the log in /var/log/acpid only
shows simple messages (started service, registered 1 rule). Nothing
particularly interesting from dmesg or TTY 12, either.
CC'd replies would be appreciated.
Thanks,
Martin
reply other threads:[~2003-10-11 15:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=oprwvydmtg9y0cdf@mail.gmx.net \
--to=optilude@gmx.net \
--cc=linux-kernel@vger.kernel.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