Re: [OMPI devel] [2.0.1rc2] SIGBUS on Linux/SPARC

2016-09-01 Thread Paul Hargrove 
Giles,

I will try the patch and let you know.
However, it will likely not be until tomorrow (Friday AM California time)
that I have results.

-Paul

On Wed, Aug 31, 2016 at 9:26 PM, Gilles Gouaillardet 
wrote:

> Thanks Paul,
>
>
> can you please try the patch available at https://patch-diff.
> githubusercontent.com/raw/open-mpi/ompi-release/pull/1357.patch ?
>
>
> Cheers,
>
>
> Gilles
>
> On 9/1/2016 2:12 AM, Paul Hargrove wrote:
>
> On an emulated UltraSPARC system running Linux (and using V9 ABI) I was
> able to build the RC, but get a SIGBUS when running ring_c.
> The problem is an unaligned 64-bit access, as shown by the gdb session
> below.
>
> I have not tried, but it *might* be possible to reproduce on PPC64 via
> "prctl --unaligned=signal".
>
> -Paul
>
>
> Core was generated by `examples/ring_c'.
> Program terminated with signal 10, Bus error.
> #0  0xf630ed64 in component_set_addr (peer=0xf6bb7114, uris=0x90ec8)
> at /home/phargrov/OMPI/openmpi-2.0.1rc2-linux-sparcv9/openmpi-
> 2.0.1rc2/orte/mca/oob/usock/oob_usock_component.c:318
> 318 if (OPAL_SUCCESS != opal_hash_table_get_value_
> uint64(&mca_oob_usock_module.peers,
>
> (gdb) l
> 313 if (ORTE_PROC_IS_APP) {
> 314 /* if this is my daemon, then take it - otherwise, ignore
> */
> 315 if (ORTE_PROC_MY_DAEMON->jobid == peer->jobid &&
> 316 ORTE_PROC_MY_DAEMON->vpid == peer->vpid) {
> 317 ui64 = (uint64_t*)peer;
> 318 if (OPAL_SUCCESS != opal_hash_table_get_value_
> uint64(&mca_oob_usock_module.peers,
> 319
>  (*ui64), (void**)&pr) || NULL == pr) {
> 320 pr = OBJ_NEW(mca_oob_usock_peer_t);
> 321 pr->name = *peer;
> 322 opal_hash_table_set_value_
> uint64(&mca_oob_usock_module.peers, (*ui64), pr);
>
> (gdb) print ui64
> $1 = (uint64_t *) 0xf6bb7114
>
> --
> Paul H. Hargrove  phhargr...@lbl.gov
> Computer Languages & Systems Software (CLaSS) Group
> Computer Science Department   Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>
>
> ___
> devel mailing 
> listde...@lists.open-mpi.orghttps://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>
>
>
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>



-- 
Paul H. Hargrove  phhargr...@lbl.gov
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

[OMPI devel] openmpi-2.0.0 - problems with ppc64, PGI and atomics

2016-09-01 Thread Vallee, Geoffroy R. 
Hello,

I get the following problem when we compile OpenMPI-2.0.0 (it seems to be 
specific to 2.x; the problem did not appear with 1.10.x) with PGI:

CCLD opal_wrapper
../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_sc_64'
../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_ll_64'
../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_swap_64'
make[1]: *** [opal_wrapper] Error 2

It is a little for me to pin point the exact problem but i can see the 
following:

$ nm ./.libs/libopen-pal.so | grep atomic
00026320 t 0017.plt_call.opal_atomic_add_32
00026250 t 0017.plt_call.opal_atomic_cmpset_32
00026780 t 0017.plt_call.opal_atomic_cmpset_64
000280c0 t 0017.plt_call.opal_atomic_cmpset_acq_32
00028ae0 t 0017.plt_call.opal_atomic_ll_64
00027fe0 t 0017.plt_call.opal_atomic_mb
00027d50 t 0017.plt_call.opal_atomic_rmb
00028500 t 0017.plt_call.opal_atomic_sc_64
00027670 t 0017.plt_call.opal_atomic_sub_32
00026da0 t 0017.plt_call.opal_atomic_swap_64
00027050 t 0017.plt_call.opal_atomic_wmb
0005e6a0 t mca_base_pvar_is_atomic
0004715c T opal_atomic_add_32
0004703c T opal_atomic_cmpset_32
000470e8 T opal_atomic_cmpset_64
00047060 T opal_atomic_cmpset_acq_32
0004710c T opal_atomic_cmpset_acq_64
0002a610 t opal_atomic_cmpset_ptr
00047094 T opal_atomic_cmpset_rel_32
00047134 T opal_atomic_cmpset_rel_64
00032cc0 t opal_atomic_init
00033980 t opal_atomic_init
000396a0 t opal_atomic_init
 U opal_atomic_ll_64
0002e460 t opal_atomic_lock
00032cf0 t opal_atomic_lock
000339b0 t opal_atomic_lock
00047024 T opal_atomic_mb
0004702c T opal_atomic_rmb
 U opal_atomic_sc_64
00047174 T opal_atomic_sub_32
 U opal_atomic_swap_64
0002e4e0 t opal_atomic_unlock
00032d70 t opal_atomic_unlock
00033a30 t opal_atomic_unlock
00047034 T opal_atomic_wmb
000324d0 t opal_lifo_pop_atomic
000cc260 t opal_lifo_pop_atomic
0002a490 t opal_lifo_push_atomic

Any idea of how to fix the problem?

Thanks,
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] openmpi-2.0.0 - problems with ppc64, PGI and atomics

2016-09-01 Thread Jeff Squyres (jsquyres) 
Can you try the latest v2.0.1 nightly snapshot tarball?


> On Sep 1, 2016, at 2:56 PM, Vallee, Geoffroy R.  wrote:
> 
> Hello,
> 
> I get the following problem when we compile OpenMPI-2.0.0 (it seems to be 
> specific to 2.x; the problem did not appear with 1.10.x) with PGI:
> 
> CCLD opal_wrapper
> ../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_sc_64'
> ../../../opal/.libs/libopen-pal.so: undefined reference to `opal_atomic_ll_64'
> ../../../opal/.libs/libopen-pal.so: undefined reference to 
> `opal_atomic_swap_64'
> make[1]: *** [opal_wrapper] Error 2
> 
> It is a little for me to pin point the exact problem but i can see the 
> following:
> 
> $ nm ./.libs/libopen-pal.so | grep atomic
> 00026320 t 0017.plt_call.opal_atomic_add_32
> 00026250 t 0017.plt_call.opal_atomic_cmpset_32
> 00026780 t 0017.plt_call.opal_atomic_cmpset_64
> 000280c0 t 0017.plt_call.opal_atomic_cmpset_acq_32
> 00028ae0 t 0017.plt_call.opal_atomic_ll_64
> 00027fe0 t 0017.plt_call.opal_atomic_mb
> 00027d50 t 0017.plt_call.opal_atomic_rmb
> 00028500 t 0017.plt_call.opal_atomic_sc_64
> 00027670 t 0017.plt_call.opal_atomic_sub_32
> 00026da0 t 0017.plt_call.opal_atomic_swap_64
> 00027050 t 0017.plt_call.opal_atomic_wmb
> 0005e6a0 t mca_base_pvar_is_atomic
> 0004715c T opal_atomic_add_32
> 0004703c T opal_atomic_cmpset_32
> 000470e8 T opal_atomic_cmpset_64
> 00047060 T opal_atomic_cmpset_acq_32
> 0004710c T opal_atomic_cmpset_acq_64
> 0002a610 t opal_atomic_cmpset_ptr
> 00047094 T opal_atomic_cmpset_rel_32
> 00047134 T opal_atomic_cmpset_rel_64
> 00032cc0 t opal_atomic_init
> 00033980 t opal_atomic_init
> 000396a0 t opal_atomic_init
> U opal_atomic_ll_64
> 0002e460 t opal_atomic_lock
> 00032cf0 t opal_atomic_lock
> 000339b0 t opal_atomic_lock
> 00047024 T opal_atomic_mb
> 0004702c T opal_atomic_rmb
> U opal_atomic_sc_64
> 00047174 T opal_atomic_sub_32
> U opal_atomic_swap_64
> 0002e4e0 t opal_atomic_unlock
> 00032d70 t opal_atomic_unlock
> 00033a30 t opal_atomic_unlock
> 00047034 T opal_atomic_wmb
> 000324d0 t opal_lifo_pop_atomic
> 000cc260 t opal_lifo_pop_atomic
> 0002a490 t opal_lifo_push_atomic
> 
> Any idea of how to fix the problem?
> 
> Thanks,
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] openmpi-2.0.0 - problems with ppc64, PGI and atomics

2016-09-01 Thread Vallee, Geoffroy R. 
This is indeed a little better but still creating a problem:

  CCLD opal_wrapper
../../../opal/.libs/libopen-pal.a(opal_progress.o): In function 
`_opal_progress_unregister':
/autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/runtime/opal_progress.c:459: 
undefined reference to `opal_atomic_swap_64'
../../../opal/.libs/libopen-pal.a(opal_progress.o): In function 
`_opal_progress_register':
/autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/runtime/opal_progress.c:398: 
undefined reference to `opal_atomic_swap_64'
make[2]: *** [opal_wrapper] Error 2
make[2]: Leaving directory 
`/autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/tools/wrappers'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal'
make: *** [all-recursive] Error 1

