Re: [OMPI devel] 1.3.1 fails with GM

I've just tested OMPI 1.3.1 w/ GM 2.0.19 and the "ring" test from LAM's examples directory. I too see an early death. The backtrace is shown below. -Paul $ mpirun -mca btl gm,self -H pcp-i-1,pcp-i-2 ./ring Rank 0 starting message around the ring -- 1st of 5 [pcp-i-1:27587] *** Process receive

Re: [OMPI devel] 1.3.1 fails with GM

Hi Christian, Christian Siebert wrote: I just gave the new release 1.3.1 a go. While Ethernet and InfiniBand seem to work properly, I noticed that Myrinet/GM compiles fine but gives a segmentation violation in the first attempt to communicate (MPI_Send in a simple "hello world" application). I

[OMPI devel] OMPI 1.5.0

Hello all As Jeff indicated in an earlier note, Open MPI is revising its release procedure to embrace a feature and a stable series structure. Jeff and I have been designated co-release manager of the next feature/stable pair (to follow the current 1.3 feature, and upcoming 1.4 stable). O

[OMPI devel] 1.3.1 fails with GM

Hi, I just gave the new release 1.3.1 a go. While Ethernet and InfiniBand seem to work properly, I noticed that Myrinet/GM compiles fine but gives a segmentation violation in the first attempt to communicate (MPI_Send in a simple "hello world" application). Is GM not supported anymore or

Re: [OMPI devel] 1.3.1rc5

On Mar 20, 2009, at 11:06 AM, Eugene Loh wrote: > I'm still seeing a very low incidence of the sm segv during startup (. > 01% -- 23 tests out of ~160k), so let's ship 1.3.1 and roll in > Eugene's new sm code for 1.3.2. > I wanted to join in the fun, but... no go. I'm running an "MPI_Init()

Re: [OMPI devel] 1.3.1rc5

Jeff Squyres wrote: Looks good to cisco. Ship it. I'm still seeing a very low incidence of the sm segv during startup (. 01% -- 23 tests out of ~160k), so let's ship 1.3.1 and roll in Eugene's new sm code for 1.3.2. I wanted to join in the fun, but... no go. I'm running an "MPI_Init()"

Re: [OMPI devel] opal_util_register_stackhandlers()

On Mar 20, 2009, at 9:12 AM, Kees Verstoep wrote: Thanks for the quick feedback and fix! This should work. I will test it out when the next release candidate becomes available. We have a fairly aggressive schedule for 1.3.2 -- but it'll still be at least a few weeks before rc's start appe

Re: [OMPI devel] opal_util_register_stackhandlers()

Thanks for the quick feedback and fix! This should work. I will test it out when the next release candidate becomes available. Cheers, Kees Verstoep Jeff Squyres wrote: > Thanks for the bug report! > > I've just changed the behavior to emit a warning and *not* intercept a signal > if the old

Re: [OMPI devel] RFC: Final cleanup of included headers

Agreed - thanks for the help! At the moment, almost none of the 1.3.2 CMRs apply cleanly... :-/ That's the source of my concern with a change that would hit so many things. Thanks Rainer! Ralph On Mar 20, 2009, at 6:45 AM, Jeff Squyres wrote: This sounds reasonable -- small changes are alw

Re: [OMPI devel] RFC: Final cleanup of included headers

This sounds reasonable -- small changes are always appreciated. If we can hold off on the big patch until 1.3 is about to morph into 1.4, that would be good. Can you remind us about this issue when 1.3.2 gets out the door? (sorry, not trying to be a jerk; I just know that my short term me