[ofa-general] Re: 2.6.30.1: possible irq lock inversion dependency detected

[Roland Dreier]

 > After having applied this patch it took somewhat longer before a
 > locking inversion report was generated, but unfortunately there still
 > was a locking inversion report generated (see also
 > http://bugzilla.kernel.org/show_bug.cgi?id=13757 for the details):

ummm, yikes...

can you apply the hack patch I sent originally to take priv->lock from
an interrupt ASAP and try that along with the fix patch to drop
priv->lock before calling ipoib_send()?  That might make the lockdep
trace understandable.

 - R.