From: Thomas Meyer <thomas@m3y3r.de>
To: Len Brown <lenb@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: ACPI: EC: evaluating _Q10
Date: Wed, 03 Jan 2007 08:46:24 +0100 [thread overview]
Message-ID: <459B5F50.8010703@m3y3r.de> (raw)
In-Reply-To: <200701022241.05303.lenb@kernel.org>
Len Brown schrieb:
>>> The bigger question is why you get "tons of these" --
>>> as EC events are usually infrequent.
>>> Do you have a big number next to "acpi" in /proc/interrupts?
>>> If so, at what rate is it growing?
>>>
>> maybe tons were a bit to overstated... After a fresh reboot, i count 110
>> _q10 and one _q21messages now with 8 min. uptime and around 10300 acpi
>> interrupts.
>>
>
> 480 sec/110 ec events = 4 seconds/event. This doesn't worry me.
> Could be battery updates, thermal updates etc.
>
> 480/10300 = an interrupt every 46 ms.
> This is certainly not right.
> Have you always seen runaway acpi interrupts on this box, no matter the kernel?
>
To be honest i didn't care and knew about that this could be an problem
until now. But the biggest part of the acpi interrupts seems to happen
while the first minutes, maybe while booting because with 22 min. uptime
i get these values:
CPU0 CPU1
0: 413784 0 IO-APIC-edge timer
9: 14544 0 IO-APIC-fasteoi acpi
24 min. uptime:
CPU0 CPU1
0: 435875 0 IO-APIC-edge timer
9: 15247 0 IO-APIC-fasteoi acpi
26 min. uptime:
0: 470428 0 IO-APIC-edge timer
9: 16251 0 IO-APIC-fasteoi acpi
So let's say approximatley 700 to 1000 acpi interrupts in 120 seconds. I
guess this sounds better, doesn't it?
prev parent reply other threads:[~2007-01-03 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-01 14:56 ACPI: EC: evaluating _Q10 Thomas Meyer
2007-01-02 17:05 ` Len Brown
2007-01-02 20:32 ` Thomas Meyer
2007-01-03 3:41 ` Len Brown
2007-01-03 7:46 ` Thomas Meyer [this message]
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=459B5F50.8010703@m3y3r.de \
--to=thomas@m3y3r.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--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