Hi Chris
I think you misunderstood the issue here. The problem is that mpirun appears to
be hanging before it ever gets to the point of launching something. Enabling
debug output should tell us if that is true or not, and we can then debug from
there.
On Sep 20, 2013, at 7:16 PM, Christopher
Hi,
Sorry about that. the fix is here: r29223
Regards
M
On Fri, Sep 20, 2013 at 7:32 PM, Jeff Squyres (jsquyres) wrote:
> Mellanox --
>
> Please remove all uses of bzero. memset is the portable way to go here.
>
>
>
> On Sep 20, 2013, at 12:30 PM, "David Goodell
Thank you!
Sent from my phone. No type good.
On Sep 21, 2013, at 3:27 AM, "Mike Dubman"
> wrote:
Hi,
Sorry about that. the fix is here: r29223
Regards
M
On Fri, Sep 20, 2013 at 7:32 PM, Jeff Squyres (jsquyres)
Don't forget to add this to the shmem CMR.
Sent from my phone. No type good.
On Sep 21, 2013, at 9:29 AM, "Jeff Squyres (jsquyres)"
> wrote:
Thank you!
Sent from my phone. No type good.
On Sep 21, 2013, at 3:27 AM, "Mike Dubman"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/09/13 14:33, Ralph Castain wrote:
> I think you misunderstood the issue here. The problem is that
> mpirun appears to be hanging before it ever gets to the point of
> launching something.
Ah, quite correct, I hadn't realised the debug info
Dear all,
Really thanks a lot for your efforts. I too downloaded the trunk to check if it
works for my case and as of revision 29215, it works for the original case I
reported. Although it works, I still see the following in the output. Does it
mean anything?
On Sep 21, 2013, at 4:54 PM, Suraj Prabhakaran
wrote:
> Dear all,
>
> Really thanks a lot for your efforts. I too downloaded the trunk to check if
> it works for my case and as of revision 29215, it works for the original case
> I reported. Although it works, I
Strange, the backtrace below looks total crazy, I don't see how debug
checks could still pass in that case.
Any chance you valgrind that thing?
Brice
Le 21/09/2013 01:09, Ralph Castain a écrit :
> Hmmm...nope, not a peep (no extra output at all). Just segfaulted like
> before.
>
> On Sep 20,
Okay, I found it - was a sequencing problem in OMPI itself (we "set" the new
topology too late in the setup sequence). Sorry for false alarm.
Thanks for the help!
Ralph
On Sep 20, 2013, at 11:36 PM, Brice Goglin wrote:
> Strange, the backtrace below looks total crazy, I