The only warning I'm getting in the part of the code impacted by the
patch is:
---------------------
../../../../../ompi/mca/btl/openib/btl_openib_async.c(322): warning
#188: enumerated type mixed with another type
event_type ^= IBV_XRC_QP_EVENT_FLAG;
---------------------
Regards,
On Wed, 2010-07-14 at 14:10 -0400, Jeff Squyres wrote:
> Do you get additional warnings when compiling with the intel compiler (about
> printf'ing an enum type)? I seem to recall that there's already a truckload
> of those kinds of warnings...
>
>
> On Jul 13, 2010, at 1:58 AM, nadia.derbey wrote:
>
> > Hi,
> >
> > When the asynchronous events device handler(btl_openib_async_deviceh())
> > gets an async event and XRC is enabled, the XRC bit is cleared to
> > process the event_type value, but orte_show_help is called with the
> > event_type original value (i.e. XRC bit still present). This leads to
> > the following kind of message:
> >
> > ----------------------------------------------------------
> > The OpenFabrics stack has reported a network error event. Open MPI
> > will try to continue. but your job may end up failing.
> >
> > Local host: XXXX
> > MPI process PID: 31818
> > Error number: -2147483645 (UNKNOWN)
> > This error may indicate connectivity problems within the fabric;
> > please contact your system administrator
> > -----------------------------------------------------------
> >
> > While the expected error number is
> > Error number: 3 (IBV_EVENT_QP_ACCESS_ERR)
> >
> > I propose the attached small patch to fix this issue.
> >
> > Regards,
> > Nadia
> >
> > --
> > nadia.derbey <[email protected]>
> >
> > <001_async_event_type.patch>_______________________________________________
> > devel mailing list
> > [email protected]
> > http://www.open-mpi.org/mailman/listinfo.cgi/devel
>
>
--
nadia.derbey <[email protected]>
