Bug tracked upstream: https://github.com/dotcloud/docker/issues/6370
A fix is on the way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327442
Title:
docker multicast packets origination addresses
For what it's worth, some bugs can be easier to reproduce on machines
with lots of cores (that might explain why you couldn't reproduce it on
your local laptop).
I recall that bug #1011792 never happened on our local 4-cores VM, but
the same workload would lock up a 8-cores VM in a few hours.
--
The sequence of ip link ...` commands does not provoke the bug with the
3.11.0 kernel that you indicated.
Tags and status updated as requested.
Thanks!
** Tags added: kernel-fixed-upstream
** Changed in: linux-lts-raring (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug
Public bug reported:
When destroying a veth interface when both members of the veth pair are
up, a kernel bug is triggered.
How to reproduce:
ip link add type veth
ip link set veth0 up
ip link set veth1 up
ip link del veth0
I've uploaded the kernel log to
https://gist.github.com/jpetazzo/619092
For the record: we also experienced this issue on EC2 PV instances
(m2.2xlarge in us-east-1), using a very intensive workload (~1000 LXC
containers running a mix of web apps and databases). Running any kind of
3.X kernel (3.2, 3.4, 3.6) causes our test workload to crash in less
than one hour.
The
On my setup (Dell 6420 with integrated HD3000; shows as 8086:0126 (rev
09) in lspci; running Debian 2.6.38-2), the bug appears only after a
while (so it's hard to reproduce).
I tried your new kernel anyway. I got the error just once, after the boot:
[ 73.270170] [drm:i915_hangcheck_ring_idle] *E