$ nm libopen-pal.a  | grep atomic
 U opal_atomic_cmpset_64
0ab0 t opal_atomic_cmpset_ptr
 U opal_atomic_wmb
0950 t opal_lifo_push_atomic
 U opal_atomic_cmpset_acq_32
03d0 t opal_atomic_lock
0450 t opal_atomic_unlock
 U opal_atomic_wmb
 U opal_atomic_ll_64
 U opal_atomic_sc_64
 U opal_atomic_wmb
1010 t opal_lifo_pop_atomic
 U opal_atomic_cmpset_acq_32
04b0 t opal_atomic_init
04e0 t opal_atomic_lock
 U opal_atomic_mb
0560 t opal_atomic_unlock
 U opal_atomic_wmb
 U opal_atomic_add_32
 U opal_atomic_cmpset_acq_32
0820 t opal_atomic_init
0850 t opal_atomic_lock
 U opal_atomic_sub_32
 U opal_atomic_swap_64
08d0 t opal_atomic_unlock
 U opal_atomic_wmb
0130 t opal_atomic_init
atomic-asm.o:
0138 T opal_atomic_add_32
0018 T opal_atomic_cmpset_32
00c4 T opal_atomic_cmpset_64
003c T opal_atomic_cmpset_acq_32
00e8 T opal_atomic_cmpset_acq_64
0070 T opal_atomic_cmpset_rel_32
0110 T opal_atomic_cmpset_rel_64
 T opal_atomic_mb
0008 T opal_atomic_rmb
0150 T opal_atomic_sub_32
0010 T opal_atomic_wmb
2280 t mca_base_pvar_is_atomic
 U opal_atomic_ll_64
 U opal_atomic_sc_64
 U opal_atomic_wmb
0900 t opal_lifo_pop_atomic

