Hi,
> > >>> I have installed openmpi-1.8.2rc2 with gcc-4.9.0 on Solaris
> > >>> 10 Sparc and I receive a bus error, if I run a small program.
I've finally reproduced the bus error in my SPARC environment.
#0 0x00db4740 (__waitpid_nocancel + 0x44)
(0x200,0x0,0x0,0xa0,0xf80100064af0,0
I have an extremely vague recollection about a similar issue in the
datatype engine: on the SPARC architecture the 64 bits integers must be
aligned on a 64bits boundary or you get a bus error.
Takahiro you can confirm this by printing the value of data when signal is
raised.
George.
On Fri, Au
Hi George,
> Takahiro you can confirm this by printing the value of data when signal is
> raised.
It's in the trace.
0x07fede74
#2 0x0282aff4 (store + 0x540) (uid=(unsigned long *)
0x0118a128,scope=8:'\b',key=(char *) 0x0106a0a8
"opal.local.ldr",data=(void *) 0x
Using the "--mca btl tcp,self" switch to mpirun solved all the issues (in
addition to
the requirement to include the --mca btl_tcp_if_include eth0 switch). I believe
the "--mca btl tcp,self" switch limits inter-process communication within a
node to using the TCP
loopback rather than shared memor
On Aug 8, 2014, at 1:24 AM, Lane, William wrote:
> Using the "--mca btl tcp,self" switch to mpirun solved all the issues (in
> addition to
> the requirement to include the --mca btl_tcp_if_include eth0 switch). I
> believe
> the "--mca btl tcp,self" switch limits inter-process communication wit
Hello. I have read a couple of posts on Stackoverflow that seem to imply
that independently started processes should be able to communicate via
ompi-server, but I have not been able to accomplish this. Is this actually
possible? Here is an outline of what I have done and the error I am
receiving. I
