Re: Regression: 20 ACPI interrupts per second on EEEPC 4G
Alexey Starikovskiy wrote: Alan Jenkins wrote: On latest git, powertop shows 20 ACPI interrupts per second. Previously, this was closer to 1 per second. See attached output (a vs b, a is from 2.6.29-rc8). This is from a pretty sparse KDE desktop. Normally I run gnome-power-manager, but I killed it to make sure that wasn't causing any problems. gpe18: 60975 enabled gpe_all: 60975 sci: 60975 which I presume means lots of EC interrupts. [0.134068] ACPI: EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62 This patch looks to be a suspect: 34ff4dbce54c83b1234d39b7ad9e548a75dd, Please check if reversing it helps No, I still get 20 ACPI interrupts per second. I tried without powertop, just in case that was provoking it, but it still happens: a...@alan-eeepc:/sys/firmware/acpi/interrupts$ cat sci; sleep 5; cat sci 2583 2680 Thanks Alan -- To unsubscribe from this list: send the line unsubscribe kernel-testers in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Regression: 20 ACPI interrupts per second on EEEPC 4G
On latest git, powertop shows 20 ACPI interrupts per second. Previously, this was closer to 1 per second. See attached output (a vs b, a is from 2.6.29-rc8). This is from a pretty sparse KDE desktop. Normally I run gnome-power-manager, but I killed it to make sure that wasn't causing any problems. a...@alan-eeepc:/sys/firmware/acpi/interrupts$ grep -v invalid * error: 0 ff_gbl_lock: 0enabled ff_pwr_btn: 0 enabled ff_rt_clk: 0 disabled gpe03: 0 disabled gpe04: 0 disabled gpe05: 0 disabled gpe09: 0 disabled gpe0B: 0 disabled gpe0C: 0 disabled gpe0D: 0 disabled gpe0E: 0 disabled gpe18: 60975 enabled gpe_all: 60975 sci: 60975 which I presume means lots of EC interrupts. [0.134068] ACPI: EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62 Any ideas? Thanks Alan PowerTOP 1.11 (C) 2007, 2008 Intel Corporation Collecting data for 100 seconds CnAvg residency C0 (cpu running)( 0.0%) polling 0.0ms ( 0.0%) C10.1ms ( 0.0%) C20.0ms ( 0.0%) C3 93.5ms (100.0%) P-states (frequencies) Wakeups-from-idle per second : 10.7 interval: 100.0s no ACPI power usage estimate available Top causes for wakeups: 17.0% ( 2.0) interrupt : ehci_hcd:usb1, uhci_hcd:usb2 15.1% ( 1.8) interrupt : extra timer interrupt 12.7% ( 1.5) udevd : ehci_work (ehci_watchdog) 8.6% ( 1.0) Xorg : schedule_hrtimeout_range (hrtimer_wakeup) 8.5% ( 1.0) kwrapper : do_nanosleep (hrtimer_wakeup) 8.5% ( 1.0) kwin : schedule_hrtimeout_range (hrtimer_wakeup) 8.5% ( 1.0) USB device 1-5 : UB6225 (ENE) 4.2% ( 0.5) hald-addon-stor : schedule_hrtimeout_range (hrtimer_wakeup) 2.4% ( 0.3) interrupt : ata_piix 2.1% ( 0.2)NetworkManager : atl2_open (atl2_watchdog) 1.8% ( 0.2) interrupt : acpi 1.7% ( 0.2) kded : schedule_hrtimeout_range (hrtimer_wakeup) 1.7% ( 0.2) kernel core : page_writeback_init (wb_timer_fn) 1.6% ( 0.2) init : schedule_hrtimeout_range (hrtimer_wakeup) 1.0% ( 0.1) kernel module : neigh_table_init_no_netlink (neigh_periodic_timer) 1.0% ( 0.1) kernel core : neigh_table_init_no_netlink (neigh_periodic_timer) 0.8% ( 0.1) ssh-agent : schedule_hrtimeout_range (hrtimer_wakeup) 0.8% ( 0.1) klauncher : schedule_hrtimeout_range (hrtimer_wakeup) 0.3% ( 0.0) kernel module : acpi_thermal_check (acpi_thermal_run) 0.3% ( 0.0) scsi_scan_2 : blk_add_timer (blk_rq_timed_out_timer) 0.3% ( 0.0) kernel core : blk_add_timer (blk_rq_timed_out_timer) 0.3% ( 0.0) hald : schedule_hrtimeout_range (hrtimer_wakeup) 0.2% ( 0.0) kdesktop : schedule_hrtimeout_range (hrtimer_wakeup) 0.2% ( 0.0) kernel core : queue_delayed_work (delayed_work_timer_fn) 0.2% ( 0.0)kicker : schedule_hrtimeout_range (hrtimer_wakeup) 0.1% ( 0.0) interrupt : PS/2 keyboard/mouse/touchpad 0.1% ( 0.0) cron : do_nanosleep (hrtimer_wakeup) 0.1% ( 0.0) kernel core : addrconf_verify (addrconf_verify) 0.1% ( 0.0) kernel core : inet_initpeers (peer_check_expire) 0.1% ( 0.0) rsyslogd : futex_wait (hrtimer_wakeup) A USB device is active 100.0% of the time: USB device 1-5 : UB6225 (ENE) Suggestion: Enable USB autosuspend by pressing the U key or adding usbcore.autosuspend=1 to the kernel command line in the grub config 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 frequently for background VM activity Suggestion: Disable 'hal' from polling your cdrom with: hal-disable-polling --device /dev/cdrom 'hal' is the component that auto-opens a window if you plug in a CD but disables SATA power saving from kicking in. Recent USB suspend statistics Active Device name 100.0% USB device 1-5 : UB6225 (ENE) 0.0% USB device usb5 : UHCI Host Controller (Linux 2.6.29-rc8eeepc uhci_hcd) 0.0% USB device usb4 : UHCI Host Controller (Linux 2.6.29-rc8eeepc uhci_hcd) 0.0% USB device usb3 : UHCI Host Controller (Linux 2.6.29-rc8eeepc uhci_hcd) 0.0% USB device usb2 : UHCI Host Controller (Linux 2.6.29-rc8eeepc uhci_hcd) 100.0% USB device usb1 : EHCI Host Controller (Linux 2.6.29-rc8eeepc ehci_hcd) PowerTOP 1.11 (C) 2007, 2008 Intel Corporation Collecting data for 100 seconds CnAvg residency C0 (cpu running)( 0.3%) polling 0.0ms ( 0.0%) C10.0ms ( 0.0%) C21.1ms ( 0.0%) C3 42.1ms (99.7%) P-states (frequencies) Wakeups-from-idle per second : 23.9 interval: 100.0s no ACPI power usage estimate available Top causes for wakeups: 64.2% ( 19.7) interrupt
Re: Regression: 20 ACPI interrupts per second on EEEPC 4G
Hi Alan, This patch looks to be a suspect: 34ff4dbce54c83b1234d39b7ad9e548a75dd, Please check if reversing it helps Regards, Alex. Alan Jenkins wrote: On latest git, powertop shows 20 ACPI interrupts per second. Previously, this was closer to 1 per second. See attached output (a vs b, a is from 2.6.29-rc8). This is from a pretty sparse KDE desktop. Normally I run gnome-power-manager, but I killed it to make sure that wasn't causing any problems. a...@alan-eeepc:/sys/firmware/acpi/interrupts$ grep -v invalid * error: 0 ff_gbl_lock: 0enabled ff_pwr_btn: 0 enabled ff_rt_clk: 0 disabled gpe03: 0 disabled gpe04: 0 disabled gpe05: 0 disabled gpe09: 0 disabled gpe0B: 0 disabled gpe0C: 0 disabled gpe0D: 0 disabled gpe0E: 0 disabled gpe18: 60975 enabled gpe_all: 60975 sci: 60975 which I presume means lots of EC interrupts. [0.134068] ACPI: EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62 Any ideas? Thanks Alan -- To unsubscribe from this list: send the line unsubscribe kernel-testers in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
