Public bug reported:
I read your following post (https://lkml.org/lkml/2019/5/29/309). Is
there any other configuration to disable or which patch is required to
resolve this issue?
I am facing a very similar issue with almost identical output from dmesg
call trace. This occurs with high frequency. It's fairly easy to
identify as kworker usage gets stuck very high when the problem occurs,
but this manifests into a bigger problem as docker containers cannot
start/restart and host requires a reboot to resolve. I have machines
running Ubuntu with various kernels (4.15.0-1031-azure through
4.15.0-1041-azure) and problem occurs randomly on every kernel version.
Using weave plugins vs docker overlay drivers for swarm scope, docker
overlay drivers seem to have the problem more frequently, but weave has
same kworker issue with a lower frequency. I have also disabled ipv6
on many nodes, but this doesn't solve the issue either.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.15.0-1040-azure 4.15.0-1040.44
ProcVersionSignature: User Name 4.15.0-1040.44-azure 4.15.18
Uname: Linux 4.15.0-1040-azure x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Jun 7 17:14:08 2019
SourcePackage: linux-signed-azure
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: linux-signed-azure (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug uec-images xenial
** Attachment added: "output.log"
https://bugs.launchpad.net/bugs/1832022/+attachment/5269380/+files/output.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1832022
Title:
Kworker stuck 100% high Workqueue: netns cleanup_net _raw_spin_lock
Status in linux-signed-azure package in Ubuntu:
New
Bug description:
I read your following post (https://lkml.org/lkml/2019/5/29/309).
Is there any other configuration to disable or which patch is required
to resolve this issue?
I am facing a very similar issue with almost identical output from
dmesg call trace. This occurs with high frequency. It's fairly easy
to identify as kworker usage gets stuck very high when the problem
occurs, but this manifests into a bigger problem as docker containers
cannot start/restart and host requires a reboot to resolve. I have
machines running Ubuntu with various kernels (4.15.0-1031-azure
through 4.15.0-1041-azure) and problem occurs randomly on every kernel
version. Using weave plugins vs docker overlay drivers for swarm
scope, docker overlay drivers seem to have the problem more
frequently, but weave has same kworker issue with a lower frequency.
I have also disabled ipv6 on many nodes, but this doesn't solve the
issue either.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.15.0-1040-azure 4.15.0-1040.44
ProcVersionSignature: User Name 4.15.0-1040.44-azure 4.15.18
Uname: Linux 4.15.0-1040-azure x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Jun 7 17:14:08 2019
SourcePackage: linux-signed-azure
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-azure/+bug/1832022/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
