Bug 443867

Summary: acpi generates lot of interrupts according to powertop
Product: [Fedora] Fedora Reporter: Juha Heljoranta <juha.heljoranta>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 9CC: kernel-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-14 15:45:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmidecode (serial and uuid removed from system information) none

Description Juha Heljoranta 2008-04-23 19:28:15 UTC
Description of problem:
PowerTOP shows large amount of interrupts generated by acpi:
Wakeups-from-idle per second : 278.8    interval: 10.0s
Power usage (ACPI estimate): 20.2W (2.1 hours)

Top causes for wakeups:
  91.9% (2544.1)       <interrupt> : acpi 
   3.0% ( 82.3)       <interrupt> : uhci_hcd:usb3, i915@pci:0000:00:02.0 
   1.8% ( 49.6)      <kernel IPI> : Rescheduling interrupts 

This causes laptop battery to drain fast while doing nothing.


Version-Release number of selected component (if applicable):
kernel-2.6.25-1.fc9.x86_64
 
Actual results:
lot of acpi generated interrupts

Expected results:
reasonable amount of interrupts from acpi

Additional info:
According to top the kacpid eats constantly over 4 % of the cpu:
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND           
                                                                               
                 
   64 root      15  -5     0    0    0 S  4.3  0.0   1:10.62 kacpid            
              

Same problem is also in F8.

Comment 1 Juha Heljoranta 2008-04-23 19:28:15 UTC
Created attachment 303541 [details]
dmidecode (serial and uuid removed from system information)

Comment 2 Bug Zapper 2008-05-14 10:01:45 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2009-06-10 00:23:09 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-07-14 15:45:28 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.