Number of processes exploded after upgrade to 4.13.0-32-generic

Bug #1747597 reported by Marc Pignat
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

After an update from 4.10.0-40-generic to 4.13.0-32-generic (ubuntu 16.04 + hwe kernel), the number of process when doing IO on my machine has exploded.

Before the update, maximum number of process : 284
After the update, doing a simple rsync to an external disk : 771

The system is now unstable and crashes. The processes are hundreds of "kworker".

Please let me know if there is something more needed.
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Feb 6 09:04 seq
 crw-rw---- 1 root audio 116, 33 Feb 6 09:04 timer
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-32-generic.
AplayDevices: aplay: device_list:268: no soundcards found...
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: arecord: device_list:268: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
PciMultimedia:

ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=ef4f1569-51cf-478d-868c-78a3b7f04a2c ro
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic N/A
 linux-firmware 1.157.15
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial
Uname: Linux 4.13.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip kvm libvirtd lpadmin lxd plugdev sambashare sudo sudo-no-log video
_MarkForUpload: True
dmi.bios.date: 05/17/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.70
dmi.board.name: Z97 Extreme6
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd05/17/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Marc Pignat (swid) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1747597

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: zesty
Revision history for this message
Marc Pignat (swid) wrote :

apport-collect 1747597 fails with "Bad bot, go away!"

tags: added: xenial
removed: zesty
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Marc Pignat (swid) wrote : CRDA.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Marc Pignat (swid) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Marc Pignat (swid) wrote : JournalErrors.txt

apport information

Revision history for this message
Marc Pignat (swid) wrote : Lspci.txt

apport information

Revision history for this message
Marc Pignat (swid) wrote : Lsusb.txt

apport information

Revision history for this message
Marc Pignat (swid) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Marc Pignat (swid) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Marc Pignat (swid) wrote : ProcEnviron.txt

apport information

Revision history for this message
Marc Pignat (swid) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Marc Pignat (swid) wrote : ProcModules.txt

apport information

Revision history for this message
Marc Pignat (swid) wrote : UdevDb.txt

apport information

Revision history for this message
Marc Pignat (swid) wrote : WifiSyslog.txt

apport information

affects: linux (Ubuntu) → linux-meta-hwe (Ubuntu)
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 v4.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'.

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/v4.15

Changed in linux-meta-hwe (Ubuntu):
importance: Undecided → Medium
affects: linux-meta-hwe (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-bisect
Revision history for this message
Marc Pignat (swid) wrote :

I installed the 4.15.0-041500-generic kernel, and the machine failed to reboot, unfortunately this is a remote machine.

Next try in 6-8 hours.

Revision history for this message
Marc Pignat (swid) wrote :

using the 4.15.0-041500-generic kernel, the total process count was very high (473) just after the boot, perhaps something to do with the raid array resync.

Now doing backup to the external disk, process count seems normal (287).

I still think there is a problem with that process count since older kernel never showed more than 286 thread in the last year.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Marc Pignat (swid) wrote :

As requested, I added the tag kernel-bug-exists-upstream and changed the status to confirmed

Revision history for this message
Marc Pignat (swid) wrote :

4.16.0-041600rc2-generic is also affected.

Revision history for this message
Marc Pignat (swid) wrote :

I'm trying to bisect the bug, but I have some problem doing it.

I have cloned the branch hwe of git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git, using "git clone -b hwe git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git"

Then I have built the kernel (just to test the build process) using "fakeroot debian/rules binary-headers binary-generic binary-perarch" and this worked as expected.

Then I started bisecting using "git bisect start Ubuntu-hwe-4.13.0-32.35_16.04.1 Ubuntu-hwe-4.10.0-40.44_16.04.1", which seems to work as expected:

Bisecting: a merge base must be tested
[c470abd4fde40ea6a0846a2beab642a578c0b8cd] Linux 4.10

The build command ("fakeroot debian/rules binary-headers binary-generic binary-perarch") fails with : "/usr/bin/fakeroot: line 175: debian/rules: No such file or directory"

There is no more debian directory, I don't understand how this git repository is working...

Revision history for this message
Marc Pignat (swid) wrote :

I've got 4 computers running ubuntu.
2 computers affected, and 2 computers unaffected. The two affected computer are using btrfs.

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.