** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
Title:
kworker uses 70-90% of a CPU core (hyperthreaded)
To manage notifications about this bug go to:
https://bugs.launchp
Sorry for the belated response.
In this case, I think kernel parameter "acpi_mask_gpe=0x13" to disable
it is the only workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
Title:
kworke
I dont't believe my laptop has a free fall sensor, didn't ever hear of such a
thing. How do I check?
It does have ExpressCache though.
My vague hypothesis is that it has something to do with the ODD but i don't
understand enough of this for being able to verify any of this without
instructions.
Does this laptop have a free fall sensor?
Seems like gpe13 tries to notify your SATA controller something. Or
maybe it's related to the ExpressCache?
Scope (_GPE)
{
Method (_L13, 0, NotSerialized) // _Lxx: Level-Triggered GPE
{
If ((PFLV == FDTP))
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1087010/+attachment/5143923/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
Title
Can you attach acpidump?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
Title:
kworker uses 70-90% of a CPU core (hyperthreaded)
To manage notifications about this bug go to:
https://bugs.la
** Tags removed: kernel-bug-exists-upstream-4.17-rc4 needs-filing-upstream
** Tags added: kernel-bug-exists-upstream-4.17-rc6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
Title:
kworker use
I can confirm that the issue is present with 4.17-rc6 too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
Title:
kworker uses 70-90% of a CPU core (hyperthreaded)
To manage notifications abou
Ok I just saw it's a GPE issue. Can you try latest mainline kernel [1]?
There are several GPE/EC fixes.
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
`perf top` output on 4.15.0-20-generic
13,09% [kernel][k] acpi_os_read_port
11,81% [kernel][k] acpi_ns_search_one_scope
6,42% [kernel][k] acpi_os_write_port
4,62% [kernel][k] acpi_ut_track_stack_
Hi Mio,
Can you install linux-tools-generic and use `perf top` to see which
functions cause this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
Title:
kworker uses 70-90% of a CPU cor
here is the mailing list post https://marc.info/?l=linux-
acpi&m=152675757008502&w=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
Title:
kworker uses 70-90% of a CPU core (hyperthreaded)
T
sorry i continued posting with information i thought might be relevant or
helpful without reloading the page and did not see the new comments.
I did now send the report as requested. How do i know when it is available in
the archives?
--
You received this bug notification because you are a me
Mio, if you want an upstream developer to review your problem and submit
a fix patch, you *need* to file a *new* upstream report as previously
advised (not continue to post here on Launchpad). Otherwise your issue
may never be addressed.
** Tags removed: regression-potential
** Tags added: needs-f
I did some more research and found this kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=53071 which seems to descibe
exactly this issue. In that thread there is mentioned that a bios update might
fix the problem.
Thus I went hunting for an update for my model since the Software Update to
Mio, please don't change the Description. It is filled with old,
irrelevant, and speculative statements that confuse and hinder
developers resolving the problem.
Despite this, have you reported this upstream as noted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1087010/comments/73
?
**
** Description changed:
- I see high (70-90%) cpu usage from a kworker thread. Usually kworker/0:1 or
kworker/0:2.
- This does not always happen. On some boots all is fine but once it shows,
rebooting does not make it go away.
+ I see high cpu usage from a kworker thread. Usually kworker/0:1 or
Mio, the issue you are reporting is an upstream one. Could you please
report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO: Rafael J. Wysocki and Len Brown CC: linux-acpi)?
Please provide a direct URL to your po
** Description changed:
- I see high cpu usage from a kworker thread. Usually kworker/0:1 or
kworker/0:2. I tested various kernels from Ubuntu and mainline (3.5.0-x, 3.6.x,
3.7.0-rcx) and they all showed the same behavior. This does not always happen.
- I wasn't able to determine on which basis
Full computer model is Samsung Chronos 7 NP700Z7C-S02DE
** Tags removed: needs-full-computer-model
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
Title:
kworker uses 70-90% of a CPU core (hy
i tested the 4.17.0-rc4 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc4/ and can confirm that
this is still an issue there
4.17.0-rc5 would not boot
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.17.0-rc4
** Tags remo
the above apport was sent while gpe13 interrup was enabled and issue was
occurring (massive amount of interrupt, high cpu usage)
$ cat /sys/firmware/acpi/interrupts/gpe13
3913101 STS enabled unmasked
just in a few seconds
--
You received this bug notification because you are a member
the above apport was sent while gpe13 interrup was enabled and issue was
occurring (massive amount of interrupt, high cpu usage)
$ cat /sys/firmware/acpi/interrupts/gpe13
3913101 STS enabled unmasked
just in a few seconds
--
You received this bug notification because you are a member
the workaround was the same as described in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491467
echo "disable" > /sys/firmware/acpi/interrupts/gpe13
** Description changed:
I see high cpu usage from a kworker thread. Usually kworker/0:1 or
kworker/0:2. I tested various kernels from U
the above apport was sent from the current 18.04 release (with gpe13 interrupt
disabled).
I did a fresh install and noticed again this problem
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
apport information
** Tags added: apport-collected bionic
** Description changed:
I see high cpu usage from a kworker thread. Usually kworker/0:1 or
kworker/0:2. I tested various kernels from Ubuntu and mainline (3.5.0-x, 3.6.x,
3.7.0-rcx) and they all showed the same behavior. This does not
Pablo Almeida, making "Me too!" comments is just simply unhelpful. However, so
your hardware and problem may be tracked, could you please file a new report
with Ubuntu by executing the following in a terminal while booted into the
default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux
Just had this again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
Title:
kworker uses 70-90% of a CPU core (hyperthreaded)
To manage notifications about this bug go to:
https://bugs.launch
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
T
Vladimir Scherbaev, thank you for your comment. So your hardware and problem
may be tracked, could you please file a new report with Ubuntu 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 r
I have 12.04, but I try all availiable kernels from 12.10, 13.04, 13.10
and this bug affect me
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Mark Holtzhausen, please do not apport-collect to this bug as you are not the
original reporter. If you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu
Bug Control team, and Ubuntu Bug Squad would like you to please file a new
report by executing the following in a terminal while booted int
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mark 1883 F pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=c15da4c5-75e7-4590-ad12-5b994dd400bb
InstallationDate: Installed on 2013-11-23 (0
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
T
Mio, 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? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .
*** This bug is a duplicate of bug 887793 ***
https://bugs.launchpad.net/bugs/887793
Same here, on an Asus X53sc. Disabling gpe06 fixed the issue.
Thank you very much!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
*** This bug is a duplicate of bug 887793 ***
https://bugs.launchpad.net/bugs/887793
This bug also affects me, using Asus A53S Notebook. For me the problem
was in gpe06, thanks a ton for the workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
*** This bug is a duplicate of bug 887793 ***
https://bugs.launchpad.net/bugs/887793
Just did a little blog post on the subject, which sums up the fixes. I
hope it is useful.
http://carlocapocasa.com/crushing-the-kworker-uprising-or-how-to-fix-
your-linux-lenovo-ideapad-y560p/
--
You receiv
*** This bug is a duplicate of bug 887793 ***
https://bugs.launchpad.net/bugs/887793
Though the workaround works, this is a serious issue (definitely above
"Medium" importance and needs to be solved at the kernel level. WTH is
interrupt 13 anyway? Maybe it is invoking/reporting something impor
*** This bug is a duplicate of bug 887793 ***
https://bugs.launchpad.net/bugs/887793
** This bug has been marked a duplicate of bug 887793
Kworker constantly taking about 100% CPU
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 887793 ***
https://bugs.launchpad.net/bugs/887793
@Alexandre: great work man! thank you very much, your solution is really
appreciated.
I'm experiencing the same problem as exposed here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887793
(this bug
Sorry to budge in. Experiencing the exact same problem on my brand new
Samsung Chronos Series 7 using Arch Linux.
Just thought you might be interested in a dirty workaround that takes
CPU usage down (at the expense of some problem? dunno, still haven't
experienced any):
1 - Locate problematic GPE
why is this incomplete? should I add something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
Title:
kworker uses 70-90% of a CPU core (hyperthreaded)
To manage notifications about this bug
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087010
Title:
kw
** Description changed:
- I see high cpu usage from a kworker thread. Usually kworker/0:1 or
kworker/0:2. I tested various kernels from Ubuntu and mainline (3.5.0-x, 3.6.x,
3.7.0-rcx) and they all showed the same behaviour. This does not always happen.
+ I see high cpu usage from a kworker threa
45 matches
Mail list logo
