Bug 1743 - kworker taking CPU
Summary: kworker taking CPU
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-11 03:46 CEST by Olivier FAURAX
Modified: 2011-09-03 22:44 CEST (History)
1 user (show)

See Also:
Source RPM: kernel-desktop586-latest-2.6.38.7-1.mga1
CVE:
Status comment:


Attachments

Description Olivier FAURAX 2011-06-11 03:46:31 CEST
My computer has some little freezes and when I look at the processes using the gnome system monitor, I see that kworker/1:1 alternates between 10% and 80% of CPU usage.
The CPU consomation is by regular peak, every second or so.

I don't know what is the purpose of this process.

I see also rtkit-daemon taking CPU when kworker is high.
Comment 1 Olivier FAURAX 2011-06-11 15:08:33 CEST
Not better with kernel-linus

Source RPM: kernel => kernel-desktop586-latest-2.6.38.7-1.mga1

Comment 2 Olivier FAURAX 2011-06-11 15:23:26 CEST
Not that when kworker take the CPU, the keyboard is blocked every X sec when you type something.
The letter doesn't appear on the screen when you type something. You can even lose letters.
VERY ANNOYING.

Severity: normal => major

Comment 3 Olivier FAURAX 2011-06-11 16:14:35 CEST
I tested with the previous mandriva kernel, with no luck.

As mentioned in bug 1749, I have duplicated package.

I tried to see if it was HAL or udev, and I have :
$ rpm -qa | grep udev
system-config-printer-udev-1.3.1-4.mga1
libudev0-166-5.mga1
udev-166-5.mga1
libgudev1.0_0-166-5.mga1
udev-153-5mnb2

So perhaps the duplicated udev is the culprit, and this can also be the source of the bug 1742 (no ethernet).
Comment 4 Dick Gevers 2011-06-11 17:35:16 CEST
May we know some hardware specs of your box? Have you tried a ligher DM (xfce, lxde, icewm)? or other OS? LiveCD ? If yes does it not occur then or does it?

CC: (none) => dvgevers

Comment 5 Olivier FAURAX 2011-06-11 18:55:35 CEST
Same problem when booting on init 3, but not in init 1.

So I tested by removing the services one by one, and is is the network....

service network stop : no kworker eating CPU
service network start : kworker start by taking 100% CPU

As I also have ethernet not working (bug 1742), I tried to rmmod the e1000e module... and the problem has gone!

Workaround: rmmod e1000e (ethernet driver module)
Comment 6 Olivier FAURAX 2011-09-03 22:44:29 CEST
Fixed in kernel update.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.