Re: [OMPI devel] Possible OMPI 1.6.5 bug? SEGV in malloc.c

2013-08-29 Thread Jeff Squyres (jsquyres)
On Aug 29, 2013, at 7:33 PM, Christopher Samuel wrote: > OK, so I'll try testing again with a larger limit to see if that will > ameliorate this issue. I'm also wondering where this is happening in > OMPI, I've a sneaking suspicion this is at MPI_INIT(). FWIW, the stack traces you sent are not

Re: [OMPI devel] Possible OMPI 1.6.5 bug? SEGV in malloc.c

2013-08-29 Thread Christopher Samuel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jeff, Ralph, On 29/08/13 23:30, Jeff Squyres (jsquyres) wrote: > Let me try to understand this test: > > - you're simulating a 1GB memory limit via ulimit of virtual > memory ("ulimit -v $((1*1024*1024))"), or 1,048,576 bytes. Yeah, basically do

Re: [OMPI devel] NO LT_DLADVISE - CANNOT LOAD LIBOMPI JAVA BINDINGS

2013-08-29 Thread Ralph Castain
you need to install the lt_dladvise package as well On Aug 29, 2013, at 6:18 AM, Bibrak Qamar wrote: > Hi all, > > I have the following runtime error while running Java MPI jobs. I have check > the previous answers to the mailing list regarding this issue. > > The solutions were to install l

Re: [OMPI devel] Possible OMPI 1.6.5 bug? SEGV in malloc.c

2013-08-29 Thread Jeff Squyres (jsquyres)
Let me try to understand this test: - you're simulating a 1GB memory limit via ulimit of virtual memory ("ulimit -v $((1*1024*1024))"), or 1,048,576 bytes. - you're trying to alloc 1070*10^6 = 1,070,000,000 bytes in an MPI app - OMPI is barfing in the ptmalloc allocator Meaning: you're trying t

[OMPI devel] NO LT_DLADVISE - CANNOT LOAD LIBOMPI JAVA BINDINGS

2013-08-29 Thread Bibrak Qamar
Hi all, I have the following runtime error while running Java MPI jobs. I have check the previous answers to the mailing list regarding this issue. The solutions were to install libtool and configure-compile-and-install openmpi again this time with the latest version of m4 autoconfig automake li

Re: [OMPI devel] Possible OMPI 1.6.5 bug? SEGV in malloc.c

2013-08-29 Thread Ralph Castain
I would guess the problem is that your memory restriction is causing a malloc failure based on this line: > [pid 6796] mmap(NULL, 8560001024, PROT_READ|PROT_WRITE, > MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 ENOMEM (Cannot allocate memory) and we probably don't protect against that failure as wel

Re: [OMPI devel] Compilation error with OpenIPMI in ubntu 12.04

2013-08-29 Thread George Bosilca
Wrong mailing list, this one is for the development of OpenMPI. For OpenIPMI you should use openipmi-develo...@lists.sourceforge.net. George. On Aug 29, 2013, at 08:16 , Rishi Kaundinya Mutnuru wrote: > Hi, > I have downladed OpenIPMI-2.0.20-rc1 and tried using for developing a > hardware

[OMPI devel] Compilation error with OpenIPMI in ubntu 12.04

2013-08-29 Thread Rishi Kaundinya Mutnuru
Hi, I have downladed OpenIPMI-2.0.20-rc1 and tried using for developing a hardware monitoring tool. I am facing compilation issues on ubuntu 12.04 host. I am snipping the error below with the system details. Highly appreciate your quick response as this critical for our work. $uname -a Linux

Re: [OMPI devel] Possible OMPI 1.6.5 bug? SEGV in malloc.c

2013-08-29 Thread Christopher Samuel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28/08/13 19:36, Chris Samuel wrote: > With RHEL 6.4 gfortran it instead SEGV's straight away Using strace I can see a mmap(2) (called from malloc I presume) failing just before the SEGV. Process 6799 detached Process 6798 detached Hello, world,