kworker uses 100% CPU when nfs-kernel-server is active

Bug #1318116 reported by Gordon
56
This bug affects 10 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

I have a clean install of 14.04 on an i7-860 with 16GB RAM.

I'm using NFS to share a home directory. The volume is ~2TB, formatted JFS, and it has a single client.

I recently noticed that I had a [kworker] process using 100% CPU:

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 9253 root 20 0 0 0 0 R 99.9 0.0 0:30.17 [kworker/3:1]

Rebooting didn't help.

After some troubleshooting I found that it went away immediately when I stopped the nfs-kernel-server daemon. When I start it, it comes back after a minute or two, still using 99-100% CPU. The load goes away when the client is turned off and the NFS server is restarted, but it comes back as soon as it reconnects.

The only line in /etc/exports is:
/home 192.168.1.0/24(rw,sync,no_root_squash)

version_signature:
Ubuntu 3.13.0-24.47-generic 3.13.9

# dpkg -l nfs-kernel-server
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-==================================
ii nfs-kernel-ser 1:1.2.8-6ubu amd64 support for NFS kernel server

Description: Ubuntu 14.04 LTS
Release: 14.04

I don't think this is related to my hardware but I can provide lspci output if necessary.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: username 4414 F.... pulseaudio
                      username 4778 F.... pulseaudio
 /dev/snd/controlC0: username 4414 F.... pulseaudio
                      username 4778 F.... pulseaudio
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=de6e2d52-86c9-4867-8d37-31964953e1e6
InstallationDate: Installed on 2014-05-01 (9 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P55A-UD4P
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/hostname-newestroot ro quiet splash
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
RfKill:

Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 10/16/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: P55A-UD4P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P55A-UD4P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1318116

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: trusty
Revision history for this message
Gordon (kmputerguy) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Gordon (kmputerguy) wrote : BootDmesg.txt

apport information

Revision history for this message
Gordon (kmputerguy) wrote : CRDA.txt

apport information

Revision history for this message
Gordon (kmputerguy) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Gordon (kmputerguy) wrote : Lspci.txt

apport information

Revision history for this message
Gordon (kmputerguy) wrote : Lsusb.txt

apport information

Revision history for this message
Gordon (kmputerguy) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Gordon (kmputerguy) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Gordon (kmputerguy) wrote : ProcModules.txt

apport information

Revision history for this message
Gordon (kmputerguy) wrote : UdevDb.txt

apport information

Revision history for this message
Gordon (kmputerguy) wrote : UdevLog.txt

apport information

Revision history for this message
Gordon (kmputerguy) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
resnostyle (bwp-pearson) wrote :

In my particular scenario I am using Ubuntu 14.04. With NFS mount and AUFS. And am seeing the same result of kworker0:1 going to and staying 100%. I have tried adjusting the acpi settings to off, but this has not helped.

Rebooting the server itself does not help. I'll post any needed logs to help fixing it.

Turning off nfs-server has helped.

-----

I am running kernel 3.13.0-19-generic.

Revision history for this message
xeno678g (e3-hvag-jl) wrote :

Same here.

14.04 kernel 3.13.0-24-generic and nfs-kernel-server kworker results in 1 core on 100% (i3 CPU);

remove 3.13.0-24-generic (downgrade to 3.11.0-19-generic from 13.10) - OR - stop/remove nfs-kernel-server fixes it.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc5-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-da-key needs-bisect
Revision history for this message
Gordon (kmputerguy) wrote :

Linux hostname 3.15.0-031500rc5-generic #201405091635 SMP Fri May 9 20:36:31 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Don't see the process any more. Looks like the 3.15 kernel fixes it.

tags: added: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Gordon (kmputerguy)
description: updated
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you also test the latest v3.13 stable kernel to see if the fix in 3.15 already migrated down through stable? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.2-trusty/

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Gordon (kmputerguy) wrote :

Problem exists in the 3.13 kernel you linked me to:
Linux hostname 3.13.11-03131102-generic #201405081435 SMP Thu May 8 18:36:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.