kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #08199
[Bug 1213917] Re: kworker thread consuming 99.8 - 100% CPU after update
We can perform a kernel bisect to identify the commit that introduced
this regression. Do you happen to know the last kernel version that did
not exhibit this bug? If not, can you test the following kernels:
v3.11-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/
v3.11-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc2-saucy/
v3.11-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc3-saucy/
v3.11-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc4-saucy/
You don't have to test every kernel, just up until the kernel that first
has this bug.
Thanks in advance!
** Tags added: performing-bisect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1213917
Title:
kworker thread consuming 99.8 - 100% CPU after update
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
After updating today (hadn't updated for a while), my fan won't stop
and top is showing:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4 root 20 0 0 0 0 R 100,2 0,0 36:42.35 kworker/0:0
Edit: seems related to bug 1214071. I can reproduce with:
1) Start with a fresh reboot
2) suspend and resume
At this point after the successful resume, kworker thread starts
consuming 100% cpu and I can no longer suspend (bug 1214071).
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-2-generic 3.11.0-2.5
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: michael 2372 F.... pulseaudio
Date: Mon Aug 19 14:39:57 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=1efd421f-ac68-455b-b4d4-8912fa02494d
MachineType: ASUSTeK COMPUTER INC. X201EP
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic.efi.signed root=UUID=05643352-201b-43e8-976a-c1d40d591e80 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.11.0-2-generic N/A
linux-backports-modules-3.11.0-2-generic N/A
linux-firmware 1.113
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/04/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X201EP.209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X201EP
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX201EP.209:bd02/04/2013:svnASUSTeKCOMPUTERINC.:pnX201EP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX201EP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X201EP
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions
References