I think this is two separate problems. The kernel bug is one thing, but we now think it may not be recreated using the method specified.
Our method of attempting to recreate the oops (which appears reliably in an application we have written) does indeed cause an immediate reboot, but we now think for a different reason; the exact commands are set out above and the network setup was a desktop with eth0 on DHCP (i.e. nothing very exciting). We were not passing a -f argument to lxc-create, and we are now guessing this running /sbin/init (perhaps inside the container). ^C then kills the container's /sbin/init, which causes the system to reboot. It would probably be a good thing if in the absence of a config file (which the manpage describes as optional) lxc-create did not run /sbin/init by default (if that's what it's doing), but perhaps ran /bin/sh or something, if only on the principle of least surprise. >From my point of view the bug is really the oops though. It looks like we need to find another way to duplicate that. -- 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
