kworker amok
 

wtf is kworker and why is it running 9 processes on my box now?

368 ? S 0:00 [kworker/0:1]
816 ? S 0:00 [kworker/u:6]
817 ? S 0:00 [kworker/u:7]
2098 ? S 0:00 [kworker/0:6]
2538 ? S 0:00 [kworker/0:0]
3006 ? S 0:00 [kworker/0:5]
3177 ? S 0:00 [kworker/0:4]
3571 ? S 0:00 [kworker/0:3]
3695 ? S 0:00 [kworker/0:2]

Linux dtd 2.6.38.7-smp #1 SMP Sat May 21 20:29:12 CDT 2011 i686 AMD Athlon(tm) Processor LE-1640 AuthenticAMD GNU/Linux

Oh my God! The same thing is happening to me! I'm killing them all as we speak! We're being overrun!

EDIT: Actually... I think this just might be normal.

kworker is a Kernel process.

You can read the Kernel documentation for workqueue.txt if you need more info.

dTd,

What ver. of Slack are you running & which desktop?


disturbed1,

What kind of "Kernel process" is kworker, i.e. what does it do?
Where can OP find workqueue.txt?

/usr/src/linux/Documentation/workqueue.txt

Killing this process is stupidity... actually I think you can't kill it -

pgrep kworker
10
12
417
627
672
5592
5650

Notice, Linux (or in general Unix) is NOT windows... it has a lot of low negligible memory consuming processes, and shows them all unlike windows which hides 90% of the system processes.

I don't have a problem with them, and haven't tried to kill any of them :P I was just wondering... thanks for the explanation.

I had same the problem kworker going mad. I have been messing around with BIOS setting (overclocking), then Kworker started using 100% on core 0. Cleared the BIOS by taking out battery and replacing it, this stopped the Kworker problem for me.

Did not solve that problem!
 

... hew, I'm feeling sorry about it, but I red your explanations and didn't manage to solve that trouble on my computer! :'(
Still presently, some kworker/0:x processes are using a lot of my CPU power, around 70/80%, and I can't understand the way to solve it...

May someone please explain it to me?

http://askubuntu.com/questions/33640...ng-so-much-cpu

you might find some clues here - your problem could well be related to the kernel you're running.