On Wed, 26 Mar 2014 10:47:56 +1100
Jonathan Mynard <[email protected]> wrote:

> I am a novice user and have this exact problem on a cluster.  How do
> I apply the patch?

Patching the installation directly:

$ cd `python -c"import instant; print instant.__path__[0]"`
$ patch -p2 < ofed-fork.patch

Note that if you install from source, triggering the installation again
may overwrite the patch. So you may similarly patch your source files.

Jan

> 
> Thanks.
> 
> Jonathan.
> 
> On 26/03/2014, at 1:24 AM, <[email protected]> wrote:
> 
> > After some digging, it seems that segfaults observed on
> > OFED/InfiniBand clusters (see [1], [2], [3]) are caused by
> > implementation of
> > 
> >  subprocess.Popen
> > 
> > Check your local subprocess.py:_execute_child. Parent does not seem
> > to keep hands of memory between fork() and exec() (as required [4],
> > [5]), especially as it is fiddling with garbage collector.
> > 
> > I tried switching to os.system (posix implementation in [6])
> > instead of subprocess.Popen and it seems promising. Check out [7]
> > or enclosed patch.
> > 
> > Jan
> > 
> > [1] https://answers.launchpad.net/dolfin/+question/219270
> > [2] https://answers.launchpad.net/dolfin/+question/225946
> > [3] http://fenicsproject.org/pipermail/fenics/2013-June/000398.html
> > [4] https://www.open-mpi.org/faq/?category=openfabrics#ofa-fork
> > [5]
> > http://www.openfabrics.org/downloads/OFED/release_notes/OFED_3.12_rc1_release_notes#3.03
> > [6]
> > http://svn.python.org/projects/python/trunk/Modules/posixmodule.c
> > [7] https://bitbucket.org/blechta/instant/branch/blechta/ofed-fork
> > 
> 
> 
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud
> service. For more information please visit
> http://www.symanteccloud.com
> ______________________________________________________________________

_______________________________________________
fenics mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics

Reply via email to