2

What are Kworker and SignalSender and why are they utilizing so much CPU? The stats from Powertop gave these numbers. How can I optimize it?

Top causes for wakeups:
28.4% (420.4)   PS/2 keyboard/mouse/touchpad interrupt
14.8% (219.5)   [kernel scheduler] Load balancing tick
14.0% (206.8)   kworker/0:0
8.4% (124.9)   SignalSender
7.7% (114.5)   [Rescheduling interrupts] <kernel IPI>

Kernel:

Kernel version - Linux xyz-xx-xx-110-1100 2.6.38-11-generic #48-Ubuntu SMP 
Fri Jul 29 19:05:14 UTC 2011 i686 i686 i386 GNU/Linux

PowerTop Stats

Top causes for wakeups:
18.5% (203.6)   [kernel scheduler] Load balancing tick
18.5% (203.5)   kworker/0:0
16.1% (176.6)   [Rescheduling interrupts] <kernel IPI>
14.2% (156.2)   SignalSender
9.4% (103.5)   [uhci_hcd:usb5, eth1, i915] <interrupt>
8.6% ( 94.5)D  chromium-browse
4.4% ( 48.8)   compiz
3.8% ( 41.5)   alsa-sink
3.4% ( 37.7)   icecast
0.6% (  6.1)   Xorg
0.5% (  6.0)   nginx
0.5% (  5.1)   [Function call interrupts] <kernel IPI>
0.5% (  5.0)   syndaemon
0.4% (  4.1)   [ahci] <interrupt>
0.1% (  1.0)   [hda_intel] <interrupt>
Improve this question
2
  • Kworker is what controls the ACPI wakeup signals from the BIOS.
    – Rinzwind
    Aug 26, 2011 at 12:04
  • Kernel version - Linux xyz-xx-xx-110-1100 2.6.38-11-generic #48-Ubuntu SMP Fri Jul 29 19:05:14 UTC 2011 i686 i686 i386 GNU/Linux
    – user7044
    Aug 26, 2011 at 12:20

1 Answer 1

Reset to default
1

Seems to be related to Chromium and Google Chrome as per this issue. It seems to have been fixed in Chromium 14.0.817. Not sure when it will reach Google Chrome.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .