Since I have a system that has the scif libraries installed I will try to
reproduce and see if I can come up with a fix. It will probably be sometime
next week at the earliest.
-Nathan
From: devel [devel-boun...@open-mpi.org] on behalf of Gilles Gouaillar
Nathan, or anybody with access to the target hardware,
If you can provide a minimalistic output of the applications with and
without the above-mentioned patch and with mpi_ddt_unpack_debug and
mpi_ddt_pack_debug, and mpi_ddt_position_debug set to 1, I would try
to help.
George.
On Thu, May 8,
George,
you do not need any hardware, just download MPSS from Intel and install it.
make sure the mic kernel module is loaded *and* you can read/write to the
newly created /dev/mic/* devices.
/* i am now running this on a virtual machine with no MIC whatsoever */
i was able to improve things a b
If you can get me the backtrace from one of the crash core files I would like
to see what is going on there.
-Nathan
From: devel [devel-boun...@open-mpi.org] on behalf of Gilles Gouaillardet
[gilles.gouaillar...@iferc.org]
Sent: Thursday, May 08, 2014 1:3
Nathan and George,
here are the output files of the original test_scif.c
the command line was
mpirun -np 2 -host localhost --mca btl scif,vader,self --mca
mpi_ddt_unpack_debug 1 --mca mpi_ddt_pack_debug 1 --mca
mpi_ddt_position_debug 1 a.out
this is a silent failure and there is no core file
the
Hi,
My reproducer failed even with one port enabled (-mca btl_openib_if_include
mlx4_0:1 ).
I tried with trunk as well - the same issue.
Best,
Elena
On Thu, May 8, 2014 at 11:49 AM, Gilles Gouaillardet <
gilles.gouaillar...@iferc.org> wrote:
> Nathan and George,
>
> here are the output files o
Nathan and George,
here are the (compressed) traces
Gilles
On 2014/05/08 16:43, Hjelm, Nathan T wrote:
> If you can get me the backtrace from one of the crash core files I would like
> to see what is going on there.
>
> -Nathan
>
> From: devel [devel-bou
WHAT: Remove the backwards-compatibility autogen.sh sym link
WHY: Because it's time
WHERE: svn rm autogen.sh
TIMEOUT: Teleconf next Tuesday, 13 May 2014
MORE DETAIL:
We converted from autogen.sh to autogen.pl nearly 4 years ago (2010-09-17).
The autogen.sh->autogen.pl sym link was put in sho
+1
On Thu, May 8, 2014 at 6:08 AM, Jeff Squyres (jsquyres)
wrote:
> WHAT: Remove the backwards-compatibility autogen.sh sym link
>
> WHY: Because it's time
>
> WHERE: svn rm autogen.sh
>
> TIMEOUT: Teleconf next Tuesday, 13 May 2014
>
> MORE DETAIL:
>
> We converted from autogen.sh to autogen.p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1
Best
Steve...
On 5/8/14, 6:08 AM, Jeff Squyres (jsquyres) wrote:
> WHAT: Remove the backwards-compatibility autogen.sh sym link
>
> WHY: Because it's time
>
> WHERE: svn rm autogen.sh
>
> TIMEOUT: Teleconf next Tuesday, 13 May 2014
>
> MORE DETA
This will break my build but it’s an easy fix so don’t let that stop you.
Ashley.
On 8 May 2014, at 11:08, Jeff Squyres (jsquyres) wrote:
> WHAT: Remove the backwards-compatibility autogen.sh sym link
>
> WHY: Because it's time
>
> WHERE: svn rm autogen.sh
>
> TIMEOUT: Teleconf next Tuesday
I started getting build failures against trunk on the 29th, most likely as a
result of this commit:
https://github.com/open-mpi/ompi-svn-mirror/commit/3f42cbf50670c5b311cc4414dbb3f4ccf762e455
It looks like there was another commit almost immediately afterwards which
fixed the first problem (in
Hi, Adam
We (MLNX) are working on a new SLURM PMI2 plugin that we plan to eventually
push upstream. However, to use it, it will require linking in a proprietary
Mellanox library that accelerates the collective operations (available in
MOFED versions 2.1 and higher.) Similar in spirit to the MXM M
On Thu, 8 May 2014 09:10:00 AM Joshua Ladd wrote:
> We (MLNX) are working on a new SLURM PMI2 plugin that we plan to eventually
> push upstream. However, to use it, it will require linking in a proprietary
> Mellanox library that accelerates the collective operations (available in
> MOFED versions
On May 8, 2014, at 8:59 AM, Ashley Pittman wrote:
> This will break my build but it’s an easy fix so don’t let that stop you.
Something like this should do ya:
--- bogus 2014-05-08 06:26:19.759259593 -0700
+++ bogus-new 2014-05-08 06:26:22.567481480 -0700
@@ -14,7 +14,11 @@
-./aut
I was thinking of something even easier than that ;) I try to keep an eye on
the message queue functionality so it’s not often that I need to build code
over four years old from source.
Ashley.
On 8 May 2014, at 14:27, Jeff Squyres (jsquyres) wrote:
> On May 8, 2014, at 8:59 AM, Ashley Pitt
On May 8, 2014, at 6:23 AM, Chris Samuel wrote:
> On Thu, 8 May 2014 09:10:00 AM Joshua Ladd wrote:
>
>> We (MLNX) are working on a new SLURM PMI2 plugin that we plan to eventually
>> push upstream. However, to use it, it will require linking in a proprietary
>> Mellanox library that accelerate
I'm unable to reproduce your error, even with a git clone of the mirror.
Perhaps you need to "git clean -df"?
On May 8, 2014, at 9:09 AM, Ashley Pittman wrote:
>
> I started getting build failures against trunk on the 29th, most likely as a
> result of this commit:
>
> https://github.com/o
Chris,
The necessary packages will be supported and available in community OFED.
Josh
On Thu, May 8, 2014 at 9:23 AM, Chris Samuel wrote:
> On Thu, 8 May 2014 09:10:00 AM Joshua Ladd wrote:
>
> > We (MLNX) are working on a new SLURM PMI2 plugin that we plan to
> eventually
> > push upstream.
Ah, it was something my end. I had a bug in my build script that it wasn’t
wiping the install directory before doing the build. This might be an
indication that something in the build is picking up the install directory in
preference to the build directory but I don’t think that would represe
This RFC is now complete - the renaming exercise is done. My apologies to all
for the churn, and my deepest thanks for your patience.
I know it will take awhile to get used to using the revised names and to avoid
breaking the abstractions going forward. We have a "canary" for most of the
abstra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/05/14 23:45, Ralph Castain wrote:
> Artem and I are working on a new PMIx plugin that will resolve it
> for non-Mellanox cases.
Ah yes of course, sorry my bad!
- --
Christopher SamuelSenior Systems Administrator
VLSCI - Victorian L
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/05/14 00:16, Joshua Ladd wrote:
> The necessary packages will be supported and available in community
> OFED.
We're constrained to what is in RHEL6 I'm afraid.
This is because we have to run GPFS over IB to BG/Q from the same NSDs
that talk GP
23 matches
Mail list logo