> On Sep 1, 2016, at 3:16 PM, Jeff Squyres (jsquyres)  
> wrote:
> 
> Can you try the latest v2.0.1 nightly snapshot tarball?
> 
> 
>> On Sep 1, 2016, at 2:56 PM, Vallee, Geoffroy R.  wrote:
>> 
>> Hello,
>> 
>> I get the following problem when we compile OpenMPI-2.0.0 (it seems to be 
>> specific to 2.x; the problem did not appear with 1.10.x) with PGI:
>> 
>> CCLD opal_wrapper
>> ../../../opal/.libs/libopen-pal.so: undefined reference to 
>> `opal_atomic_sc_64'
>> ../../../opal/.libs/libopen-pal.so: undefined reference to 
>> `opal_atomic_ll_64'
>> ../../../opal/.libs/libopen-pal.so: undefined reference to 
>> `opal_atomic_swap_64'
>> make[1]: *** [opal_wrapper] Error 2
>> 
>> It is a little for me to pin point the exact problem but i can see the 
>> following:
>> 
>> $ nm ./.libs/libopen-pal.so | grep atomic
>> 00026320 t 0017.plt_call.opal_atomic_add_32
>> 00026250 t 0017.plt_call.opal_atomic_cmpset_32
>> 00026780 t 0017.plt_call.opal_atomic_cmpset_64
>> 000280c0 t 0017.plt_call.opal_atomic_cmpset_acq_32
>> 00028ae0 t 0017.plt_call.opal_atomic_ll_64
>> 00027fe0 t 0017.plt_call.opal_atomic_mb
>> 00027d50 t 0017.plt_call.opal_atomic_rmb
>> 00028500 t 0017.plt_call.opal_atomic_sc_64
>> 00027670 t 0017.plt_call.opal_atomic_sub_32
>> 00026da0 t 0017.plt_call.opal_atomic_swap_64
>> 00027050 t 0017.plt_call.opal_atomic_wmb
>> 0005e6a0 t mca_base_pvar_is_atomic
>> 0004715c T opal_atomic_add_32
>> 0004703c T opal_atomic_cmpset_32
>> 000470e8 T opal_atomic_cmpset_64
>> 00047060 T opal_atomic_cmpset_acq_32
>> 0004710c T opal_atomic_cmpset_acq_64
>> 0002a610 t opal_atomic_cmpset_ptr
>> 00047094 T opal_atomic_cmpset_rel_32
>> 00047134 T opal_atomic_cmpset_rel_64
>> 00032cc0 t opal_atomic_init
>> 00033980 t opal_atomic_init
>> 000396a0 t opal_atomic_init
>>U opal_atomic_ll_64
>> 0002e460 t opal_atomic_lock
>> 00032cf0 t opal_atomic_lock
>> 000339b0 t opal_atomic_lock
>> 00047024 T opal_atomic_mb
>> 0004702c T opal_atomic_rmb
>>U opal_atomic_sc_64
>> 00047174 T opal_atomic_sub_32
>>U opal_atomic_swap_64
>> 0002e4e0 t opal_atomic_unlock
>> 00032d70 t opal_atomic_unlock
>> 00033a30 t opal_atomic_unlock
>>

Re: [OMPI devel] openmpi-2.0.0 - problems with ppc64, PGI and atomics

2016-09-01 Thread Jeff Squyres (jsquyres) 
Please send all the information on the build support page and open an issue at 
github.  Thanks.


> On Sep 1, 2016, at 3:41 PM, Vallee, Geoffroy R.  wrote:
> 
> This is indeed a little better but still creating a problem:
> 
>  CCLD opal_wrapper
> ../../../opal/.libs/libopen-pal.a(opal_progress.o): In function 
> `_opal_progress_unregister':
> /autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/runtime/opal_progress.c:459:
>  undefined reference to `opal_atomic_swap_64'
> ../../../opal/.libs/libopen-pal.a(opal_progress.o): In function 
> `_opal_progress_register':
> /autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/runtime/opal_progress.c:398:
>  undefined reference to `opal_atomic_swap_64'
> make[2]: *** [opal_wrapper] Error 2
> make[2]: Leaving directory 
> `/autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/tools/wrappers'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory 
> `/autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal'
> make: *** [all-recursive] Error 1
> 
> $ nm libopen-pal.a  | grep atomic
> U opal_atomic_cmpset_64
> 0ab0 t opal_atomic_cmpset_ptr
> U opal_atomic_wmb
> 0950 t opal_lifo_push_atomic
> U opal_atomic_cmpset_acq_32
> 03d0 t opal_atomic_lock
> 0450 t opal_atomic_unlock
> U opal_atomic_wmb
> U opal_atomic_ll_64
> U opal_atomic_sc_64
> U opal_atomic_wmb
> 1010 t opal_lifo_pop_atomic
> U opal_atomic_cmpset_acq_32
> 04b0 t opal_atomic_init
> 04e0 t opal_atomic_lock
> U opal_atomic_mb
> 0560 t opal_atomic_unlock
> U opal_atomic_wmb
> U opal_atomic_add_32
> U opal_atomic_cmpset_acq_32
> 0820 t opal_atomic_init
> 0850 t opal_atomic_lock
> U opal_atomic_sub_32
> U opal_atomic_swap_64
> 08d0 t opal_atomic_unlock
> U opal_atomic_wmb
> 0130 t opal_atomic_init
> atomic-asm.o:
> 0138 T opal_atomic_add_32
> 0018 T opal_atomic_cmpset_32
> 00c4 T opal_atomic_cmpset_64
> 003c T opal_atomic_cmpset_acq_32
> 00e8 T opal_atomic_cmpset_acq_64
> 0070 T opal_atomic_cmpset_rel_32
> 0110 T opal_atomic_cmpset_rel_64
>  T opal_atomic_mb
> 0008 T opal_atomic_rmb
> 0150 T opal_atomic_sub_32
> 0010 T opal_atomic_wmb
> 2280 t mca_base_pvar_is_atomic
> U opal_atomic_ll_64
> U opal_atomic_sc_64
> U opal_atomic_wmb
> 0900 t opal_lifo_pop_atomic
> 
>> On Sep 1, 2016, at 3:16 PM, Jeff Squyres (jsquyres)  
>> wrote:
>> 
>> Can you try the latest v2.0.1 nightly snapshot tarball?
>> 
>> 
>>> On Sep 1, 2016, at 2:56 PM, Vallee, Geoffroy R.  wrote:
>>> 
>>> Hello,
>>> 
>>> I get the following problem when we compile OpenMPI-2.0.0 (it seems to be 
>>> specific to 2.x; the problem did not appear with 1.10.x) with PGI:
>>> 
>>> CCLD opal_wrapper
>>> ../../../opal/.libs/libopen-pal.so: undefined reference to 
>>> `opal_atomic_sc_64'
>>> ../../../opal/.libs/libopen-pal.so: undefined reference to 
>>> `opal_atomic_ll_64'
>>> ../../../opal/.libs/libopen-pal.so: undefined reference to 
>>> `opal_atomic_swap_64'
>>> make[1]: *** [opal_wrapper] Error 2
>>> 
>>> It is a little for me to pin point the exact problem but i can see the 
>>> following:
>>> 
>>> $ nm ./.libs/libopen-pal.so | grep atomic
>>> 00026320 t 0017.plt_call.opal_atomic_add_32
>>> 00026250 t 0017.plt_call.opal_atomic_cmpset_32
>>> 00026780 t 0017.plt_call.opal_atomic_cmpset_64
>>> 000280c0 t 0017.plt_call.opal_atomic_cmpset_acq_32
>>> 00028ae0 t 0017.plt_call.opal_atomic_ll_64
>>> 00027fe0 t 0017.plt_call.opal_atomic_mb
>>> 00027d50 t 0017.plt_call.opal_atomic_rmb
>>> 00028500 t 0017.plt_call.opal_atomic_sc_64
>>> 00027670 t 0017.plt_call.opal_atomic_sub_32
>>> 00026da0 t 0017.plt_call.opal_atomic_swap_64
>>> 00027050 t 0017.plt_call.opal_atomic_wmb
>>> 0005e6a0 t mca_base_pvar_is_atomic
>>> 0004715c T opal_atomic_add_32
>>> 0004703c T opal_atomic_cmpset_32
>>> 000470e8 T opal_atomic_cmpset_64
>>> 00047060 T opal_atomic_cmpset_acq_32
>>> 0004710c T opal_atomic_cmpset_acq_64
>>> 0002a610 t opal_atomic_cmpset_ptr
>>> 00047094 T opal_atomic_cmpset_rel_32
>>> 00047134 T opal_atomic_cmpset_rel_64
>>> 00032cc0 t opal_atomic_init
>>> 00033980 t opal_atomic_init
>>> 000396a0 t opal_atomic_init
>>>   U opal_atomic_ll_64
>>> 0002e460 t opal_atomic_lock
>>> 00032cf0 t opal_atomic_lock
>>> 000339b0 t opal_atomic_

