The following seems pretty reliable to me: - gcc reproducer.c -o reproducer (using the paste.ubuntu.com code above) - sudo ./reproducer - ctrl+c - lxc-start -n <some-container> - dmesg | grep unregister
It appears that reproducing it that way is very reliable here, though the result is slightly different. Using this reproducer, the container will usually hang at startup for a few minutes, then eventually succeed to boot. When getting the bug without that reproducer, it'd usually hang indefinitely (where indefinitely > 10 minutes). -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
