Hi, powertop -d from my standard idle desktop. Firefox, Thunderbird and Pidgin are running in the background. It seems, the wlan card is pure evil :-O cu romal [root@helios ~]# powertop -d PowerTOP 1.7 (C) 2007 Intel Corporation Sammle Daten für 5 Sekunden Cn Avg residency (5s) C0 (Prozessor läuft) (10,7%) C1 0,0ms ( 0,0%) C2 3,9ms (83,6%) C3 5,3ms ( 5,8%) P-states (frequencies) 1,86 GHz 3,4% 1,60 GHz 0,0% 1060 MHz 0,4% 800 MHz 96,2% Wakeups-from-idle per second : 223,4 Keine ACPI Stromverbrauch-Schätzung verfügbar Top causes for wakeups: 28,7% ( 77,0) <interrupt> : ipw2200 15,7% ( 42,2) S06cpuspeed : queue_delayed_work_on (delayed_work_timer_fn) 5,4% ( 14,6) X : do_setitimer (it_real_fn) 5,1% ( 13,8) at-spi-registry : schedule_timeout (process_timeout) 4,5% ( 12,0) firefox-bin : futex_wait (hrtimer_wakeup) 4,2% ( 11,4) pcscd : schedule_timeout (process_timeout) 4,2% ( 11,2) <interrupt> : uhci_hcd:usb4, HDA Intel 3,7% ( 10,0) <kernel core> : ehci_work (ehci_watchdog) 3,7% ( 10,0) <kernel module> : sky2_probe (sky2_idle) 3,7% ( 10,0) /usr/bin/sealer : schedule_timeout (process_timeout) 3,3% ( 8,8) <interrupt> : libata 2,1% ( 5,6) hald-addon-acpi : schedule_timeout (process_timeout) 1,8% ( 4,8) thunderbird-bin : futex_wait (hrtimer_wakeup) 1,5% ( 4,0) <kernel module> : usb_hcd_poll_rh_status (rh_timer_func) 1,2% ( 3,2) fnfxd : do_nanosleep (hrtimer_wakeup) 1,1% ( 3,0) <interrupt> : eth1 1,0% ( 2,6) pcscd : do_nanosleep (hrtimer_wakeup) 1,0% ( 2,6) <kernel module> : ipw_up (delayed_work_timer_fn) 0,9% ( 2,4) gnome-terminal : schedule_timeout (process_timeout) 0,9% ( 2,4) <kernel core> : uhci_scan_schedule (uhci_fsbr_timeout) 0,8% ( 2,2) <interrupt> : uhci_hcd:usb2, ahci 0,7% ( 2,0) multiload-apple : schedule_timeout (process_timeout) 0,4% ( 1,0) <kernel core> : queue_delayed_work_on (delayed_work_timer_fn) 0,4% ( 1,0) dhcdbd : schedule_timeout (process_timeout) 0,4% ( 1,0) cpufreq-applet : schedule_timeout (process_timeout) 0,4% ( 1,0) automount : futex_wait (hrtimer_wakeup) 0,4% ( 1,0) nm-applet : schedule_timeout (process_timeout) 0,2% ( 0,6) <kernel module> : neigh_table_init_no_netlink (neigh_periodic_timer) 0,2% ( 0,6) gam_server : schedule_timeout (process_timeout) 0,2% ( 0,6) NetworkManager : schedule_timeout (process_timeout) 0,2% ( 0,6) gnome-vfs-daemo : schedule_timeout (process_timeout) 0,1% ( 0,4) X : schedule_timeout (process_timeout) 0,1% ( 0,4) pidgin : schedule_timeout (process_timeout) 0,1% ( 0,4) <kernel core> : sk_reset_timer (tcp_delack_timer) 0,1% ( 0,4) sensors-applet : schedule_timeout (process_timeout) 0,1% ( 0,4) <kernel core> : neigh_table_init_no_netlink (neigh_periodic_timer) 0,1% ( 0,4) hald-addon-stor : schedule_timeout (process_timeout) 0,1% ( 0,4) <kernel core> : neigh_update (neigh_timer_handler) 0,1% ( 0,2) <interrupt> : i8042 0,1% ( 0,2) pam_timestamp_c : schedule_timeout (process_timeout) 0,1% ( 0,2) init : schedule_timeout (process_timeout) 0,1% ( 0,2) ssh-agent : do_setitimer (it_real_fn) 0,1% ( 0,2) pidgin : sk_reset_timer (tcp_write_timer) 0,1% ( 0,2) gnome-power-man : schedule_timeout (process_timeout) 0,1% ( 0,2) S99smartd : __netdev_watchdog_up (dev_watchdog) 0,1% ( 0,2) mapping-daemon : schedule_timeout (process_timeout) 0,1% ( 0,2) <kernel core> : page_writeback_init (wb_timer_fn) 0,1% ( 0,2) cupsd : schedule_timeout (process_timeout) 0,1% ( 0,2) pcscd : uhci_scan_schedule (uhci_fsbr_timeout) 0,1% ( 0,2) gnome-panel : schedule_timeout (process_timeout) [root@helios ~]# Bill Nottingham schrieb: > Would you like your laptop battery to last longer? Would you like your > servers to use less electricity? We certainly would. So we're investigating > and fixing Fedora to use less juice. > > One of the biggest power problems is apps that wake up the CPU > unnecessarily. With the tickless kernel for x86 (and soon x86_64), > every time this happens it's a chance for power savings lost. > > HOW YOU CAN HELP > ---------------- > > We'd like to get as many reports of misbehaving apps as possible. > > 1) Install the 'powertop' package > > 2) Run it in a terminal window on a reasonably idle system with your > normal combination of apps. (If you run it when you're actively > compiling a kernel, watching a movie, or doing other CPU-intensive > things, the results aren't as useful.) > > 3) Note the results. If you'd like to capture them for safe-keeping > later, you can use the (Fedora-specific) '-d' option to dump them > to stdout, rather than pasting from the running app. > > 4) Report the results. You can add reports here, on #fedora-devel, > or to the upstream powertop community at power@xxxxxxxxxxx or > #powertop on irc.oftc.net. > > *** Please use a service such as http://pastebin.ca/ rather than > pasting powertop reports directly to an IRC channel. *** > > If you've got a specific app you know is misbehaving, please > file a bug with the details, and set it to block the 'wakeup' > bug in Fedora bugzilla. (bug number 204948.) > > Thanks for your assistance and help. > > Bill > -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
