Bug is stale/abandoned. Closing
** Changed in: linux (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275809
Title:
(docker/lxc) container restart causes
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.
--
I just had the same issue when rebooting the system although aufs wasn't
directly involved (it was loaded but not used). I'll blacklist it now
and see if it happens again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
I've tried to reproduce it with the same containers but with docker's
btrfs driver instead of the default aufs driver and I couldn't reproduce
it. So it might be an issue with aufs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Let me know if there is anything I can do to help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275809
Title:
(docker/lxc) container restart causes kernel to lockup
To manage notifications about
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275809
Title:
(docker/lxc) container restart causes kernel to lockup
To manage noti
apport information
** Tags added: apport-collected
** Description changed:
After restarting some 'ghost' docker containers on precise with the
raring-lts kernel, the kernel locks up and shows:
[1095015.392057] BUG: soft lockup - CPU#0 stuck for 22s! [gunicorn:12804]
... (for e
I could *not* reproduce this issue on my laptop, so it might be specific
to some aspect of our servers. Those are Dell PowerEdge R710 with
Intel(R) Xeon(R) CPU L5520 @ 2.27GHz and 24GB RAM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Looks like 3.14 has no support for aufs, so I can't reproduce it with
those (aufs based) containers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275809
Title:
(docker/lxc) container restart cause
The systems are new, so I'm not aware of any state where this doesn't
happen. I'll try the mainline kernel soon and will if I can reproduce it
there as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Do you you know if this is a regression? Was there a prior kernel
version that did not exhibit this bug?
Also, it would be good to know if the latest mainline kernel also has
the bug. It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc1-trusty/
--
You received th
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key kernel-stable-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275809
Title:
(docker/lxc) container res
12 matches
Mail list logo
