Daniel, can you please attach output of `grep . /sys/class/dmi/id/*`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799235
Title:
kworker process starts at 85% of cpu and stays there
To manage
PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
20684 root 20 0 0 0 0 I 59.9 0.0 2:52.66
kworker/0:0-kacpi_notify
I'm also having this on a Dell G7 laptop ( Intel(R) Core(TM) i7-8750H
CPU @ 2.20GHz ) with kernel
This is also found on a Cannon Lake Intel SDP with Xeon E-2176G running
v5.4-rc1 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799235
Title:
kworker process starts at 85% of cpu and stays
** Tags added: ubuntu-certified
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799235
Title:
kworker process starts at 85% of cpu and stays there
To manage notifications about this bug go to:
** 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/1799235
Title:
kworker process starts at 85% of cpu and stays there
To manage notifications about this bug go to:
Hi again: So, I tried both with restored default bios settings and
default factory setting. The kworker process is still going at over
85%. I can turn it off w/ echo "disable" >
/sys/firmware/acpi/interrupts/gpe6F in both cases.
One odd thing I noticed. With the default settings, I have two
Hmm, I think the main bios change is that I have safe mode turned off
(at least in part because of that unsigned module). I'll see what I can
do the next time I restart the system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On your system, this is in kernel message:
[ 0.104005] ACPI: GPE 0x6F active on init
I just tested Precision 3630 Tower in our lab, no such message, and I
don't see the issue here.
/sys/firmware/acpi/interrupts/gpe6F stays at 0 all the time.
Can you try "restore default settings" in BIOS?
**
Thanks Kai-Heng.
Unfortunately, my system wouldn't boot with v4.13. I installed the
following kernel-related files:
linux-headers-4.13.16-041316_4.13.16-041316.201711240901_all.deb
linux-headers-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64.deb
Can you try v4.13? There's a new commit introduced in v4.14:
commit ecc1165b8b743fd1503b9c799ae3a9933b89877b
Author: Rafael J. Wysocki
Date: Thu Aug 10 00:30:09 2017 +0200
ACPICA: Dispatch active GPEs at init time
In some cases GPEs are already active when they are enabled by
I've updated the BIOS for my system. It did not solve the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799235
Title:
kworker process starts at 85% of cpu and stays there
To manage
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799235
Title:
kworker process starts at 85% of cpu and stays there
To manage
There's a BIOS update for this system, it might solve the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799235
Title:
kworker process starts at 85% of cpu and stays there
To manage
I should add that I issued the following last night:
echo "enable" > /sys/firmware/acpi/interrupts/gpe6F
And then tried to shut down my system. After 8 minutes, the system had
not shut down, so I did so manually. Either the interrupts from the bug
are preventing the shutdown or this is a
I've now tested with 4.19-rc8. The kworker process remains at about 65%
continuously. Not quite sure how to mark this as confirmed, but will
try.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The issue began after a fresh system install on a new computer.
Admittedly, the first system I installed was Qubes, with Fedora (24 I
believe). When I decided Qubes wasn't adequate for my needs, I wiped
the system (reformatted using gparted) and installed the latest Ubuntu
(as of a month ago).
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19
17 matches
Mail list logo