[OMPI devel] 2.0.1rc3 posted

2016-09-01 Thread Jeff Squyres (jsquyres) 
We're getting close.  Unless any showstoppers show up in the immediate future, 
we will likely be releasing this as 2.0.1:

rc3 tarballs here:

https://www.open-mpi.org/software/ompi/v2.0/

Changes since rc2:

- Fix COMM_SPAWN segv
- Fix yalla bandwidth issue
- Fix an OMPIO-related crash when using built-in datatypes
- Fix a Solaris alignment issue
- Fix a stdin problem
- Fix a bunch of typos and make other updates in README

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

[OMPI devel] PMIx shared memory dstore now off by default

2016-09-01 Thread r...@open-mpi.org 
Hi folks

In order to let some folks continue working on dynamic operations on the 
master, I have turned the PMIx shared memory data store support “off” by 
default for the embedded code. You can turn it “on” using the 
--enable-pmix3-dstore option.

Once the dynamics support is functional, we will reverse the default setting of 
that flag. Sorry for the disruption.
Ralph

___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] openmpi-2.0.0 - problems with ppc64, PGI and atomics

2016-09-01 Thread Paul Hargrove 
FWIW I have not seen problems when testing the 2.0.1rc2 w/ PGI versions
12.10, 13.9, 14.3 or 15.9.

I am going to test 2.0.2.rc3 ASAP and try to get PGI 16.4 coverage added in

-Paul

On Thu, Sep 1, 2016 at 12:48 PM, Jeff Squyres (jsquyres)  wrote:

