From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Arjan van de Ven <arjan@linux.intel.com>
Subject: Rescheduling interrupts
Date: Tue, 22 Jan 2008 01:19:38 +0200 [thread overview]
Message-ID: <200801220119.42312.caglar@pardus.org.tr> (raw)
[-- Attachment #1: Type: text/plain, Size: 2704 bytes --]
Hi;
With Linus's latest git, powertop reports following while system nearly %100
idle;
PowerTOP version 1.9 (C) 2007 Intel Corporation
Cn Avg residency P-states (frequencies)
C0 (cpu running) ( 6,3%) 1,84 Ghz 0,4%
C1 0,0ms ( 0,0%) 1333 Mhz 0,0%
C2 0,1ms ( 0,5%) 1000 Mhz 99,6%
C3 3,7ms (93,2%)
Wakeups-from-idle per second : 306,8 interval: 10,0s
Power usage (5 minute ACPI estimate) : 23,1 W (0,5 hours left)
Top causes for wakeups:
59,9% (238,4) <kernel IPI> : Rescheduling interrupts
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
14,7% ( 58,6) amarokapp : schedule_timeout (process_timeout)
5,5% ( 21,9) java : futex_wait (hrtimer_wakeup)
5,0% ( 19,8) <interrupt> : iwl3945
2,5% ( 10,0) java : schedule_timeout (process_timeout)
2,5% ( 10,0) <kernel core> : ehci_work (ehci_watchdog)
2,5% ( 10,0) <interrupt> : extra timer interrupt
1,6% ( 6,4) artsd : schedule_timeout (process_timeout)
1,0% ( 4,0) <kernel module> : usb_hcd_poll_rh_status (rh_timer_func)
0,5% ( 2,0) <interrupt> : ohci1394, uhci_hcd:usb4, nvidia
0,5% ( 2,0) <kernel core> : clocksource_check_watchdog
(clocksource_watchdog)
0,5% ( 2,0) kwin : schedule_timeout (process_timeout)
0,5% ( 1,9) wpa_supplicant : schedule_timeout (process_timeout)
0,3% ( 1,2) kdesktop : schedule_timeout (process_timeout)
0,3% ( 1,0) kwrapper : do_nanosleep (hrtimer_wakeup)
0,3% ( 1,0) klipper : schedule_timeout (process_timeout)
0,3% ( 1,0) artsd : do_setitimer (it_real_fn)
0,3% ( 1,0) gpg-agent : schedule_timeout (process_timeout)
0,3% ( 1,0) X : nv_start_rc_timer (nv_kern_rc_timer)
0,3% ( 1,0) kicker : schedule_timeout (process_timeout)
0,1% ( 0,5) iwl3945 : ieee80211_authenticate
(ieee80211_sta_timer)
0,1% ( 0,5) <kernel core> : neigh_table_init_no_netlink
(neigh_periodic_timer)
This "<kernel IPI> : Rescheduling interrupts" causes at least 200 wakeups
(sometimes i see ~400 wakeups) for me and a quick google search yields [1],
but i didn't see this reported to LKML, so here it is :).
If anything else is needed please yell...
[1] http://www.mail-archive.com/power@bughost.org/msg01009.html
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-01-21 23:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 23:19 S.Çağlar Onur [this message]
2008-01-22 10:57 ` Rescheduling interrupts Ingo Molnar
2008-01-22 12:55 ` S.Çağlar Onur
2008-01-22 15:23 ` Ingo Molnar
2008-01-22 15:37 ` Ingo Molnar
2008-01-22 16:00 ` S.Çağlar Onur
2008-01-22 15:55 ` S.Çağlar Onur
2008-01-22 16:05 ` Ingo Molnar
2008-01-22 16:11 ` S.Çağlar Onur
2008-01-22 16:22 ` S.Çağlar Onur
2008-01-22 17:03 ` Matt Mackall
2008-01-22 19:27 ` Ingo Molnar
[not found] ` <p73fxwoncs4.fsf@crumb.suse.de>
2008-01-23 15:52 ` Matt Mackall
2008-05-13 18:03 ` Vegard Nossum
2008-05-13 19:04 ` Vegard Nossum
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=200801220119.42312.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.