Comment 12 for bug 1273386

Hi Salvatore, so that old crash really looks quite similar. One interesting difference is that this process did simply exit and was not killed. Which sounds, like you did suspect as well, that this is not a regression in a recent kernel but something in the way things are executed changed and makes it just happen more often now.

I hear from James Page that right now some changes in OpenStack will cause more things happen in parallel. That maybe causes some races to get triggered which haven't been observed (that often) before.

To get a better understanding what the exact state of things is when this happens, would it be possible to enable crashdump on one of the development machines experiencing the issue and set it to panic on the oops? A description how to set up crashdump you would find at https://wiki.ubuntu.com/Kernel/CrashdumpRecipe. To cause the oops to become a panic you would have to echo 1 into /proc/sys/kernel/panic_on_oops after boot.