> Please send all the information on the build support page and open an
> issue at github.  Thanks.
>
>
> > On Sep 1, 2016, at 3:41 PM, Vallee, Geoffroy R. 
> wrote:
> >
> > This is indeed a little better but still creating a problem:
> >
> >  CCLD opal_wrapper
> > ../../../opal/.libs/libopen-pal.a(opal_progress.o): In function
> `_opal_progress_unregister':
> > /autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/runtime/opal_progress.c:459:
> undefined reference to `opal_atomic_swap_64'
> > ../../../opal/.libs/libopen-pal.a(opal_progress.o): In function
> `_opal_progress_register':
> > /autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/runtime/opal_progress.c:398:
> undefined reference to `opal_atomic_swap_64'
> > make[2]: *** [opal_wrapper] Error 2
> > make[2]: Leaving directory `/autofs/nccs-svm1_sw/gvh/src/
> openmpi-2.0.1rc2/opal/tools/wrappers'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/autofs/nccs-svm1_sw/gvh/src/
> openmpi-2.0.1rc2/opal'
> > make: *** [all-recursive] Error 1
> >
> > $ nm libopen-pal.a  | grep atomic
> > U opal_atomic_cmpset_64
> > 0ab0 t opal_atomic_cmpset_ptr
> > U opal_atomic_wmb
> > 0950 t opal_lifo_push_atomic
> > U opal_atomic_cmpset_acq_32
> > 03d0 t opal_atomic_lock
> > 0450 t opal_atomic_unlock
> > U opal_atomic_wmb
> > U opal_atomic_ll_64
> > U opal_atomic_sc_64
> > U opal_atomic_wmb
> > 1010 t opal_lifo_pop_atomic
> > U opal_atomic_cmpset_acq_32
> > 04b0 t opal_atomic_init
> > 04e0 t opal_atomic_lock
> > U opal_atomic_mb
> > 0560 t opal_atomic_unlock
> > U opal_atomic_wmb
> > U opal_atomic_add_32
> > U opal_atomic_cmpset_acq_32
> > 0820 t opal_atomic_init
> > 0850 t opal_atomic_lock
> > U opal_atomic_sub_32
> > U opal_atomic_swap_64
> > 08d0 t opal_atomic_unlock
> > U opal_atomic_wmb
> > 0130 t opal_atomic_init
> > atomic-asm.o:
> > 0138 T opal_atomic_add_32
> > 0018 T opal_atomic_cmpset_32
> > 00c4 T opal_atomic_cmpset_64
> > 003c T opal_atomic_cmpset_acq_32
> > 00e8 T opal_atomic_cmpset_acq_64
> > 0070 T opal_atomic_cmpset_rel_32
> > 0110 T opal_atomic_cmpset_rel_64
> >  T opal_atomic_mb
> > 0008 T opal_atomic_rmb
> > 0150 T opal_atomic_sub_32
> > 0010 T opal_atomic_wmb
> > 2280 t mca_base_pvar_is_atomic
> > U opal_atomic_ll_64
> > U opal_atomic_sc_64
> > U opal_atomic_wmb
> > 0900 t opal_lifo_pop_atomic
> >
> >> On Sep 1, 2016, at 3:16 PM, Jeff Squyres (jsquyres) 
> wrote:
> >>
> >> Can you try the latest v2.0.1 nightly snapshot tarball?
> >>
> >>
> >>> On Sep 1, 2016, at 2:56 PM, Vallee, Geoffroy R. 
> wrote:
> >>>
> >>> Hello,
> >>>
> >>> I get the following problem when we compile OpenMPI-2.0.0 (it seems to
> be specific to 2.x; the problem did not appear with 1.10.x) with PGI:
> >>>
> >>> CCLD opal_wrapper
> >>> ../../../opal/.libs/libopen-pal.so: undefined reference to
> `opal_atomic_sc_64'
> >>> ../../../opal/.libs/libopen-pal.so: undefined reference to
> `opal_atomic_ll_64'
> >>> ../../../opal/.libs/libopen-pal.so: undefined reference to
> `opal_atomic_swap_64'
> >>> make[1]: *** [opal_wrapper] Error 2
> >>>
> >>> It is a little for me to pin point the exact problem but i can see the
> following:
> >>>
> >>> $ nm ./.libs/libopen-pal.so | grep atomic
> >>> 00026320 t 0017.plt_call.opal_atomic_add_32
> >>> 00026250 t 0017.plt_call.opal_atomic_cmpset_32
> >>> 00026780 t 0017.plt_call.opal_atomic_cmpset_64
> >>> 000280c0 t 0017.plt_call.opal_atomic_cmpset_acq_32
> >>> 00028ae0 t 0017.plt_call.opal_atomic_ll_64
> >>> 00027fe0 t 0017.plt_call.opal_atomic_mb
> >>> 00027d50 t 0017.plt_call.opal_atomic_rmb
> >>> 00028500 t 0017.plt_call.opal_atomic_sc_64
> >>> 00027670 t 0017.plt_call.opal_atomic_sub_32
> >>> 00026da0 t 0017.plt_call.opal_atomic_swap_64
> >>> 00027050 t 0017.plt_call.opal_atomic_wmb
> >>> 0005e6a0 t mca_base_pvar_is_atomic
> >>> 0004715c T opal_atomic_add_32
> >>> 0004703c T opal_atomic_cmpset_32
> >>> 000470e8 T opal_atomic_cmpset_64
> >>> 00047060 T opal_atomic_cmpset_acq_32
> >>> 0004710c T opal_atomic_cmpset_ac

Re: [OMPI devel] 2.0.1rc3 posted

2016-09-01 Thread Paul Hargrove 
On Thu, Sep 1, 2016 at 1:47 PM, Jeff Squyres (jsquyres) 
wrote:

> - Fix a Solaris alignment issue
>

If you mean the SIGBUS I reported that was Linux on SPARC h/w

-Paul


-- 
Paul H. Hargrove  phhargr...@lbl.gov
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] 2.0.1rc3 posted

2016-09-01 Thread Gilles Gouaillardet 

Paul,


I guess this was a typo, and you should either read

- Fix a SPARC alignment issue

or

- Fix an alignment issue on alignment sensitive processors such as SPARC


the patch i submitted to fix the issue you reported is definitely 
included in 2.0.1rc3



Cheers,


Gilles


On 9/2/2016 9:31 AM, Paul Hargrove wrote:


On Thu, Sep 1, 2016 at 1:47 PM, Jeff Squyres (jsquyres) 
mailto:jsquy...@cisco.com>> wrote:


- Fix a Solaris alignment issue


If you mean the SIGBUS I reported that was Linux on SPARC h/w

-Paul


--
Paul H. Hargrove phhargr...@lbl.gov 
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900


___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel


___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] 2.0.1rc3 posted

2016-09-01 Thread Paul Hargrove 
Giles,

Thanks for the clarification.
I have 2.0.1rc2 + patch running on the Linux/SPARC system, but it is still
many hours from finishing/
I hope to run 2.0.1rc3 there tomorrow.

-Paul

On Thu, Sep 1, 2016 at 5:42 PM, Gilles Gouaillardet 
wrote:

