Red Hat Bugzilla – Bug 1031273
kworker Task over 50% after some time
Last modified: 2013-12-27 04:08:07 EST
Description of problem:
The kworker task uses constant 50% after some time. There are several different kworkers with different second numbers and 0 as first number. I use an Asus f201e with fedora gnome. The problem occurs after the last update of fedora. I had this bug before, but I fixed it with this https://www.blakerohde.com/blog/2012/05/fedora-16-17-kworker-high-cpu/
Version-Release number of selected component (if applicable):
Install fedora 19 on an asus f201e with second installed windows which uses half of the hard drive.
I have also tried to use pcie_ports=compat but it didn't work either
I have to correct myself, the numbers of the kworker are every time different in both, the first and the second number.
Hard to say if it is expected or not.
you could do the following (either before kworker threads go high in cpu usage
[better] or during the event itself [less ideal):
sudo perf record -a
Let it run for a minute or so (while the kworker threads are consuming CPU) and
then stop it.
sudo perf report --stdio > perf.txt
Upload 'perf.txt' to this case
Setting needinfo appropriately. see c#2
can you provide the info asked for in comment 2 please?
Please excuse me for not answering. I decided to move to debian, because it works more battery friendly then fedora even without the kworker task. if no one else is interested in this problem you can close here.
Ok, no worries. I'll close this for now. If someone else will see this issue they will open another BZ