Re: [OMPI devel] possible bug in 1.3.2 sm transport

2009-07-14 Thread Bryan Lally
Developers, I was about to test 1.3.3rc2, then I saw that 1.3.3 had also escaped. I tried it, and voila! It solves the issue I reported in May, below. Thanks for all the work that went into this. - Bryan -- Bryan Lally, la...@lanl.gov 505.667.9954 CCS-2 Los Alamos National

Re: [OMPI devel] sm BTL flow management

2009-06-24 Thread Bryan Lally
Ralph Castain wrote: Be happy to put it through the wringer... :-) My wringer is available, too. - Bryan -- Bryan Lally, la...@lanl.gov 505.667.9954 CCS-2 Los Alamos National Laboratory Los Alamos, New Mexico

Re: [OMPI devel] Hang in collectives involving shared memory

2009-06-16 Thread Bryan Lally
C translation of Ralph's reproducer as well. - Bryan -- Bryan Lally, la...@lanl.gov 505.667.9954 CCS-2 Los Alamos National Laboratory Los Alamos, New Mexico

Re: [OMPI devel] Hang in collectives involving shared memory

2009-06-16 Thread Bryan Lally
9.x86_64). I don't think it's just the one machine and it's configuration. - Bryan -- Bryan Lally, la...@lanl.gov 505.667.9954 CCS-2 Los Alamos National Laboratory Los Alamos, New Mexico Developers, This is my first post to the openmpi developers list. I think I'

Re: [OMPI devel] possible bug in 1.3.2 sm transport

2009-05-19 Thread Bryan Lally
Bryan Lally wrote: Here's what we've found. It wasn't the platform file as such. I've since built with ./configure and some standard, obvious command line switches. What's then required is to edit the platform configuration file, /etc/openmpi-mca-params.conf and add

Re: [OMPI devel] possible bug in 1.3.2 sm transport

2009-05-19 Thread Bryan Lally
Jeff Squyres wrote: On May 18, 2009, at 11:49 PM, Bryan Lally wrote: Ralph sent me a platform file and a corresponding .conf file. I built ompi from openmpi-1.3.3a1r21223.tar.gz, with these files. I've been running my normal tests and have been unable to hang a job yet. I've run e

Re: [OMPI devel] possible bug in 1.3.2 sm transport

2009-05-18 Thread Bryan Lally
the application side) were 4 bytes. There were only 4 processes involved. - Bryan -- Bryan Lally, la...@lanl.gov 505.667.9954 CCS-2 Los Alamos National Laboratory Los Alamos, New Mexico

Re: [OMPI devel] possible bug in 1.3.2 sm transport

2009-05-18 Thread Bryan Lally
e the problem first showed up. I'll report more as soon as I know more. Hopefully in the morning. - Bryan -- Bryan Lally, la...@lanl.gov 505.667.9954 CCS-2 Los Alamos National Laboratory Los Alamos, New Mexico

Re: [OMPI devel] Build failures on trunk? r21235

2009-05-14 Thread Bryan Lally
it. This is a very stock OS X box. Apple's tools, including gcc (4.0.1), libtool and the linker. - Bryan -- Bryan Lally, la...@lanl.gov 505.667.9954 CCS-2 Los Alamos National Laboratory Los Alamos, New Mexico

Re: [OMPI devel] Build failures on trunk? r21235

2009-05-14 Thread Bryan Lally
ers. This was with the native Leopard compilers. - Bryan -- Bryan Lally, la...@lanl.gov 505.667.9954 CCS-2 Los Alamos National Laboratory Los Alamos, New Mexico

Re: [OMPI devel] Build failures on trunk? r21235

2009-05-14 Thread Bryan Lally
Argh. This time with attachment attached ... Bryan Lally wrote: While we're talking about build failures ... I haven't been able to build any of the 1.3.x releases on my OS X machines. OS X 10.5.6 (Leopard) on Intel macs. Attached is the configure command and the failure from la

Re: [OMPI devel] Build failures on trunk? r21235

2009-05-14 Thread Bryan Lally
. 1.2.x builds fine. - Bryan -- Bryan Lally, la...@lanl.gov 505.667.9954 CCS-2 Los Alamos National Laboratory Los Alamos, New Mexico

Re: [OMPI devel] possible bug in 1.3.2 sm transport

2009-05-11 Thread Bryan Lally
ora 9. The application code was built with that and NAG's fortran, and in another test with Pathscale's C and Fortran. We're only using the C bindings to OMPI, never the Fortran bindings. - Bryan -- Bryan Lally, la...@lanl.gov 505.667.9954 CCS-2 Los Alamos National Labora

[OMPI devel] possible bug in 1.3.2 sm transport

2009-05-11 Thread Bryan Lally
hing like this before? If not, what do we do next? Thanks. - Bryan -- Bryan Lally, la...@lanl.gov 505.667.9954 CCS-2 Los Alamos National Laboratory Los Alamos, New Mexico