> Paul,
>
>
> I guess this was a typo, and you should either read
>
> - Fix a SPARC alignment issue
>
> or
>
> - Fix an alignment issue on alignment sensitive processors such as SPARC
>
>
> the patch i submitted to fix the issue you reported is definitely included
> in 2.0.1rc3
>
>
> Cheers,
>
>
> Gilles
>
> On 9/2/2016 9:31 AM, Paul Hargrove wrote:
>
>
> On Thu, Sep 1, 2016 at 1:47 PM, Jeff Squyres (jsquyres) <
> jsquy...@cisco.com> wrote:
>
>> - Fix a Solaris alignment issue
>>
>
> If you mean the SIGBUS I reported that was Linux on SPARC h/w
>
> -Paul
>
>
> --
> Paul H. Hargrove  phhargr...@lbl.gov
> Computer Languages & Systems Software (CLaSS) Group
> Computer Science Department   Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>
>
> ___
> devel mailing 
> listde...@lists.open-mpi.orghttps://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>
>
>
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>



-- 
Paul H. Hargrove  phhargr...@lbl.gov
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] openmpi-2.0.0 - problems with ppc64, PGI and atomics

2016-09-01 Thread Vallee, Geoffroy R. 
Interesting, I am having the problem with both 16.5 and 16.7.

My 2 cents,

