lkml.org 
[lkml]   [2007]   [Jan]   [3]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateWed, 03 Jan 2007 08:46:24 +0100
FromThomas Meyer <>
SubjectRe: ACPI: EC: evaluating _Q10
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?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-01-03 07:49    [from the cache]
©2003-2008