maybe I shouldn't have opened my mouth, mixing libraries doesn't
necessarily explain the more than 4 procs thing... unless when you run
with 4 procs they are being scheduled to the same node, and running with
more causes another node to come into the mix.
How are process being assigned to nodes?
burlen wrote:
Also, make sure you PV configuration uses the opengl and osmesa from
your build. To make it easy I always run ccmake the first time with
these options on the command line:
-DVTK_OPENGL_HAS_OSMESA=ON
-DOPENGL_INCLUDE_DIR=/u/burlen/apps/Mesa-7.5.1-Intel/include
-DOPENGL_gl_LIBRARY=/u/burlen/apps/Mesa-7.5.1-Intel/lib64/libGL.so
-DOPENGL_glu_LIBRARY=/u/burlen/apps/Mesa-7.5.1-Intel/lib64/libGLU.so
-DOPENGL_xmesa_INCLUDE_DIR=/u/burlen/apps/Mesa-7.5.1-Intel/include
-DOSMESA_INCLUDE_DIR=/u/burlen/apps/Mesa-7.5.1-Intel/include
-DOSMESA_LIBRARY=/u/burlen/apps/Mesa-7.5.1-Intel/lib64/libOSMesa.so
that mitigates some of the configuration pain.
burlen wrote:
Getting the exact same OSMesa setup as someone who has this working
on many processors could help to confirm this.
A possibility is that when run on the compute nodes open gl libraries
other than the one you expect are used. That can cause a strange
crash. I have seen it before. If you're not doing it, prepend your
mesa path to LD_LIBRARY_PATH before you launch pvserver.
I always used OSMesa configured with mesa configs. eg. "make linux",
installed in my home directory, as long as I set LD_LIBRARY_PATH I
never have had any troubles.
Hope it helps
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
