hmmm, that's very hard for us to analyze. We did meet a similar oops
before because of the heavy workload and CFQ block IO scheduler. Could
you a test for us? change your default Block IO scheduler from CFQ to
deadline and run LXC as usual to verify this issue is gone. I'm just
guess and hope this can do some help.
-Bryan
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021471
Title:
stuck on mutex_lock creating a new network namespace when starting a
container
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1021471/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