> On Sep 1, 2016, at 8:25 PM, Paul Hargrove  wrote:
> 
> FWIW I have not seen problems when testing the 2.0.1rc2 w/ PGI versions 
> 12.10, 13.9, 14.3 or 15.9.
> 
> I am going to test 2.0.2.rc3 ASAP and try to get PGI 16.4 coverage added in
> 
> -Paul
> 
> On Thu, Sep 1, 2016 at 12:48 PM, Jeff Squyres (jsquyres)  
> wrote:
> Please send all the information on the build support page and open an issue 
> at github.  Thanks.
> 
> 
> > On Sep 1, 2016, at 3:41 PM, Vallee, Geoffroy R.  wrote:
> >
> > This is indeed a little better but still creating a problem:
> >
> >  CCLD opal_wrapper
> > ../../../opal/.libs/libopen-pal.a(opal_progress.o): In function 
> > `_opal_progress_unregister':
> > /autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/runtime/opal_progress.c:459:
> >  undefined reference to `opal_atomic_swap_64'
> > ../../../opal/.libs/libopen-pal.a(opal_progress.o): In function 
> > `_opal_progress_register':
> > /autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/runtime/opal_progress.c:398:
> >  undefined reference to `opal_atomic_swap_64'
> > make[2]: *** [opal_wrapper] Error 2
> > make[2]: Leaving directory 
> > `/autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/tools/wrappers'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory 
> > `/autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal'
> > make: *** [all-recursive] Error 1
> >
> > $ nm libopen-pal.a  | grep atomic
> > U opal_atomic_cmpset_64
> > 0ab0 t opal_atomic_cmpset_ptr
> > U opal_atomic_wmb
> > 0950 t opal_lifo_push_atomic
> > U opal_atomic_cmpset_acq_32
> > 03d0 t opal_atomic_lock
> > 0450 t opal_atomic_unlock
> > U opal_atomic_wmb
> > U opal_atomic_ll_64
> > U opal_atomic_sc_64
> > U opal_atomic_wmb
> > 1010 t opal_lifo_pop_atomic
> > U opal_atomic_cmpset_acq_32
> > 04b0 t opal_atomic_init
> > 04e0 t opal_atomic_lock
> > U opal_atomic_mb
> > 0560 t opal_atomic_unlock
> > U opal_atomic_wmb
> > U opal_atomic_add_32
> > U opal_atomic_cmpset_acq_32
> > 0820 t opal_atomic_init
> > 0850 t opal_atomic_lock
> > U opal_atomic_sub_32
> > U opal_atomic_swap_64
> > 08d0 t opal_atomic_unlock
> > U opal_atomic_wmb
> > 0130 t opal_atomic_init
> > atomic-asm.o:
> > 0138 T opal_atomic_add_32
> > 0018 T opal_atomic_cmpset_32
> > 00c4 T opal_atomic_cmpset_64
> > 003c T opal_atomic_cmpset_acq_32
> > 00e8 T opal_atomic_cmpset_acq_64
> > 0070 T opal_atomic_cmpset_rel_32
> > 0110 T opal_atomic_cmpset_rel_64
> >  T opal_atomic_mb
> > 0008 T opal_atomic_rmb
> > 0150 T opal_atomic_sub_32
> > 0010 T opal_atomic_wmb
> > 2280 t mca_base_pvar_is_atomic
> > U opal_atomic_ll_64
> > U opal_atomic_sc_64
> > U opal_atomic_wmb
> > 0900 t opal_lifo_pop_atomic
> >
> >> On Sep 1, 2016, at 3:16 PM, Jeff Squyres (jsquyres)  
> >> wrote:
> >>
> >> Can you try the latest v2.0.1 nightly snapshot tarball?
> >>
> >>
> >>> On Sep 1, 2016, at 2:56 PM, Vallee, Geoffroy R.  wrote:
> >>>
> >>> Hello,
> >>>
> >>> I get the following problem when we compile OpenMPI-2.0.0 (it seems to be 
> >>> specific to 2.x; the problem did not appear with 1.10.x) with PGI:
> >>>
> >>> CCLD opal_wrapper
> >>> ../../../opal/.libs/libopen-pal.so: undefined reference to 
> >>> `opal_atomic_sc_64'
> >>> ../../../opal/.libs/libopen-pal.so: undefined reference to 
> >>> `opal_atomic_ll_64'
> >>> ../../../opal/.libs/libopen-pal.so: undefined reference to 
> >>> `opal_atomic_swap_64'
> >>> make[1]: *** [opal_wrapper] Error 2
> >>>
> >>> It is a little for me to pin point the exact problem but i can see the 
> >>> following:
> >>>
> >>> $ nm ./.libs/libopen-pal.so | grep atomic
> >>> 00026320 t 0017.plt_call.opal_atomic_add_32
> >>> 00026250 t 0017.plt_call.opal_atomic_cmpset_32
> >>> 00026780 t 0017.plt_call.opal_atomic_cmpset_64
> >>> 000280c0 t 0017.plt_call.opal_atomic_cmpset_acq_32
> >>> 00028ae0 t 0017.plt_call.opal_atomic_ll_64
> >>> 00027fe0 t 0017.plt_call.opal_atomic_mb
> >>> 00027d50 t 0017.plt_call.opal_atomic_rmb
> >>> 00028500 t 0017.plt_call.opal_atomic_sc_64
> >>> 00027670 t 0017.plt_call.opal_atomic_sub_32
> >>> 00026da0 t 0017.plt_call.opal_atomic_swap_64
> >>> 00027050 t 0017.plt_call.opal_atomic_wmb
> >>> 0005e6a0 t mca_base_pvar_is_atomic
> >>> 0004715c T opal_atomic_add_

Re: [OMPI devel] openmpi-2.0.0 - problems with ppc64, PGI and atomics

2016-09-01 Thread Paul Hargrove 
I failed to get PGI 16.x working at all (licence issue, I think).
So, I can neither confirm nor refute Geoffroy's reported problems.

-Paul

On Thu, Sep 1, 2016 at 6:15 PM, Vallee, Geoffroy R. 
wrote:

> Interesting, I am having the problem with both 16.5 and 16.7.
>
> My 2 cents,
>
> > On Sep 1, 2016, at 8:25 PM, Paul Hargrove  wrote:
> >
> > FWIW I have not seen problems when testing the 2.0.1rc2 w/ PGI versions
> 12.10, 13.9, 14.3 or 15.9.
> >
> > I am going to test 2.0.2.rc3 ASAP and try to get PGI 16.4 coverage added
> in
> >
> > -Paul
> >
> > On Thu, Sep 1, 2016 at 12:48 PM, Jeff Squyres (jsquyres) <
> jsquy...@cisco.com> wrote:
> > Please send all the information on the build support page and open an
> issue at github.  Thanks.
> >
> >
> > > On Sep 1, 2016, at 3:41 PM, Vallee, Geoffroy R. 
> wrote:
> > >
> > > This is indeed a little better but still creating a problem:
> > >
> > >  CCLD opal_wrapper
> > > ../../../opal/.libs/libopen-pal.a(opal_progress.o): In function
> `_opal_progress_unregister':
> > > /autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/runtime/opal_progress.c:459:
> undefined reference to `opal_atomic_swap_64'
> > > ../../../opal/.libs/libopen-pal.a(opal_progress.o): In function
> `_opal_progress_register':
> > > /autofs/nccs-svm1_sw/gvh/src/openmpi-2.0.1rc2/opal/runtime/opal_progress.c:398:
> undefined reference to `opal_atomic_swap_64'
> > > make[2]: *** [opal_wrapper] Error 2
> > > make[2]: Leaving directory `/autofs/nccs-svm1_sw/gvh/src/
> openmpi-2.0.1rc2/opal/tools/wrappers'
> > > make[1]: *** [all-recursive] Error 1
> > > make[1]: Leaving directory `/autofs/nccs-svm1_sw/gvh/src/
> openmpi-2.0.1rc2/opal'
> > > make: *** [all-recursive] Error 1
> > >
> > > $ nm libopen-pal.a  | grep atomic
> > > U opal_atomic_cmpset_64
> > > 0ab0 t opal_atomic_cmpset_ptr
> > > U opal_atomic_wmb
> > > 0950 t opal_lifo_push_atomic
> > > U opal_atomic_cmpset_acq_32
> > > 03d0 t opal_atomic_lock
> > > 0450 t opal_atomic_unlock
> > > U opal_atomic_wmb
> > > U opal_atomic_ll_64
> > > U opal_atomic_sc_64
> > > U opal_atomic_wmb
> > > 1010 t opal_lifo_pop_atomic
> > > U opal_atomic_cmpset_acq_32
> > > 04b0 t opal_atomic_init
> > > 04e0 t opal_atomic_lock
> > > U opal_atomic_mb
> > > 0560 t opal_atomic_unlock
> > > U opal_atomic_wmb
> > > U opal_atomic_add_32
> > > U opal_atomic_cmpset_acq_32
> > > 0820 t opal_atomic_init
> > > 0850 t opal_atomic_lock
> > > U opal_atomic_sub_32
> > > U opal_atomic_swap_64
> > > 08d0 t opal_atomic_unlock
> > > U opal_atomic_wmb
> > > 0130 t opal_atomic_init
> > > atomic-asm.o:
> > > 0138 T opal_atomic_add_32
> > > 0018 T opal_atomic_cmpset_32
> > > 00c4 T opal_atomic_cmpset_64
> > > 003c T opal_atomic_cmpset_acq_32
> > > 00e8 T opal_atomic_cmpset_acq_64
> > > 0070 T opal_atomic_cmpset_rel_32
> > > 0110 T opal_atomic_cmpset_rel_64
> > >  T opal_atomic_mb
> > > 0008 T opal_atomic_rmb
> > > 0150 T opal_atomic_sub_32
> > > 0010 T opal_atomic_wmb
> > > 2280 t mca_base_pvar_is_atomic
> > > U opal_atomic_ll_64
> > > U opal_atomic_sc_64
> > > U opal_atomic_wmb
> > > 0900 t opal_lifo_pop_atomic
> > >
> > >> On Sep 1, 2016, at 3:16 PM, Jeff Squyres (jsquyres) <
> jsquy...@cisco.com> wrote:
> > >>
> > >> Can you try the latest v2.0.1 nightly snapshot tarball?
> > >>
> > >>
> > >>> On Sep 1, 2016, at 2:56 PM, Vallee, Geoffroy R. 
> wrote:
> > >>>
> > >>> Hello,
> > >>>
> > >>> I get the following problem when we compile OpenMPI-2.0.0 (it seems
> to be specific to 2.x; the problem did not appear with 1.10.x) with PGI:
> > >>>
> > >>> CCLD opal_wrapper
> > >>> ../../../opal/.libs/libopen-pal.so: undefined reference to
> `opal_atomic_sc_64'
> > >>> ../../../opal/.libs/libopen-pal.so: undefined reference to
> `opal_atomic_ll_64'
> > >>> ../../../opal/.libs/libopen-pal.so: undefined reference to
> `opal_atomic_swap_64'
> > >>> make[1]: *** [opal_wrapper] Error 2
> > >>>
> > >>> It is a little for me to pin point the exact problem but i can see
> the following:
> > >>>
> > >>> $ nm ./.libs/libopen-pal.so | grep atomic
> > >>> 00026320 t 0017.plt_call.opal_atomic_add_32
> > >>> 00026250 t 0017.plt_call.opal_atomic_cmpset_32
> > >>> 00026780 t 0017.plt_call.opal_atomic_cmpset_64
> > >>> 000280c0 t 0017.plt_call.opal_atomic_cmpset_acq_32
> > >>> 00028ae0 t 0017.plt_call.opal_atomic_ll_64
> > >>> 00027fe0 t 0017.plt_call.opal_atom

