[gpaw-users] Segfaults when testing gpaw-python
Hildur Guðmundsdóttir
hildur.gud at gmail.com
Thu Mar 21 12:21:00 CET 2013
Good morning
I am trying to install GPAW on the NHPC cluster
(http://nhpc.hi.is/content/hardware) and when running the tests with
gpaw-python they stop on the fourth test, due to segmentation faults.
This happens for numpy_zdotc_graphite.py, eigh.py and blas.py and no
doubt others too. I do not get any output, the tests just stop
running.
When doing for instance:
mpirun -np 2 gpaw-python gpaw/test/blas.py
I get
--------------------------------------------------------------------------
mpirun noticed that process rank 1 with PID 11048 on node
gardar-1.local exited on signal 11 (Segmentation fault).
--------------------------------------------------------------------------
I have compiled numpy and GPAW with gcc using the same mkl libraries
for blas and lapack ('mkl_blas95_lp64', 'mkl_lapack95_lp64'). I'm
using python2.7, numpy1.7.0, openmpi-1.4.4 and gpaw 0.9.0-8965. First
I installed with the system provided numpy and got the same problem.
Attached is my customize.py
I saw this has happened to others before but couldn't find a solution
for the problem, I would appreciate any advice.
Thanks in advance,
Hildur
-------------- next part --------------
A non-text attachment was scrubbed...
Name: customize.py
Type: application/octet-stream
Size: 1577 bytes
Desc: not available
Url : http://listserv.fysik.dtu.dk/pipermail/gpaw-users/attachments/20130321/c0485af0/attachment.obj
More information about the gpaw-users
mailing list