*** This bug is a duplicate of bug 1711535 ***
https://bugs.launchpad.net/bugs/1711535
4.4.0-94.117 has solved the problem so I'll mark this as a duplicate of
LP: #1711535 (update to stable kernel 4.4.82).
** This bug has been marked a duplicate of bug 1711535
Xenial update to 4.4.82
This really looks like https://patchwork.ozlabs.org/patch/799015/ which
fortunately made it into 4.4.0-94.117. I'll give that -proposed kernel a
test run.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.13 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
I'm now seeing similar traces on a wildly different machine that's not
using the bonding module. All machines are KVM hypervisors with
VHOST_NET_ENABLED=1. I'm attaching multiple dmesg extract from 3
machines, 2 PowerEdge R830 and 1 old Core 2 Duo/Xeon.
** Summary changed:
- linux 4.4.0-93
So far those messages were only noticed on 2 of our hypervisor nodes.
I'm attaching the relevant extracts of dmesg on those 2 machines.
** Attachment added: "multiple-dmesg.tgz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713787/+attachment/4940943/+files/multiple-dmesg.tgz
--
You
5 matches
Mail list logo
