From: Faye Pearson <faye-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: constant processor 0x80 events
Date: Tue, 31 Dec 2002 21:12:59 +0000 [thread overview]
Message-ID: <20021231211259.GA28810@clara.net> (raw)
This is probably a DSDT problem but I'm bewildered as to where to look
now, so would really appreciate any advice people can offer.
When the machine becomes under load for a while, or is hot already and
the processor is under load, then the CPU time in system becomes very
high, /proc/acpi/event is constantly printing:
processor CPU0 00000080 00000000
processor CPU0 00000080 00000000
processor CPU0 00000080 00000000
There are constantly starting and dying kacpidp processes -
top is almost always showing 1 or 2 zombie processes (kacpidp) and the
load average sticks around 2.0.
It used to also run the fan at it's maximum RPM which I didn't feel was
healthy so I've panicked and switched it off quickly to change kernels
back to a non-acpi version which doesn't have this problem - even under
consistent heavy load.
I added this CHTR call (it wasn't being called before) and that seems to
stave off the problem for a while.. while programs are running, there
isn't a steady rise in temperature, the temperature is seemingly all
over the place. It will get up to 82 and then suddenly drop to 59.
Even when the load is going mad now, the fan is only on its high, not
critical level.
5180 Store (Local0, Local2)
5181 Multiply (Local0, 0x0A, Local1)
5182 Add (Local1, TBSE, Local0)
5183 Store ("Current Temperature K is
----------- ", Debug)
5184 Store (Local0, Debug)
5185 CHTR (Local2)
5186 Return (Local0)
I've put my dsdt, and the dsl (from iasl 021205) on my website at
http://dude.noc.clara.net/~faye/dsdt
http://dude.noc.clara.net/~faye/dsdt.dsl
I've never used the kernel debugger before but I'm happy to get my hands
dirty if it will help solve the problem.
Faye
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2002-12-31 21:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 21:12 Faye Pearson [this message]
[not found] ` <20021231211259.GA28810-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2003-01-01 12:30 ` constant processor 0x80 events Adachi, Kenichi
[not found] ` <000101c2b191$93b74130$2d2202d3-F8JvWDuGsZU@public.gmane.org>
2003-01-01 13:55 ` Adachi, Kenichi
2003-01-01 16:40 ` 'Faye Pearson'
[not found] ` <20030101164052.GA31172-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2003-01-01 17:58 ` Adachi, Kenichi
[not found] ` <20030101192644.GA31476@clara.net>
[not found] ` <20030101192644.GA31476-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2003-01-02 10:15 ` Faye Pearson
[not found] ` <20030102101513.GA947-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2003-01-02 13:52 ` Adachi, Kenichi
2003-01-02 13:59 ` Faye Pearson
[not found] ` <20030102135937.GA9257-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2003-01-02 17:29 ` Adachi, Kenichi
[not found] ` <000201c2b284$89a033c0$232202d3-F8JvWDuGsZU@public.gmane.org>
2003-01-02 22:03 ` Faye Pearson
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=20021231211259.GA28810@clara.net \
--to=faye-6jsjyq0qj1reowh0uzbu5w@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