OK, we are much closer to repeating this oops. Ignore the original instructions - that seems to be a surprising lxc feature rather than the oops.
In order to repeat, you need to have a) a container b) which is forwarding IPv4 traffic from one interface in the container to another (2 veth interfaces in this case) - one ping packet per second will do c) iptables with an IP conntrack rule. d) delete the container (it doesn't matter if you delete the iptables rule first and sleep for a couple of seconds). You then get the oops above. This also occurs on root@node-10-157-128-101:~# uname -a Linux node-10-157-128-101 3.0.0-10-server #16-Ubuntu SMP Fri Sep 2 18:51:05 UTC 2011 x86_64 GNU/Linux I have attached a double oops from that kernel too. ** Attachment added: "oops.txt" https://bugs.launchpad.net/ubuntu/+source/linux-lts-backport-natty/+bug/843892/+attachment/2376908/+files/oops.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/843892 Title: Repeatable kernel oops on container delete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-backport-natty/+bug/843892/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
