Bug 437672 - 1000Hz timer still active on tickless kernel
1000Hz timer still active on tickless kernel
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-03-15 22:47 EDT by Michael Cronenworth
Modified: 2008-03-15 23:23 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-03-15 23:23:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
dmesg.txt (28.18 KB, text/plain)
2008-03-15 22:47 EDT, Michael Cronenworth
no flags Details
lspci.txt (26.04 KB, text/plain)
2008-03-15 22:48 EDT, Michael Cronenworth
no flags Details
powertop.txt (792 bytes, text/plain)
2008-03-15 22:50 EDT, Michael Cronenworth
no flags Details

  None (edit)
Description Michael Cronenworth 2008-03-15 22:47:35 EDT
Description of problem: Powertop reports that a 1000Hz timer is still active.
This prevents the CPU from sleeping.

Version-Release number of selected component (if applicable): kernel-

How reproducible: Always

Steps to Reproduce:
1. Boot Kernel
2. Sit at idle
Actual results: ~1600 wakeups

Expected results: ~500 or lower wakeups

Additional info: Attaching lspci, dmesg, and powertop outputs.

This does not happen on my Pentium 4 3ghz HT-enabled 32-bit machine. Same
packages installed.
Comment 1 Michael Cronenworth 2008-03-15 22:47:35 EDT
Created attachment 298174 [details]
Comment 2 Michael Cronenworth 2008-03-15 22:48:01 EDT
Created attachment 298175 [details]
Comment 3 Michael Cronenworth 2008-03-15 22:50:53 EDT
Created attachment 298176 [details]
Comment 4 Dave Jones 2008-03-15 23:23:22 EDT
it's because of the IR receiver on your TV card.  AFAICT, this is a limitation
of the hardware (it doesn't appear to send an interrupt when it receives an IR
event, so the kernel has to poll frequently to see if something happened).  If
we lower the polling frequency, we may end up missing events.

Note You need to log in before you can comment on or make changes to this bug.