[HP 6710b] Kworker constantly taking about 100% CPU
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | linux (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
I've this issue since the latest Ubuntu 11.10 version, all updates applied till today, and it's still there. Ubuntu 11.04 did not have this issue.
If I run top there is a Kworker constantly taking much CPU, I don't know how to research where this comes from.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] Bestand of map bestaat niet
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe4404000 irq 46'
Mixer name : 'Analog Devices AD1981'
Components : 'HDA:11d41981,
Controls : 11
Simple ctrls : 9
Date: Tue Nov 8 22:29:10 2011
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Hewlett-Packard HP Compaq 6710b (GB891ET#ABH)
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.60
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/15/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DDU Ver. F.15
dmi.board.name: 30C0
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.2E
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Compaq 6710b (GB891ET#ABH)
dmi.product.
dmi.sys.vendor: Hewlett-Packard
| KP Stolk (kp-stolk) wrote : | #1 |
| Changed in linux (Ubuntu): | |
| status: | New → Confirmed |
| Joseph Salisbury (jsalisbury) wrote : | #2 |
| Joseph Salisbury (jsalisbury) wrote : | #3 |
This could be an upstream issue. There is no single cause for kworker issues:
https:/
Getting additional information:
https:/
| KP Stolk (kp-stolk) wrote : | #4 |
@ Joseph Salisbury
Can you provide me the exaxt url where I can find the debs of the latest kernel?
Here I only find the linux image for amd64, while I have i686/i386 and this is the only v3.2-rcN listed:
http://
| Joseph Salisbury (jsalisbury) wrote : | #5 |
Thanks, I didn't realize the 32 bit kernels were not there yet. Can you test the latest 3.1 kernel instead:
| Gabriele N. Tornetta (phoenix1987) wrote : | #6 |
On my machine this issue is strongly correlated with failure of the wifi connection. When kworker goes nuts the wifi automatically stops working and "sudo service networking restart" is practically no use.
| KP Stolk (kp-stolk) wrote : | #7 |
I investigated the kworker problem a bit further, it seemse this kworker is only active and taking high CPU when I first boot my pc.
If I close my laptop so it goes on standby and resume it, the kworker is gone!
I will try the latest 3.1 kernel now and post back the results.
| KP Stolk (kp-stolk) wrote : | #8 |
Nope. I now have kernel 3.1.0-030100-
After standby the kworker is gone.
@ Joseph Salisbury, how can I investigate this further?
| Watschu (watschu) wrote : | #9 |
I had the same problem, occured yesterday after i standby and lasted till 10 minutes ago.
It is gone after i closed my Thinkpad T61 -> standby. When i tried to resume it, there was just a black screen with a cursor blinking left at the top. So i made a cold poweroff -> no problem with the kworker anymore.
Even after restarting or standby there is no problem.
I hope it will stay good.
| KP Stolk (kp-stolk) wrote : | #10 |
I just tried that too now. I did a cold poweroff also, but it's still returning in my case.
Very annoying. Can't trace where this kworker comes from...
| KP Stolk (kp-stolk) wrote : | #11 |
I now tried kernel 3.2.0-999-generic #201111160432 but the problem is still there...
Facing the same issue, I have added in /etc/modprobe.
options drm_kms_helper poll=N
After a reboot it was running again without any issue!
| KP Stolk (kp-stolk) wrote : | #13 |
At my PC there is no local.conf file in /etc/modprobe.d/. There are some other files but mostly blacklist*.conf files.
I searched my PC with 'locate' but there is no 'local.conf' at all..
I tried to add the file with the same text in it:
options drm_kms_helper poll=N
and rebooted. But it does not fix the kworker problem for me...
Suspending and resuming the machine only temporarily solves the issue for me. After a minute or so, my screen was freezing for a second every few seconds again.
I am using a Thinkpad T61, Ubuntu 11.10 x86_64, 3.0.0-13-generic
I can confirm that disabling networking(not just the wireless radio) stops the freezing.
I have always been using wireless, but have just noticed that the networking lights next to my eth0 port are both constantly on and ubuntu doesn't detect anything when I plug in plugging into a wired connection and doesn't connect to the internet. I am
$ sudo lshw -C network
*-network
description: Ethernet interface
product: 82566MM Gigabit Network Connection
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eth0
version: 03
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
resources: irq:45 memory:
*-network
description: Wireless interface
product: PRO/Wireless 4965 AG or AGN [Kedron] Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 61
width: 64 bits
clock: 33MHz
resources: irq:48 memory:
I am using a Thinkpad T61, Ubuntu 11.10 x86_64, 3.0.0-13-generic
| KP Stolk (kp-stolk) wrote : | #16 |
I've a HP 6710b which has a 'PRO/Wireless 3945ABG [Golan] Network Connection' wireless connection.
As long as I don't reboot or shutdown the problem does not come back, however the last week I had 2 dead locks, don't know if this has something to do with the wireless...
| KP Stolk (kp-stolk) wrote : | #17 |
I just tried V3.2-rc2 (http://
I shut down my laptop, pulled the battery out and let it sit for 5 minutes. I turned it back on and now there is now more lag. Very curious...
| Benjamin Bach (benjaoming) wrote : | #19 |
Confirmed. I suspended my computer after vacuuming my room and updating Ubuntu 11.10 (don't remember the order, but there were no kernel updates involved). After that, the kworker/* processes started occurring. They halt and block keyboard and mouse input at random intervals (like every 10 seconds). It's not a freeze, I think it's the kernel interrupt scheduler ignoring stuff such as mouse/keyboard/
/etc/init.
Disabling the NetworkManager works, all kworker processes disappear.
"/etc/init.
"dhclient eth0" does not work (the eth0 interface seems absolutely dead)
I restarted my computer and the problem persisted.
Then I did "ifconfig eth0 down" and it went away. And doing "ifconfig eth0 up" brings the kworker madness back.
Therefore I this problem is related to the ethernet module. I'm also running T61 like #14 but it's not 64 bit, it's i386. My ethernet is: 00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
| Benjamin Bach (benjaoming) wrote : | #20 |
As mentioned, once I do "ifconfig eth0 down", the problems stop. Once I do "ifconfig eth0 up", they start again.
powertop reports between:
99.2 ms/s 0.0 kWork e1000_watchdog_task
and
393.2 ms/s 0.1 kWork e1000_watchdog_task
While the network interface is completely idle (well, it doesn't work)!
The curious thing is that it used to work but it has broken recently in Ubuntu 11.10.
Btw, please see #779753 - a probably related bug.
| Kari Julkunen (kari-julkunen) wrote : | #21 |
In my desktop PC with Ubuntu 11.10 64bit kernel 3.0.0-14, there was the same kworker problem. It was consuming a lot of CPU power every now and then and thus freezing mouse cursor + keyboard. I just disabled the wireless networking because the PC is anyway wired to the router and guess what, the kworker just stopped wasting my CPU time! :) The 1 min load average dropped from 0.06 to 0.00 while just surfing on the internet without that weird kworker process.
I'm using NetworkManager if that's important somehow. The WLAN card is a TP-Link TL-WN951N.
| ITec (itec) wrote : | #22 |
On Ubuntu 12.04alpha1 Linux version 3.2.0-10-generic there is the problem with kworker, too.
I have got HP Compaq 6005 Pro machines (same vendor as KP Stolk's machines), but it happens on different (non HP) hardware, too.
"/etc/init.
The problem is described in:
http://
I do:
dd if=/dev/zero of=/tmp/zero1.tmp bs=1024 count=13000000
... two kworker threads start using up nearly 100% CPU from the time the memory cache gets filled up, shown as "cached" in top:
top - 18:20:57 up 2:44, 2 users, load average: 1.33, 0.50, 0.42
Tasks: 110 total, 3 running, 107 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0%us, 49.8%sy, 0.0%ni, 50.2%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 1791092k total, 1723636k used, 67456k free, 8k buffers
Swap: 0k total, 0k used, 0k free, 1564360k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4160 root 20 0 0 0 0 R 47 0.0 0:06.81 kworker/0:1
4217 root 20 0 0 0 0 R 47 0.0 0:06.12 kworker/1:0
4216 root 20 0 11500 632 516 D 5 0.0 0:38.42 dd
3281 root 20 0 17220 1240 904 R 0 0.1 0:11.11 top
4079 root 20 0 0 0 0 S 0 0.0 0:00.43 kworker/1:2
4093 root 20 0 0 0 0 S 0 0.0 0:00.21 kworker/0:0
1 root 20 0 24172 2016 1100 S 0 0.1 0:00.46 init
Are there any solutions known right now?
| ITec (itec) wrote : | #23 |
Affected are the following kernels on 12.04alpha1:
3.2.0-10-generic
3.2.0-8-generic
3.2.0-2-generic
Not affected is:
3.0.0-13-generic
It looks clearly like a kernel problem.
Does anybody know, how to fix this?
Is there any fix for the issue??
Please help..
Regards,
Subhojit Dutta
Operations Manager
Office : +91-80-40096244 | Mobile : +91-9741308685 | email: <email address hidden>
OnMobile Global Ltd. #165/5,Krishnaraju layout, 1st Main, J. P. Nagar Phase 7, Bangalore – 560076 (Karnataka)
www.onmobile.com
-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of ITec
Sent: 27 January 2012 21:33
To: Subhojit Dutta
Subject: [Bug 887793] Re: Kworker constantly taking about 100% CPU
Affected are the following kernels on 12.04alpha1:
3.2.0-10-generic
3.2.0-8-generic
3.2.0-2-generic
Not affected is:
3.0.0-13-generic
It looks clearly like a kernel problem.
Does anybody know, how to fix this?
--
You received this bug notification because you are subscribed to the bug report.
https:/
Title:
Kworker constantly taking about 100% CPU
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
I've this issue since the latest Ubuntu 11.10 version, all updates
applied till today, and it's still there. Ubuntu 11.04 did not have
this issue.
If I run top there is a Kworker constantly taking much CPU, I don't
know how to research where this comes from.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-
ProcVersionSi
Uname: Linux 3.0.0-12-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesI
USER PID ACCESS COMMAND
/dev/
CRDA: Error: [Errno 2] Bestand of map bestaat niet
Card0.
Card hw:0 'Intel'/'HDA Intel at 0xe4404000 irq 46'
Mixer name : 'Analog Devices AD1981'
Components : 'HDA:11d41981,
Controls : 11
Simple ctrls : 9
Date: Tue Nov 8 22:29:10 2011
HibernationDe
InstallationM
MachineType: Hewlett-Packard HP Compaq 6710b (GB891ET#ABH)
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcKernelCmd
RelatedPackag
linux-
linux-
linux-firmware 1.60
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
...
I belive I have found a fix for this ! This worked perfectly for me.
Reboot your system with the new kernel.
Open shell and become root.
Type #echo N> /sys/module/
Note that this will only be sustained till system reboot. After reboot the value will revert back to poll=Y
For a sustained effect: #echo "options drm_kms_helper poll=N"
Hope this will help your woes. Enjoy! Please post any problems you may experience.
| KP Stolk (kp-stolk) wrote : | #26 |
I have kernel version 3.2.0-030200rc2
But no effect, kworker still taking 80% or more. only thing that works is still setting laptop in standby and resume -> kworker gone.
Or do I need another kernel version?
Geting this on a 2011 Dell Lattitude, Ubuntu 11.10, always and only when the power cord has been unplugged and then plugged back in again. Once it's started happening, I can turn the kworkers on by plugging the cord in, and turn the big off by unplugging the cord. I've tried with several recent kernels including the realtime ones, and the same behaviour results.
uname -a
Linux charles-nst 3.0.12-rt30 #1 SMP PREEMPT RT Wed Dec 14 09:57:01 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux
...And again with the latest Ubuntu kernel,
charles-nst:~> uname -a
Linux charles-nst 3.0.0-16-generic #29-Ubuntu SMP Tue Feb 14 12:48:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Open shell and become root.
Type
#echo N> /sys/module/
This should drastically reduce the system load and put your system back to normal.
Note that this will only be sustained till system reboot. After reboot the value will revert back to poll=Y
For a sustained effect:
#echo "options drm_kms_helper poll=N"
Regards,
Subhojit Dutta
-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of <email address hidden>
Sent: 14 March 2012 16:57
To: Subhojit Dutta
Subject: [Bug 887793] Re: Kworker constantly taking about 100% CPU
Geting this on a 2011 Dell Lattitude, Ubuntu 11.10, always and only when the power cord has been unplugged and then plugged back in again.
Once it's started happening, I can turn the kworkers on by plugging the cord in, and turn the big off by unplugging the cord. I've tried with several recent kernels including the realtime ones, and the same behaviour results.
uname -a
Linux charles-nst 3.0.12-rt30 #1 SMP PREEMPT RT Wed Dec 14 09:57:01 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are subscribed to the bug report.
https:/
Title:
Kworker constantly taking about 100% CPU
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
I've this issue since the latest Ubuntu 11.10 version, all updates
applied till today, and it's still there. Ubuntu 11.04 did not have
this issue.
If I run top there is a Kworker constantly taking much CPU, I don't
know how to research where this comes from.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-
ProcVersionSi
Uname: Linux 3.0.0-12-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesI
USER PID ACCESS COMMAND
/dev/
CRDA: Error: [Errno 2] Bestand of map bestaat niet
Card0.
Card hw:0 'Intel'/'HDA Intel at 0xe4404000 irq 46'
Mixer name : 'Analog Devices AD1981'
Components : 'HDA:11d41981,
Controls : 11
Simple ctrls : 9
Date: Tue Nov 8 22:29:10 2011
HibernationDe
InstallationM
MachineType: Hewlett-Packard HP Compaq 6710b (GB891ET#ABH)
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcKernelCmd
sudo -i
echo N> /sys/module/
echo "options drm_kms_helper poll=N"
Works fine for me, even on Ubuntu 12.04.
KP Stolk, thank you for reporting this bug and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://
If it remains an issue, could you run the following command from a Terminal (Applications-
apport-collect -p linux <replace-
Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/
Thanks in advance.
| ITec (itec) wrote : apport information | #32 |
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
Package: linux (not installed)
ProcEnviron:
TERM=xterm
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RfKill: Error: [Errno 2] No such file or directory
Tags: precise
Uname: Linux 3.2.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 09/28/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G6 v01.16
dmi.board.
dmi.board.name: 3047h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Compaq 6005 Pro MT PC
dmi.sys.vendor: Hewlett-Packard
| ITec (itec) wrote : AcpiTables.txt | #33 |
apport information
| ITec (itec) wrote : AlsaDevices.txt | #34 |
apport information
| ITec (itec) wrote : BootDmesg.txt | #35 |
apport information
| ITec (itec) wrote : Card0.Codecs.codec.0.txt | #36 |
apport information
| ITec (itec) wrote : CurrentDmesg.txt | #37 |
apport information
| ITec (itec) wrote : Lspci.txt | #38 |
apport information
| ITec (itec) wrote : Lsusb.txt | #39 |
apport information
| ITec (itec) wrote : PciMultimedia.txt | #40 |
apport information
| Changed in linux (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Confirmed |
| Changed in linux (Ubuntu): | |
| status: | Confirmed → Incomplete |
| tags: | added: kernel-request-3.2.0-20.33 |
| tags: | added: bot-stop-nagging |
| tags: | removed: kernel-request-3.2.0-20.33 |
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Confirmed |
| Changed in linux (Ubuntu): | |
| status: | Confirmed → Triaged |
| Changed in linux: | |
| importance: | Undecided → Unknown |
| status: | New → Unknown |
| Changed in linux: | |
| importance: | Unknown → Medium |
| status: | Unknown → Confirmed |
|
84 comments hidden
Loading more comments
|
view all 164 comments |
@Scott: Yep, more or less, in the sense that I put acpi=noirq as boot parameter editing temporarily the boot parameters at startup. I think if this acpi=noirq solution works, should works as one-time try and can't be dependent on the number of reboots, but if you say that it works for you that's good. I don't know what really is/involves "acpi=noirq" and I also don't know what is/involves the disabling of gpe13.
So the questions can be these:
- it's better acpi=noirq or disabling gpe13?
- what does they mean/involve?
My Chronos is the NP700Z7C-S01IT model with Ubuntu 12.10 (no dual boot, w8 was removed) with all updates.
| Rdst (raf-k) wrote : | #126 |
Just to note that this bug still exist in ubuntu 12.10.
I have xoredgers kernel and cinnamon installed.
Problem is showing after connecting power adapter.
Dispersals once, i will unplug it.
Solution from previous comments worked just fine.
sudo su -
echo N> /sys/module/
echo "options drm_kms_helper poll=N"
Linux 3.7.0-7-generic #15-Ubuntu SMP Sat Dec 15 16:34:21 UTC 2012 i686 i686 i686 GNU/Linux
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
| jcdutton (james-superbug) wrote : | #127 |
I have a Samsung Series 7.
Same symptoms
echo "disable" > /sys/firmware/
cures the 75% CPU#0 in top due to kworker interrupts.
How do we find out what gpe13 is?
I have the same problems with a ASUS K53S running UBUNTU 11.10 but the GPE that consume CPU is the 06. The workaround proposed by Mauro works for me.
| jcdutton (james-superbug) wrote : | #129 |
I have raised a kernel bug relating to this.
I wish to find out what gpe13 actally is, so we can write a proper ACPI handler for it (the notify bit), and keep it quiet that way.
https:/
| cheater (cheater00) wrote : | #130 |
macbook pro retina 15" here, Ubuntu 12.10 following cberner's tutorial. I had to turn off interrupt 16, rather than the numbers suggested above. kworker disappeared immediately from top; before that it was anywhere between 99 and 104% at all times. the fan wouldn't shut up, now the laptop is quiet.
| Loris Zinsou (the-lz-himself) wrote : | #131 |
Asus N43SL, this bug only shows up while running Wine for me.
kworker eatin 65% of one core.
How do I find what to turn off ? I really need ACPI since I use Bumblebee to run game on the nvidia graphics card.
Loris, if you stop wine the kworker consume 65% of cpu.
To see the irq that consume cpu run the following sentence.
grep . -r /sys/firmware/
| Carlo Capocasa (carlotheman) wrote : | #133 |
Thank you! What a relief.
echo "disable" > /sys/firmware/
works like a charm, and
grep enabled /sys/firmware/
is a great way to find the offending interrupt.
Also, if you get a permission denied error upon using sudo, do this:
sudo -s
echo "disable" > /sys/firmware/
That works.
| Carlo Capocasa (carlotheman) wrote : | #134 |
Also, I did a more detailed summary of my attempts to fix this problem and solution instructions from here in a blog post. I hope it helps someone.
| Changed in linux (Ubuntu): | |
| status: | Triaged → Confirmed |
This problem only showed up in the latest kernel: vmlinuz-
I've switched back to 3.2.0-37 and it works fine.
| James Burke (jburke) wrote : | #136 |
I have a ubuntu file server that is also experiencing this bug.
uname -a
Linux spartan 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Server is running on ESXi 5.1, 8 CPU's, 10 GB memory
This locks up the who server and I need to reboot to fix.
traces from the syslog:
Mar 6 14:59:45 spartan kernel: [373442.140153] INFO: task kworker/3:1:16763 blocked for more than 120 seconds.
Mar 6 14:59:45 spartan kernel: [373442.140293] "echo 0 > /proc/sys/
Mar 6 14:59:45 spartan kernel: [373442.140413] kworker/3:1 D 0000000000000003 0 16763 2 0x00000000
Mar 6 14:59:45 spartan kernel: [373442.140419] ffff88009f71db90 0000000000000046 0000000000000000 ffffffff81c87360
Mar 6 14:59:45 spartan kernel: [373442.140425] ffff88009f71dfd8 ffff88009f71dfd8 ffff88009f71dfd8 00000000000137c0
Mar 6 14:59:45 spartan kernel: [373442.140430] ffff8802ab9dae00 ffff8800a8a94500 ffff88009f71dbc0 7fffffffffffffff
Mar 6 14:59:45 spartan kernel: [373442.140434] Call Trace:
Mar 6 14:59:45 spartan kernel: [373442.140537] [<ffffffff8165b
Mar 6 14:59:45 spartan kernel: [373442.140541] [<ffffffff8165b
Mar 6 14:59:45 spartan kernel: [373442.140595] [<ffffffff8101b
Mar 6 14:59:45 spartan kernel: [373442.140599] [<ffffffff8101b
Mar 6 14:59:45 spartan kernel: [373442.140604] [<ffffffff81091
Mar 6 14:59:45 spartan kernel: [373442.140608] [<ffffffff8165b
Mar 6 14:59:45 spartan kernel: [373442.140653] [<ffffffff81060
Mar 6 14:59:45 spartan kernel: [373442.140657] [<ffffffff8165b
Mar 6 14:59:45 spartan kernel: [373442.140662] [<ffffffff8108b
Mar 6 14:59:45 spartan kernel: [373442.140667] [<ffffffff81086
Mar 6 14:59:45 spartan kernel: [373442.140671] [<ffffffff81084
Mar 6 14:59:45 spartan kernel: [373442.140675] [<ffffffff81086
Mar 6 14:59:45 spartan kernel: [373442.140679] [<ffffffff81086
Mar 6 14:59:45 spartan kernel: [373442.140682] [<ffffffff81086
Mar 6 14:59:45 spartan kernel: [373442.140686] [<ffffffff81086
Mar 6 14:59:45 spartan kernel: [373442.140689] [<ffffffff81086
Mar 6 14:59:45 spartan kernel: [373442.140693] [<ffffffff8108b
Mar 6 14:59:45 spartan kernel: [373442.140748] [<ffffffff81667
Mar 6 14:59:45 spartan kernel: [373442.140752] [<ffffffff8108b
Mar 6 14:59:45 spartan kernel: [373442.140755] [<ffffffff81667
Mar 6 15:01:45 spartan kernel: [373562.140109] INFO: task kworker/3:1:16763 blocked for more than 120 seconds.
Mar 6 15:01:45 spartan kernel: [373562...
| Changed in linux (Ubuntu): | |
| status: | Confirmed → New |
| LeeHach (lee-hachadoorian) wrote : | #137 |
Same problem on Lenovo Y560p.
grep enabled /sys/firmware/
indicates problem is gpe17 and gpe18.
echo disable > /sys/firmware/
echo disable > /sys/firmware/
Disabling gpe18 works and alleviates some of the CPU load. Disabling gpe17 alleviates the remainder of the CPU load *but* CPU load jumps back up in less than a minute (often within 5 seconds). grep enabled /sys/firmware/
Adding the above commands to /etc/rc.local doesn't seem to work, or maybe it does but only temporarily.
I know this thread goes back to 2011, but this problem only manifested a month or two ago. Not sure what update triggered it (assuming it was some update).
Running Linux Mint 13 with kernel 3.2.0-23-generic.
| devsk (funtoos) wrote : | #138 |
For me, this bug happened after I updated the BIOS on my Samsung Series 7 17.3" laptop. I had bought it last year and never updated the BIOS. I went from P02 to P06 I think.
People who got their laptops with latest BIOS obviously had the bug all along.
This is a classic case of Samsung screwing their Linux customers while adding support for latest Windows operating system.
Disabling gpe13 in my case helps.
| Launchpad Janitor (janitor) wrote : | #139 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Vladimir Scherbaev (zemik) wrote : | #140 |
I have this issue on 13.04
| Loris Zinsou (the-lz-himself) wrote : | #141 |
Raring, linux 3.8, the bug is still present.
| Andrea Dec (andreadec) wrote : | #142 |
I am experiencing the same bug on my Samsung RC-530-S07 laptop running Xubuntu 12.10 64bit. It seems the problem began when I replaced the HDD with a OCZ Vertex 4 SSD and replaced the optical drive with the HDD. I also enabled the "SATA GEN3 mode" in the BIOS.
The workaround provided some posts before (disable GPE13) works for me too
The bug related to this one in the kernel bug tracking system id this: https:/
| tags: | added: quantal |
| webmind (webmind) wrote : | #143 |
I had this problem while running maverick on a 3.5 kernel. Then having the following in my /etc/rc.local fixed it
echo N > /sys/module/
now upgraded to raring and the problem is back, this time a
echo disable > /sys/firmware/
as suggested on http://
seems to work.
I'm running ubuntu 13.04 with kernel 3.8.0-22-generic (64bit) on a thinkpad x200s (intel videocard).
it mainly appears on boot or when starting processes which take up a lot like firefox, even when those processes are idle. the mouse-pointer becomes sluggish/frozen and 1-5 kworker processes seem to hog the cpu, but when looking at their stack all you see is something like:
[<ffffffff81078
[<ffffffff8107d
[<ffffffff816d3
[<fffffffffffff
| webmind (webmind) wrote : | #144 |
it seems to be at-least partly related to the intel driver, I now get following again on busy kworker processes:
cat /proc/228/stack
[<ffffffff8106a
[<ffffffffa00e6
[<ffffffffa00e6
[<ffffffffa00e6
[<ffffffffa00e7
[<ffffffffa00a0
[<ffffffffa00b2
[<ffffffff81076
[<ffffffff81077
[<ffffffff8107d
[<ffffffff816d3
[<fffffffffffff
However, /sys/module/
It really makes the system completely unusable at random intervals for what seems to be random amounts of time.
| Revery (glajchs) wrote : | #145 |
Ty to cheater00 for the tip about the macbook. I'm using my work's macbook pro retina 10.1, running Linux Mint 14 (ubuntu 12.10 based). For me the problematic interrupt was 16 as well (gpe16). In being thorough, I found that gpe17 had twice the amount of interrupts that 16 did (though 16 was the one hogging the CPU). I've disabled them both and my wireless seems to be working better now, but who knows how long that will last. The wireless being slow or cutting out was the main reason that I've been researching possible causes. I'm using the broadcom-
| Mauro (mascia-mauro) wrote : | #146 |
@Revery, nop please. With a retina macbook I would leave Mountain Lion installed :)
Anyway, this is an old (I've found something similar referred to 2010 or before) problem that must be fixed!! Gurus, you have to work hard on that!
| tags: | added: raring |
| tags: | added: needs-full-computer-model needs-upstream-testing |
KP Stolk, this bug report is being closed due to your last comment https:/
| Vladimir Scherbaev (zemik) wrote : | #148 |
Maybe mark this bug as new?
| jeremy-list (quick-dudley) wrote : | #149 |
I'm having almost the same issue on a new install of raring ringtail, except everything locks up when system memory usage reaches 62% instead of 100%.
| Hans Deragon (deragon) wrote : | #150 |
I have this bug coming back and bite me again.
Obviously, kworker hogging CPU can be caused by multiple causes. Since this bug report is generic in nature, maybe it should be converted as a wish for a mean to trace easily the kworker thread. We need something like 'top', to tell us why kworker is working so hard.
Any expert out there on kworker? Your opinion on this issue would be much appreciated. This issue is a serious blow for the user's experience.
| Hans Deragon (deragon) wrote : | #151 |
Without doing anything to my machine, the problem went away. However, on my Lenovo T61P where it occurred, when kworker took a lot of CPU, threeof the 11 thermometers the laptop has was red. For two of them, when the laptop is working hard, they are normally red so that was usual. But the 3rd one, I never saw it red, thus suggesting that kworker had something to do with a piece of hardware which usually does not work as hard. Now that kworker is quiet, this thermometer is back into blue, normal temperature.
Don't ask me what the thermometers are for, they are only labeled numerically.
| Launchpad Janitor (janitor) wrote : | #152 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Kim Tucker (ktucker) wrote : | #153 |
Problem persists after upgrading to Saucy from Raring ( macbook pro retina 10.1) - CPU1 always close to 100% (gnome-
| Hans Deragon (deragon) wrote : | #154 |
I just realized that the text of my comment (#151) is really bad; I cannot figure out why it came out so bad; I do not write has bad. Therefore, I am resubmitting my comment with better wording, for the sake of clarity.
----
2013-09-17
Without doing anything to my Lenovo T61P (Ubuntu 12.04), the problem went away by itself. However, when it occurred, kworker took a lot of CPU and 3 of the 11 thermometers the laptop has were red. Normally, when the laptop is working hard, there are two that are red. Thus until kworker kicked in, I never saw the 3rd one being red before, suggesting that kworker had something to do with a piece of hardware which usually does not work as hard. Now that kworker is quiet, this thermometer is back being blue, i.e. back to a normal temperature.
Don't ask me what the thermometers are for, they are only labeled numerically.
----
2013-10-25
Since, kworker has not bugged me, but since it comes and goes, I am sure I will suffer from this again.
| Martin G Miller (mgmiller) wrote : | #155 |
Had this problem with a 12.04 that had been upgraded from 11.04 to 11.10 to 12.04 32 bit. I finally reinstalled new 64 bit 12.04 and the problem persisted. For me it was gpe11 that had a value of 4200. I followed the instructions from post #114 above, modified for gpe11 instead of 13 and it seems to have resolved the problem for me. I did have to run all the commands with sudo instead of starting with the tilde (~).
| Mathias-bavay (mathias-bavay) wrote : | #156 |
Same bug, starting today with the updated 3.10.1-
| Mathias-bavay (mathias-bavay) wrote : | #157 |
Sorry, attaching a file did not work...
Here is my dmesg:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.10.1-
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] Disabled fast string operations
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000
[ 0.000000] BIOS-e820: [mem 0x000000000009f
[ 0.000000] BIOS-e820: [mem 0x00000000000d8
[ 0.000000] BIOS-e820: [mem 0x0000000000100
[ 0.000000] BIOS-e820: [mem 0x000000005f690
[ 0.000000] BIOS-e820: [mem 0x000000005f69d
[ 0.000000] BIOS-e820: [mem 0x000000005f700
[ 0.000000] BIOS-e820: [mem 0x00000000e0000
[ 0.000000] BIOS-e820: [mem 0x00000000f0008
[ 0.000000] BIOS-e820: [mem 0x00000000fed20
[ 0.000000] BIOS-e820: [mem 0x00000000ff000
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.3 present.
[ 0.000000] DMI: Sony Corporation VGN-TX750P, BIOS R0051V1 12/01/2005
[ 0.000000] e820: update [mem 0x00000000-
[ 0.000000] e820: remove [mem 0x000a0000-
[ 0.000000] e820: last_pfn = 0x5f690 max_arch_pfn = 0x1000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-CFFFF write-protect
[ 0.000000] D0000-E3FFF uncachable
[ 0.000000] E4000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask FC0000000 write-back
[ 0.000000] 1 base 040000000 mask FE0000000 write-back
[ 0.000000] 2 base 05F700000 mask FFFF00000 uncachable
[ 0.000000] 3 base 05F800000 mask FFF800000 uncachable
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] PAT not supported by CPU.
[ 0.000000] original variable MTRRs
[ 0.000000] reg 0, base: 0GB, range: 1GB, type WB
[ 0.000000] reg 1, base: 1GB, range: 512MB, type WB
[ 0.000000] reg 2, base: 1527MB, range: 1MB, type UC
[ 0.000000] reg 3, base: 1528MB, range: 8MB, type UC
[ 0.000000] total RAM covered: 1527M
[ 0.000000] Found optimal setting for mtrr clean up
[ 0.000000] gran_size: 64K chunk_size: 16M num_reg: 4 lose cover RAM: 0G
[ ...
| Wojciech Wnętrzak (ringwraith) wrote : | #158 |
I confirm that this bug still persists on Ubuntu 13.10.
Installed on ThinkPad T61.
Disabling network workorounds the problem.
| Eckhard Wiederhold (ecky) wrote : | #159 |
I confirm as well that this problem persists on Ubuntu 13.10, or more precisely :
[ 0.000000] Linux version 3.11.0-13-generic (buildd@roseapple) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) ) #20-Ubuntu SMP Wed Oct 23 07:38:26
UTC 2013 (Ubuntu 3.11.0-
It appears once in a while - about every second day. Last time it appeared it was today when I plugged in my external Hard-Drive and logged in afterwards to my allready opened session.
If this happens, there is not much to do about, just reboot and the problem goes away then but I'm quite reluctant to do it. Tried to kill it or relaunch the x-server as I thought this process is part of it. But that seems not to be the case. What are kworkers ? What are they good for? Do they manage the CPU? This might be the case as I see 3 times 8 of them enumerated from 0 to 7 and four prefixed with u this would correspond the 8 virtual cores and the 4 real ones present on my CPU.
Might it be possible that there is a race-condition on one of the cores that puts it to an endless-loop (instead of just letting it die or blocking it for example)?
| Mathias-bavay (mathias-bavay) wrote : | #160 |
The problem also appears with kernel 3.8.0-33-generic on my laptop (see my other comments above). I am now 100% positive this is linked to the wifi (ipw2200 card). I loose all network connectivity, thunderbird gets crazy (high cpu usage) and I see one or two kworker processes. Turning wifi off does not solve the problem (even waiting several minutes), but when turning it back, it solves the problem right away (the kworkers disapear and thunderbird starts behaving again).
| Vladimir Scherbaev (zemik) wrote : | #161 |
I have installed Elementary OS based on Ubuntu 12.04. Today I install last avaliable kernel 3.11.0-13-generic (linux-
| no longer affects: | linux (Ubuntu) |
| summary: |
- Kworker constantly taking about 100% CPU + [HP 6710b] Kworker constantly taking about 100% CPU |
| Launchpad Janitor (janitor) wrote : | #162 |
Status changed to 'Confirmed' because the bug affects multiple users.
Hans Deragon, please do not reopen this report as this does not affect the original reporter anymore as per his previous comments. If you have a bug in Ubuntu, and so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux
For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https:/
Ubuntu Kernel Team: https:/
Ubuntu Community: https:/
When opening up the new report, please feel free to subscribe me to it.
Thank you for your understanding.
| Changed in linux (Ubuntu): | |
| status: | New → Confirmed |
| affects: | linux (Suse) → linux (Ubuntu) |
| Changed in linux (Ubuntu): | |
| status: | New → Invalid |
| no longer affects: | linux (Ubuntu) |
| Launchpad Janitor (janitor) wrote : | #164 |
Status changed to 'Confirmed' because the bug affects multiple users.
| affects: | linux (Arch Linux) → linux (Ubuntu) |
| Changed in linux (Ubuntu): | |
| status: | New → Invalid |
| no longer affects: | linux |
Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https:/
If this bug is fixed by the mainline kernel, please add the following tag 'kernel-
If the mainline kernel does not fix this bug, please add the tag: 'kernel-
Thanks in advance.