Sounds like a typical deadlock situation. All processors are waiting for one
another.
Not a specialist but from what I know if the messages are small enough they'll
be offloaded to kernel/hardware and there is no deadlock. That why it might
work for small messages and/or certain mpi implementat
I'm sorry.
The previous code block reported, is referred to 32 bit not 64. So, the
right code block is:
static inline int opal_atomic_cmpset_32( volatile int32_t *addr,
int32_t oldval, int32_t newval)
{
unsigned char ret;
__asm__ __volatile (
Maybe, i solved this bug, deleting long cast.
Now, in compile time, it works well, but at runtime, there are other
problems, like this:
../../../opal/class/opal_object.h:428:Bounds error: pointer arithmetic would
overrun the end of the object.
../../../opal/class/opal_object.h:428: Pointer value:
Hello,
Well, actually I'm quite sure that it was not the firewall because I had to
turn it off as otherwise no connection could be established. So my
iptables --list
returns
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target
