It's is mainline since v4.20-rc6. Have you tried it?
--
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/1765980
Title:
IPv6 fragments with nf_conntrack_reasm loaded cause net_mutex deadlock
While digging into this - I found the following commit which might contain a
fix:
https://github.com/torvalds/linux/commit/ebaf39e6032faf77218220707fc3fa22487784e0
** Changed in: linux (Ubuntu Bionic)
Status: Expired => Confirmed
--
You received this bug notification because you are a
This has expired, but affects me too here.
I'm specifically using Proxmox, which uses Ubuntu for upstream kernel -
currently at 4.15.18, and I see the same symptoms.
Specifically LXC, specifically at stop and specifically kworker using 100% of
one core and preventing startup of other containers.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu Bionic) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
So far I have not been able to reproduce it on the mainline kernel linked above.
However, given the intermittent nature of the problem, I'm not convinced that
this was actually fixed.
The source code related to the underlying root cause looks unchanged, and the
symptoms may well be hidden away
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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
** Description changed:
I've spent the last few days tracking down an issue where an attempt to
shutdown an LXD container after several hours of host uptime on Ubuntu
Bionic (4.15.0-15.16-generic) would cause a kworker thread to start
spinning on one CPU core and all subsequent container
The cause of the issue is already understood, and the machine currently isn't
running an unmodified kernel for debugging reasons. Apport logs won't help here.
Contact me if you need specific information.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this
9 matches
Mail list logo
