Luis Menina wrote: > Hi list, > > I've been wanting to ask that for a long time now... Since I've tried > powertop for the first time last year, I've seen that my destop machine > has an incredibliy high number of wakeups, even idle. More than 100 > wakeups per second on a freshly booted system, with barely a GNOME > desktop and a terminal to display powertop results. It seems that either > the USB subsystem, or the ethernet one, or both, are responsible for > that. So, could someone here please give me some tips on how to improve > current situation, if possible. And if it's not possible, could you help > me to identify the bugs that cause this comportment ? > > I'm running Mandriva Linux 2009.0 with a 2.6.27.7 kernel. > > Thanks in advance, > -- > Luis > > ================ > uname -a output: > ================ > Linux donald 2.6.27.7-desktop-1mnb #1 SMP Thu Dec 11 16:45:35 EST 2008 > i686 AMD Athlon(tm) XP 3000+ GNU/Linux > > =================== > powertop -d output: > =================== > [r...@donald ~]# LC_ALL=C powertop -d > PowerTOP 1.10 (C) 2007, 2008 Intel Corporation > > Collecting data for 15 seconds > > > < Detailed C-state information is not available.> > P-states (frequencies) > Wakeups-from-idle per second : 123.3 interval: 15.0s > no ACPI power usage estimate available > Top causes for wakeups: > 90.0% (101.2) <interrupt> : ehci_hcd:usb1, eth0 > 2.1% ( 2.3) <interrupt> : pata_amd > 1.8% ( 2.0) <kernel core> : clocksource_register > (clocksource_watchdog) > 1.6% ( 1.8) gnome-terminal : schedule_timeout (process_timeout) > 0.9% ( 1.0) ifplugd : schedule_timeout (process_timeout) > 0.9% ( 1.0) ntpd : do_setitimer (it_real_fn) > 0.5% ( 0.5) pulseaudio : schedule_timeout (process_timeout) > 0.2% ( 0.3) gnome-panel : schedule_timeout (process_timeout) > 0.2% ( 0.3) <kernel core> : neigh_table_init_no_netlink > (neigh_periodic_timer) > 0.2% ( 0.3) <kernel module> : neigh_table_init_no_netlink > (neigh_periodic_timer) > 0.2% ( 0.2) init : schedule_timeout (process_timeout) > 0.2% ( 0.2) gnome-settings- : schedule_timeout (process_timeout) > 0.2% ( 0.2) <kernel core> : page_writeback_init (wb_timer_fn) > 0.2% ( 0.2) ifplugd : __netdev_watchdog_up (dev_watchdog) > 0.1% ( 0.1) mount : start_this_handle (commit_timeout) > 0.1% ( 0.1) ntpdate : do_adjtimex (sync_cmos_clock) > 0.1% ( 0.1) preload : schedule_timeout (process_timeout) > 0.1% ( 0.1) pam_timestamp_c : schedule_timeout (process_timeout) > 0.1% ( 0.1) <interrupt> : PS/2 keyboard/mouse/touchpad > 0.1% ( 0.1) X : do_setitimer (it_real_fn) > 0.1% ( 0.1) X : schedule_timeout (process_timeout) > 0.1% ( 0.1) syslogd : do_setitimer (it_real_fn) > 0.1% ( 0.1) hald : schedule_timeout (process_timeout) > 0.1% ( 0.1) gnome-power-man : schedule_timeout (process_timeout) > > Suggestion: increase the VM dirty writeback time from 4.99 to 15 seconds > with: > echo 1500 > /proc/sys/vm/dirty_writeback_centisecs > This wakes the disk up less frequenty for background VM activity > > Suggestion: Enable the ondemand cpu speed governor for all processors via: > echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor > > > Recent USB suspend statistics > Active Device name > 0.0% USB device usb3 : OHCI Host Controller (Linux > 2.6.27.7-desktop-1mnb ohci_hcd) > 0.0% USB device usb2 : OHCI Host Controller (Linux > 2.6.27.7-desktop-1mnb ohci_hcd) > 0.0% USB device usb1 : EHCI Host Controller (Linux > 2.6.27.7-desktop-1mnb ehci_hcd) > > > ============= > lspci output: > ============= > [r...@donald ~]# lspci > 00:00.0 Host bridge: nVidia Corporation nForce2 IGP2 (rev c1) > 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1) > 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1) > 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1) > 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1) > 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1) > 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4) > 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) > 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) > 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) > 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) > 00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet > Controller (rev a1) > 00:05.0 Multimedia audio controller: nVidia Corporation nForce Audio > Processing Unit (rev a2) > 00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 > Audio Controler (MCP) (rev a1) > 00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) > 00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) > 00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire (IEEE > 1394) Controller (rev a3) > 00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1) > 01:0b.0 RAID bus controller: Promise Technology, Inc. PDC20376 (FastTrak > 376) (rev 02) > 03:00.0 VGA compatible controller: ATI Technologies Inc Radeon R350 > [Radeon 9800 Pro] > 03:00.1 Display controller: ATI Technologies Inc Radeon R350 [Radeon > 9800 Pro] (Secondary) > > _______________________________________________ > Power mailing list > [email protected] > http://www.bughost.org/mailman/listinfo/power > > I found changing the kernel; under timer frequency in the processor section, setting to 100 reduces wakeups. As well as choosing server(under the preempt section) lowers the wakups around 4 to 5 hundred. (+ -) Then going through and removing modules are not needed. Then if need be, go into the kernel and remove some timers(probably not a good idea though);
regards; Justin P. Mattock _______________________________________________ Power mailing list [email protected] http://www.bughost.org/mailman/listinfo/power
