*Hi All,*
I have one issue with MTT trivial tests.All tests are not getting
passed,Please read below for detailed description.
Today I ran mtt trivial tests with latest ofed package
OFED-1.5-20091217-0600 (ompi-1.4), between two machines,I was able to
run the MTT trivial tests manually but
Hi.
We have started to scale up one of our codes and sometimes we get messages
like this:
[c9-13.local:31125] Memory 0x2aaab7b64000:217088 cannot be freed from
the registration cache. Possible memory corruption.
It seems like the application runs normally and it does not crash becaus of
this.
Afraid I don't know enough about MPICH2's different process managers (and why
they need more than one) to answer that question.
On Dec 21, 2009, at 9:29 PM, Sangamesh B wrote:
> Hi,
>
> MPICh2 has different process managers: MPD, SMPD, GFORKER etc. Is the
> Open MPI's startup daemon or
On Tue, 2009-12-22 at 09:59 +0530, Sangamesh B wrote:
> Hi,
>
> MPICh2 has different process managers: MPD, SMPD, GFORKER etc.
It also has Hydra.
> Is the Open MPI's startup daemon orted similar to MPICH2's smpd? Or
> something else?
My understand is that SMPD is for launching on Windo
Hi Ralph,
Somehow I did not receive your last answer as mail, so I reply to myself...
Thanks for the explanation. I thought that the prefix issue would be
handled by the OMPI configure parameter
"enable-mpirun-prefix-by-default". But now I see your point. Anyway, I
did not find any further informa
Hi Vishal,
This is an MTT question for mtt-us...@open-mpi.org (see comments
below).
On Tue, Dec/22/2009 03:54:08PM, vishal shorghar wrote:
>Hi All,
>
>I have one issue with MTT trivial tests.All tests are not getting
>passed,Please read below for detailed description.
>
>Today I
I got the following problem while trying to run vt-enabled HPL benchmark on a
single 8-core Linux node.
OTF ERROR in function OTF_WBuffer_setTimeAndProcess, file: OTF_WBuffer.c, line:
308:
time not increasing. (t= 2995392288, p= 2)
vtunify: Error: Could not read events of OTF stream [namestub ./
vasilis gkanis wrote:
I had a similar problem with the portland Fortran compiler. I new that this
was not caused by a network problem ( I run the code on a single node with 4
CPUs). After I tested pretty much anything, I decided to change the compiler.
I used the Intel Fortran compiler and ever
