On Feb 6, 2014, at 2:32 PM, Ross Boylan wrote:
> Yes. And it seems the recommended one for this purpose is 1.7, not 1.6.
1.7.4 is our newest feature series release. 1.6.5 is the most recent
super-stable release.
We should be rolling 1.7.x to 1.8 within a few months.
> What should happen if
On Feb 6, 2014, at 11:32 AM, Ross Boylan wrote:
> On 2/6/2014 11:08 AM, Jeff Squyres (jsquyres) wrote:
>> In addition to what Ralph said (just install OMPI under your $HOME, at least
>> for testing purposes), here's what we say about version compatibility:
>>
>> 1. OMPI started providing ABI g
On 2/6/2014 11:08 AM, Jeff Squyres (jsquyres) wrote:
In addition to what Ralph said (just install OMPI under your $HOME, at least
for testing purposes), here's what we say about version compatibility:
1. OMPI started providing ABI guarantees with v1.3.2. The ABI guarantee we
provide is that a
In addition to what Ralph said (just install OMPI under your $HOME, at least
for testing purposes), here's what we say about version compatibility:
1. OMPI started providing ABI guarantees with v1.3.2. The ABI guarantee we
provide is that a 1.x and 1.(x+1) series will be ABI compatible, where x
One thing commonly done in this situation is for a user to simply download the
OMPI tarball and install it in their own home directory, then link R etc to the
updated version. This avoids impacting everyone else on the system and is a
low-risk way of trying to see if the update fixes the problem
On 2/6/2014 3:24 AM, Jeff Squyres (jsquyres) wrote:
Have you tried upgrading to a newer version of Open MPI? The 1.4.x series is
several generations old. Open MPI 1.7.4 was just released yesterday.
It's on a cluster running Debian squeeze, with perhaps some upgrades to
wheezy coming. However
Have you tried upgrading to a newer version of Open MPI? The 1.4.x series is
several generations old. Open MPI 1.7.4 was just released yesterday.
On Feb 5, 2014, at 9:58 PM, Ross Boylan wrote:
> On 1/31/2014 1:08 PM, Ross Boylan wrote:
>> I am getting the following error, amidst many success
On 1/31/2014 1:08 PM, Ross Boylan wrote:
I am getting the following error, amidst many successful message sends:
[n10][[50048,1],1][../../../../../../ompi/mca/btl/tcp/btl_tcp_frag.c:118:mca_btl_tcp_frag_send]
mca_btl_tcp_frag_send: writev error (0x7f6155970038, 578659815)
Bad address(1)
Am 31.01.2014 um 22:08 schrieb Ross Boylan:
> I am getting the following error, amidst many successful message sends:
> [n10][[50048,1],1][../../../../../../ompi/mca/btl/tcp/btl_tcp_frag.c:118:mca_btl_tcp_frag_send]
> mca_btl_tcp_frag_send: writev error (0x7f6155970038, 578659815)
> Bad a
I am getting the following error, amidst many successful message sends:
[n10][[50048,1],1][../../../../../../ompi/mca/btl/tcp/btl_tcp_frag.c:118:mca_btl_tcp_frag_send]
mca_btl_tcp_frag_send: writev error (0x7f6155970038, 578659815)
Bad address(1)
Any ideas about what is going on or what
10 matches
Mail list logo
