>I talked to Sean Hefty about it, but we never figured out a definitive
>cause or solution. My best guess is that there is something wonky
>about multiple processes simultaneously interacting with the IBCM
>kernel driver from userspace; but I don't know jack about kernel
>stuff, so that's a total SWAG.
The only reason I can think of why ib_cm_listen() fails is if there's a conflict
with the service_id and/or service_mask from multiple threads. What does OMPI
pass in for these parameters?