** Attachment removed: AcpiTables.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887793/+attachment/2940443/+files/AcpiTables.txt
** Attachment removed: BootDmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887793/+attachment/2940445/+files/BootDmesg.txt
**
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
I have installed Elementary OS based on Ubuntu 12.04. Today I install
last avaliable kernel 3.11.0-13-generic (linux-image-generic-lts-saucy)
and this is worked ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I confirm as well that this problem persists on Ubuntu 13.10, or more precisely
:
[0.00] 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-13.20-generic 3.11.6)
It appears
I confirm that this bug still persists on Ubuntu 13.10.
Installed on ThinkPad T61.
Disabling network workorounds the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker
Same bug, starting today with the updated 3.10.1-031001-generic kernel
on Ubuntu 13.04. I suspect my ipw2200 wifi to be the source of the
problem (the driver seems to be slowly falling behind, it is getting
quite unstable, I often have to turn the wifi off and back on in order
to get back
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
Problem persists after upgrading to Saucy from Raring ( macbook pro
retina 10.1) - CPU1 always close to 100% (gnome-system-monitor).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
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),
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
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
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
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%.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Maybe mark this bug as new?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To manage notifications about this bug go to:
** Tags added: needs-full-computer-model needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To manage notifications about
KP Stolk, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887793/comments/83
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line
** Tags added: raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To manage notifications about this bug go to:
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
@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!
--
You received this bug notification because you are a member
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
[8106a460] msleep+0x20/0x30
[a00e6120] intel_dp_aux_native_read_retry+0xd0/0x140 [i915]
[a00e6bfd] intel_dp_get_dpcd+0x1d/0x60 [i915]
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/drm_kms_helper/parameters/poll
now upgraded to raring and the problem is back, this time a
echo disable /sys/firmware/acpi/interrupts/gpe11
as suggested on
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To manage notifications about this bug go to:
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
Raring, linux 3.8, the bug is still present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
I have this issue on 13.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To manage notifications about this bug go to:
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
** Changed in: linux (Ubuntu)
Status: Confirmed = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To manage notifications about this
Same problem on Lenovo Y560p.
grep enabled /sys/firmware/acpi/interrupts/*
indicates problem is gpe17 and gpe18.
echo disable /sys/firmware/acpi/interrupts/gpe17
echo disable /sys/firmware/acpi/interrupts/gpe18
Disabling gpe18 works and alleviates some of the CPU load. Disabling
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.
This problem only showed up in the latest kernel:
vmlinuz-3.2.0-38-generic. kworker has a very high CPU load, typing is
nearly impossible and also my wired network no longer worked.
I've switched back to 3.2.0-37 and it works fine.
--
You received this bug notification because you are a member
** Changed in: linux (Ubuntu)
Status: Triaged = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To manage notifications about
Thank you! What a relief.
echo disable /sys/firmware/acpi/interrupts/gpeXX
works like a charm, and
grep enabled /sys/firmware/acpi/interrupts/*
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
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.
http://carlocapocasa.com/crushing-the-kworker-uprising-or-how-to-fix-
your-linux-lenovo-ideapad-y560p/
--
You received this bug notification
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/acpi/interrupts/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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://bugzilla.kernel.org/show_bug.cgi?id=53071
** Bug watch added: Linux Kernel Bug Tracker #53071
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.
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which 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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have a Samsung Series 7.
Same symptoms
echo disable /sys/firmware/acpi/interrupts/gpe13
cures the 75% CPU#0 in top due to kworker interrupts.
How do we find out what gpe13 is?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
@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
@Scott: I've tried the only one time acpi=noirq with no success on the same
laptop (if your Chronos is the 17 version). If is a matter of number of
reboots, I can re-try this but I am skeptical on the good success of this
operation. Are you sure the problem has disappeared or is just the case
@Mauro - Did you run sudo update-grub2 after you made the change to
/etc/default/grub? Did you include acpi=noirq inside the double
quotation marks, like so:
GRUB_CMDLINE_LINUX_DEFAULT=quiet splash acpi=noirq
The model of my Chronos 7 is: NP700Z7C-S02UK, and I'm using Ubuntu
12.10. I had
@Alex: the sudo -i / su thing it's pretty strange just because we are
using the same laptop and the same ubuntu 12.10... anyway it is not a
great issue to deal with. For other users is good to have mine or your
solution to get the same result.
offtopicIf I was a MBP retina owner I surely leave
@Mauro, I tried sudo -i (same as sudo su AFAIK) with no success. Just
add that line to rc.local and be done with it. My CPU temperature
indicator is showing 38C now (compared to 60s before). Stays in low 40s
most of the time. No fan heard. Battery life: 5.5-6 hours (verified) -
moderate use:
Lenovo y560p owner here. Same issue but the interrupt appears to be
gpe18. I also can't seem to disable it with jus sudo. Actually had to
become root to do it. The kworker thread seems to have disappeared.
Weird.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Setting acpi=noirq worked for me after a couple of reboots! I guess my
laptop was really hot and need time to cool down. Just to reiterate the
workaround:
1. Edit /etc/default/grub
2. Add acpi=noirq to the GRUB_CMDLINE_LINUX_DEFAULT line (so it's:
GRUB_CMDLINE_LINUX_DEFAULT=quiet splash
Hi Alex
I've forgot to add the sudo su command before everything and I've forgot to
write that you have first to verify that the one which is causing/catching (I
don't know what is really doing) a big number of interrupts, is effectively the
gpe13 .
Becoming root should allow you to execute
@Mauro, I tried sudo -i (same as sudo su AFAIK) with no success. Just
add that line to rc.local and be done with it. My CPU temperature
indicator is showing 38C now (compared to 60s before). Stays in low 40s
most of the time. No fan heard. Battery life: 5.5-6 hours (verified) -
moderate use:
I worked around this problem on Samsung Chronos 7 series in Ubuntu 12.10
by using acpi_os_name=Windows 2009. A dump of ACPI reveals special
code for Windows 2012, which I believe Linux is having trouble with.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Scott, i gonna try
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1087010/comments/4
@Sonal, tried but doesn't works for me... are you sure after 2 or 3 reboots it
is still working?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
this https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1087010/comments/4
has really worked for me!
Ok it's a workaround but I don't care, it can shutdown this crazy CPU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This stuff seems to work very well, so...
code
~ cp /sys/firmware/acpi/interrupts/gpe13 /pathtobackup
~ crontab -e
/code
Add this line, so it will be executed every startup/reboot:
code
@reboot echo disable /sys/firmware/acpi/interrupts/gpe13
/code
Save/exit. Then, to make it work also on
Thanks, Mauro and Scott. How do I write disable to gpe13 just to test
it. Permission denied even as sudo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about
Never mind. Though cannot execute that command once booted, it works
fine in /etc/rc.local - the system startup script. My instructions are a
little shorter:
sudo gedit /etc/rc.local
Put the following command there (anywhere):
echo disable
I performed a clean install of Ubuntu 12.10 on my Samsung Series 7
Chronos (NP700Z7C-S02UK). I have applied all updates, but kworker still
constantly uses 80% CPU. I cannot use Ubuntu on my laptop because of
this bug as the fan thrashes and the unit becomes quite hot.
Have attached screenshot of
That's my kernel log: http://pastebin.com/JyqvMfL8
I've tried also acpi_os_name=Microsoft Windows XP .. nothing to do :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker
Sorry for double-posting again but without an edit function I can't do
anything else...
I'm not an expert but these lines from kernel log would sound strange:
ACPI Warning: [...numbers] SystemIO conflicts with Region \PMIO 1
(20120320/utaddress-251)
ACPI: If an ACPI driver is available for this
Ok, so... if the issue came back from 2007 is more or less impossible to
be solved... that's sucks, also because I like this 17 Chronos.
I've also tried other boot options from here
https://wiki.ubuntu.com/DebuggingACPI#Trouble_Booting with no luck:
- CPU goes to 100% with pci=noacpi or with
Probably these pics can be useful:
- http://i45.tinypic.com/2qd1obl.png
- http://i47.tinypic.com/mj7jat.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking
Thanks, Mauro. Sorry, I did not try that samsung-specific package since
you mentioned it has no effect. The kworker returned in full might. I
have to do 3-4 reboots on average (followed by the power cord trick)
until the system starts properly - the payback for a few consecutive
days of normal
Googled high ACPI interrupts and the issue appears to be BIOS-related.
Definitely kernel-level, can be traced as far back, as 2007 - reappears
after fixes.
Below is the most recent incident (when the bug was assigned) - abandoned by
the developer for whatever reason.
Same problem here: first core is always between 75% and 85%; kworker is
taking this cpu under top.
With:
echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event
I got mainly acpi_os_execute_deferred rows.
Power cord trick doesn't work for me.
System details:
Ubuntu 12.10 with
Ok, I think I've figured it out.
After a couple (5-6) reboots/shutdown-stratup without the 80% cpu
problem, it seems to be related with the phc-intel kernel module
(https://launchpad.net/~createsc/+archive/3beol2).
I don't remember exactly why I added it (probably 'cause I was trying to
solve
Mauro, I'll try that package today on my NP700Z7C (17 Chronos) and let
you know. I noticed that the situation improved lately: normal CPU
usage for the past few days, however I did not install any packages,
just normal Ubuntu updates, and I believe it was no kernel updates:
running 3.5.0-21 now.
Hi Alex, same laptop here.
I think I've talked too early... in fact, after a 3 hours turned off, I
see the same issue again (80% cpu).
I've tried also the suspend mode and, after the wakeup, the first cpu goes to
100%.
Another restart had caused normal cpu behaviour.
About the keystrokes
I've made some other tests to see the correlation between things.
From what I can see:
- wake-up after suspend causes a 100% cpu usage (even if the system starts
without the 80% cpu issue)
- the 80% cpu issue happens randomly (after shutdown or reboot, doesn't matter)
- the powercord trick works
just took the time today to try
https://wiki.ubuntu.com/Kernel/MainlineBuilds to see if there is some
hope for the future and maybe to get a better picture of this bug ...
i tried so far
- 3.5.7 20121129
- 3.6.3 20121021
- 3.7.0rc2 20121020
conclusions:
3.5.7:
same old bug, kworker never
I tested pulling the power supply in and out after booting without any
grub parameters. I tested it about 30 times while watching top.
kworker jumped from 33% to 44% or so when I pulled it out. Never went
away completely.
Lenovo Y560p
Intel i7 with ATI video.
Broadcom NIC.
Kubuntu 12.10 -
It does not always happen. However 70% of the time the power cord trick
works. Abouth third of that on the first attempt, otherwise requires
several. If the kworker refuses to calm, reboot and repeat.
1. Start the System Monitor (easiest way to track the CPU usage - Core 1 in
this case)
2.
Looks like there are be two separate upstream bugs in here: one related
to XFS (https://bugzilla.kernel.org/show_bug.cgi?id=43013) and one
related to the e1000e module (apparently no upstream Bugzilla entry,
though https://bugzilla.kernel.org/show_bug.cgi?id=14737 might be
related). The latter bug
In my case it is related to ACPI and power/battery
reporting/consumption/whataever.
Has nothing to do with XFS or Ethernet controller.
Intermittent (80% of boots/restarts) and most of the time can be fixed by
removing and inserting the power cord.
--
You received this bug notification because
Yep, same for me. It's an ACPI problem but unlike Alex, removing the
power cord doesn't seem to fix it. I am running with acpi=noirq as a
workaround but this pretty much disables all power management for me.
Lenovo Y560p
Intel i7 with ATI video.
Broadcom NIC.
Kubuntu 12.10 - Kernel 3.5.0-19
--
can confirm alex's observation that removing/reinserting power will sometimes
put kworker to rest in my 12.10-all-defaults installation.
unfortunately its 1 out of 20 tries when this happens and therefore hardly
usefull for daily work.
@danyil: i dont see what this bug has to do with e1000 or
Another prowd Samsung 7 17 owner: NP700Z7C-S01UB (Best Buy model),
Running the latest 12.10 with all oficial updates: 3.5.0-18 kernel as of
now. Clean install.
Same symptoms, as tja's (see above), only neither pci=noacpi, nor acpi=noirq
fix it for me.
In fact, adding those to
same here:
- Samsung Series 7 NP700Z7C
- Ubuntu 12.10 fresh install
symptoms:
ACPI will do around 14k/s - 16,5k/s interrupts with battery, around 17k/s -
33k/s with power supply.
kworker will do around 80% cpu usage on one core, fan will run all the time,
battery runtime around 3h.
power stats
FYI acpi=noirq works. Also bumblebee works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To manage notifications about this bug go to:
Yep, it is.
Same on Samsung Serie 7 NP700Z5C-S04DE with Mint 13/14 or Ubuntu 12.10.
noacpi works but nvidia and bumblebee will not work with noacpi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Have tried all the suggested fixes so far, still no joy.
Also -- I see this has been assigned to a linux kernel upstream bug, but
that bug doesn't look very similar to this one, it's about creating
files over 8Gb in size, and no mention of kworkers? Could the assigner
please check and confim
(anyone know if this is still an issue in 12.10 by the way?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To manage notifications about this
I'm not sure if I'm having exactly the same issue but my kworker also makes CPU
really high. It started from upgrade to Kubuntu 12.10:
perf record is giving me:
Samples: 39K of event 'cycles', Event count (approx.): 27911930181, Thread:
kworker/0:2(558)
Sean Kibler is right! Removeing e1000 and e1000e modules works.
sudo modprobe -r e1000
sudo modprobe -r e1000e
Had the problem running:
Linux sittra 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
on a Lenovo T61p.
--
You received this bug
Strange thing is that since Ubuntu 12.04 I do not have that Kworker
actively working anymore.
Only the sound on my machine is weird, it regularly turns on and off the
sound mute button on my HP 6710b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I was able to alleviate this problem by removing e1000 and e1000e
modules.
sudo modprobe -r e1000
sudo modprobe -r e1000e
I tried adding them both to /etc/modprobe.d/local.conf as blacklisted
which seemed to apply to e1000 but e1000e was still loaded and caused
watchdog and kworker to beat the
is this the same bug as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717919 btw?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To
also reported by SuSe linux:
http://forums.suse.com/archive/index.php/t-873.html
** Also affects: linux (Suse)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
... and arch https://bbs.archlinux.org/viewtopic.php?id=120892
** Also affects: linux (Arch Linux)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Just to add, I am now running 12.04 on my dell lattitude and the bug is
still here. After a suspend, unplugging and plugging causes the kworks
to appear 90% of the time; unplugging it removes them; plugging in
restores them.
--
You received this bug notification because you are a member of
Also, modprobe -r e1000e does not fix for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking about 100% CPU
To manage notifications about this bug go to:
(Note sure if this is relevant, but I do a lot of audio work on my
machine, using JACK, Ardour2, Aucacity etc and several Ubuntu Studio
packages, I think someone mentioned ALSA in regard to the bug so maybe
this is connected?)
--
You received this bug notification because you are a member of
(please feel free to mail me if I can be of any help testing my machine
as part of the debugging, I'm not qualified to hack the kernel myself
though!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi korgie,
modprobe -r e1000e did the trick for my machine (Xubuntu 11.04 AMD64
Thinkad X61).
Thanks a lot!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly taking
I was having the same problem with recent Ubuntu Server 12.04 LTS
install, but providing acpi=off helped - I no longer see 100% kworker
thread.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
I noticed that my leds of ethernet are lit, although I don't have any
cable connected.
I disabled the ethernet module (modprobe -r e1000e) and kworker seems
calm. I was using mainline kernel (I think 3.0) without problem.
--
You received this bug notification because you are a member of Ubuntu
I'm affected by this bug. I recently upgraded my HP Mini 5103 laptop
from Ubuntu 11.10 to 12.04, and this problem appeared.
Similar to what ITec reports in comment #60, when using an older 3.0.0
kernel the problem is not there, but when booting into 3.2.0 it shows
up.
--
You received this bug
Wizzu, please execute the following via the Terminal and feel free to subscribe
me to it:
ubuntu-bug linux
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
Kworker constantly
I'm on a MacBook Air, purchased April 2012, 15 w standard specs --
1.7GHz Intel Core i5, 4GB of RAM, SSD hard drive, Intel graphics etc.
I am currently running 64-bit Ubuntu 12.04 off a USB disk, set up via my
Mac and diskutil and dd.
I plugged in two external hard drives (a 2TB I am backing up
Confirming this bug.
Sometimes when my system hangs I notice a trend that if I start a new
tab in Chrome, the processors jump to about 175% then increase until the
system hangs.
However, the system hang has happened without Chrome running, as well.
--
You received this bug notification because
Linux alfred 3.0.0-17-generic #30-Ubuntu SMP Thu Mar 8 20:45:39 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
I can confirm that the bug still exists. None of the above workarounds
help.
Examining kworker tracing via https://lkml.org/lkml/2011/3/31/68 ,
kworker seems to be borked with recurring
1 - 100 of 157 matches
Mail list logo
