kernel-packages team mailing list archive

[Salvatore Orlando <1273386@xxxxxxxxxxxxxxxxxx>]

Hi Stefan,

I have a few more info.
I am trying to run the tests which trigger the issue on two machines, one with 3.2.0-57 and the other with 3.2.0-58.
So far, after 20 runs on each machine, the crash did not happen, so I can't yet confirm the regression.

However, back in october we had another kernel issue, which we solved by
not executing anymore the process which was causing it (arping). This
was originally tracked under bug 1224001.

I've looked at a crash dump I saved from the time [1], and it's exactly the same.
So I think that the update from 3.2.0-57 to 58 rather than introduce a bug exacerbated a pre-existent condition.
Indeed I also verified that the diff did not introduce any change in the do_exit code path.

Finally, just for the sake of it, I tried to apply [2], but just ended up crashing the kernel at every exit call
Stefan, let me know if there is anything I can do to help you  nail down the issue once the bug manifests; I'm not trying to write a script which just obsessively reproduces the sequence of operations which leads to the crash in the hope to have something easily reproducible.

[1] http://paste.openstack.org/show/48056/
[2] https://kernel.googlesource.com/pub/scm/linux/kernel/git/khilman/linux-omap-pm/+/8aac62706adaaf0fab02c4327761561c8bda9448%5E%21/#F0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1273386

Title:
  Neutron namespace metadata proxy triggers kernel crash on Ubuntu
  12.04/3.2 kernel

Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Compute (Nova):
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  In the past 9 days we have been seeing very frequent occurences of
  this kernel crash: http://paste.openstack.org/show/61869/

  Even if the particular crash pasted here is triggered by dnsmasq, in
  almost all cases the crash is actually triggered by the neutron metada
  proxy.

  This also affects nova badly since this issue, which appears namespace
  related, results in a hang while mounting the ndb device for key
  injection.

  logstash query:
  http://logstash.openstack.org/#eyJzZWFyY2giOiJcImtlcm5lbCBCVUcgYXQgL2J1aWxkL2J1aWxkZC9saW51eC0zLjIuMC9mcy9idWZmZXIuYzoyOTE3XCIgYW5kIGZpbGVuYW1lOnN5c2xvZy50eHQiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wMS0xNlQxODo1MDo0OCswMDowMCIsInRvIjoiMjAxNC0wMS0yN1QxOToxNjoxMSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxMzkwODUwMzI2ODY0fQ==

  We have seen about 398 hits since the bug started to manifest.
  Decreased hit rate in the past few days is due to less neutron patches being pushed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1273386/+subscriptions