Re: [OMPI devel] PMIx shared memory dstore now off by default

2016-09-01 Thread Gilles Gouaillardet 

Thanks Ralph,


as a direct consequence, Open MPI can now be built again on Solaris an 
other OS that does not support flock()



Cheers,


Gilles


On 9/2/2016 6:48 AM, r...@open-mpi.org wrote:

Hi folks

In order to let some folks continue working on dynamic operations on the 
master, I have turned the PMIx shared memory data store support “off” by 
default for the embedded code. You can turn it “on” using the 
--enable-pmix3-dstore option.

Once the dynamics support is functional, we will reverse the default setting of 
that flag. Sorry for the disruption.
Ralph

___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel


___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

[OMPI devel] [2.0.1rc3] OpenBSD 6.0 patcher failure

2016-09-01 Thread Paul Hargrove 
The OpenBSD 6.0 release was announced slightly under 12 hours before Jeff
announced the Open MPI 2.0.1rc3 tarball.
So, I just *had* to try them out together.

First, let me say that I have no expectation that the following issue be
fixed for 2.0.1, but hopefully before 2.2.

It appears that abort() is being called from mprotect() when called from
the patcher code.
This is very likely to be because the call asks for RWX, but by default
OpenBSD-6.0 *prohibits* W+X.
To allow both Write and eXec requires *both* a linker flag
(-Wl,-z,wxneeded) and that the executable be on an f/s mounted with the
"wxallowed" option.
Manually working to satisfy those conditions allows "make check" and ring_c
to run w/o failures.

-Paul


$ gdb .libs/dlopen_test dlopen_test.core
GNU gdb 6.3
[...]
This GDB was configured as "amd64-unknown-openbsd6.0"...
Core was generated by `dlopen_test'.
Program terminated with signal 6, Aborted.
[...]
#0  0x0b726a6cf44a in mprotect () at :2
2   : No such file or directory.
in 
(gdb) where
#0  0x0b726a6cf44a in mprotect () at :2
#1  0x0b72813d5943 in ModifyMemoryProtection (addr=12586039598736,
length=4096, prot=7)
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/opal/mca/patcher/base/patcher_base_patch.c:127
#2  0x0b72813d59aa in apply_patch (patch_data=0xb728e72fe60
"I▒▒-=\201r\v", address=12586039598736,
data_size=13)
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/opal/mca/patcher/base/patcher_base_patch.c:135
#3  0x0b72813d5a49 in mca_base_patcher_patch_apply_binary
(patch=0xb728e72fe00)
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/opal/mca/patcher/base/patcher_base_patch.c:152
#4  0x0b7340474f73 in mca_patcher_overwrite_apply_patch
(patch=0xb728e72fe00)
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/opal/mca/patcher/overwrite/patcher_overwrite_module.c:151
#5  0x0b7340474ff3 in mca_patcher_overwrite_patch_address
(sys_addr=12586039598736,
hook_addr=12586422447608)
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/opal/mca/patcher/overwrite/patcher_overwrite_module.c:255
#6  0x0b73404753f3 in mca_patcher_overwrite_patch_symbol
(func_symbol_name=0xb728150038f "munmap",
func_new_addr=12586422447608, func_old_addr=0xb7281827ed8)
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/opal/mca/patcher/overwrite/patcher_overwrite_module.c:301
#7  0x0b72813d301c in patcher_open ()
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/opal/mca/memory/patcher/memory_patcher_component.c:442
#8  0x0b728136f87d in open_components (framework=0xb72818240c0)
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/opal/mca/base/mca_base_components_open.c:117
#9  0x0b728136f7a0 in mca_base_framework_components_open
(framework=0xb72818240c0,
flags=MCA_BASE_OPEN_DEFAULT)
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/opal/mca/base/mca_base_components_open.c:65
#10 0x0b72813d2bab in opal_memory_base_open
(flags=MCA_BASE_OPEN_DEFAULT)
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/opal/mca/memory/base/memory_base_open.c:137
#11 0x0b7281370aad in mca_base_framework_open (framework=0xb72818240c0,
flags=MCA_BASE_OPEN_DEFAULT)
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/opal/mca/base/mca_base_framework.c:174
#12 0x0b728133e39d in opal_init (pargc=0x7f7c9ffc,
pargv=0x7f7c9ff0)
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/opal/runtime/opal_init.c:459
#13 0x0b70441012d3 in main (argc=1, argv=0x7f7ca068)
at
/home/phargrov/OMPI/openmpi-2.0.1rc3-openbsd6-amd64/openmpi-2.0.1rc3/ompi/debuggers/dlopen_test.c:134




-- 
Paul H. Hargrove  phhargr...@lbl.gov
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel