[Paraview] Paraview v3.10.1/0 segmentation fault with MPI and MESA support on.

Tue Apr 19 03:48:56 EDT 2011

Sorry but I did not set it up. somebody from SGI set it up for us.

But he did mention that there was problems related to messa and said that
the combination he is putting works well. With other messa he also had
problems.

This is the set he said that works well together:

ParaView-3.10.0.tar.gz
ParaView-3.10.0-Linux-x86_64.tar.gz
boost_1_40_0.tar.gz
cmake-2.8.3.tar.gz
MesaGLUT-7.7.1.tar.gz
MesaLib-7.7.1.tar.gz
openmpi-1.4.3.tar.gz
Python-2.7.1.tar
qt-everywhere-opensource-src-4.6.3.tar.gz

So this is what i am using.

Sorry, i could not be much help.

Take care
Arjun

>差出人 : "Albina, Frank" <frank.albina at sauber-motorsport.com>
>宛先 : Arjun Yadav <y-arjun.az at srigroup.co.jp>
>件名 : RE: [Paraview] Paraview v3.10.1/0 segmentation fault with MPI and
MESA support on.
>送信日時 : 2011/04/19 15:59:03
>
>Hi Arjun!
>
>Thanks for the info. I tried this one too, but it does not work either.
Just to be sure, I rebuilt it from scratch and I am having a different
issue (Illegal instruction instead of segmentation fault), but at the same
place:
>
>[...]
>#0  0x0000000000b14f90 in ?? ()
>#1  0x00002aaab68640b7 in vtkOpenGLRenderWindow::OpenGLInit
(this=0x1501cc0) at /scratch/fal/COMPILE/ParaView-3.10.1
/src/VTK/Rendering/vtkOpenGLRenderWindow.cxx:241
>#2  0x00002aaab68c18c1 in vtkXOpenGLRenderWindow::WindowInitialize
(this=0x1501cc0) at /scratch/fal/COMPILE/ParaView-3.10.1
/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1043
>#3  0x00002aaab68c1907 in vtkXOpenGLRenderWindow::Initialize
(this=0x1501cc0) at /scratch/fal/COMPILE/ParaView-3.10.1
/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1052
>#4  0x00002aaab68c1dbb in vtkXOpenGLRenderWindow::Start (this=0x1501cc0)
at /scratch/fal/COMPILE/ParaView-3.10.1
/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1185
>#5  0x00002aaab677ae0d in vtkRenderWindow::DoStereoRender (this=0x1501cc0)
at /scratch/fal/COMPILE/ParaView-3.10.1
/src/VTK/Rendering/vtkRenderWindow.cxx:687
>#6  0x00002aaab677adde in vtkRenderWindow::DoFDRender (this=0x1501cc0) at
/scratch/fal/COMPILE/ParaView-3.10.1
/src/VTK/Rendering/vtkRenderWindow.cxx:676
>#7  0x00002aaab677a873 in vtkRenderWindow::DoAARender (this=0x1501cc0) at
/scratch/fal/COMPILE/ParaView-3.10.1
/src/VTK/Rendering/vtkRenderWindow.cxx:563
>#8  0x00002aaab6779e22 in vtkRenderWindow::Render (this=0x1501cc0) at
/scratch/fal/COMPILE/ParaView-3.10.1
/src/VTK/Rendering/vtkRenderWindow.cxx:376
>#9  0x00002aaab68c4755 in vtkXOpenGLRenderWindow::Render (this=0x1501cc0)
at /scratch/fal/COMPILE/ParaView-3.10.1
/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1845
>#10 0x00002aaaaddf7a2d in vtkPVRenderView::Render (this=0x14758b0,
interactive=false, skip_rendering=false) at
/scratch/fal/COMPILE/ParaView-3.10.1
/src/Servers/Filters/vtkPVRenderView.cxx:752
>#11 0x00002aaaaddf72b7 in vtkPVRenderView::StillRender (this=0x14758b0) at
/scratch/fal/COMPILE/ParaView-3.10.1
/src/Servers/Filters/vtkPVRenderView.cxx:592
>#12 0x00002aaaad75837e in vtkPVRenderViewCommand (arlu=0xcafee0,
ob=0x14758b0, method=0x155b2c9 "StillRender", msg=@0x7fffffff8a20,
resultStream=@0xce6900)
>[...]
>
>So I guess that your configuration differs from mine. Do you have by
chance an excerpt of your CMakeCache.txt file in your build directory
showing which settings you are using for OpenGL, when running MESA instead
of GPU rendering?
>
>For comparison, here are mine (which do not work):
>OPENGL_INCLUDE_DIR:PATH=/code/CFD/develop/opt/share/Mesa-7.7.1/include
>OPENGL_gl_LIBRARY:FILEPATH=/code/CFD/develop/opt/share/Mesa-7.7.1
/lib/libGL.so
>OPENGL_glu_LIBRARY:FILEPATH=/code/CFD/develop/opt/share/Mesa-7.7.1
/lib/libGLU.so
>OPENGL_xmesa_INCLUDE_DIR:PATH=/code/CFD/develop/opt/share/Mesa-7.7.1
/include
>OSMESA_INCLUDE_DIR:PATH=/code/CFD/develop/opt/share/Mesa-7.7.1/include
>OSMESA_LIBRARY:FILEPATH=/code/CFD/develop/opt/share/Mesa-7.7.1
/lib/libOSMesa.so
>VTK_USE_X:BOOL=ON
>VTK_OPENGL_HAS_OSMESA:BOOL=ON
>
>Again, these settings work fine with paraview 3.8.1 and the compiled
paraview executable does not produce a segmentation fault.
>
>Cheers,
>
>Frank.
>
>-----Original Message-----
>From: Arjun Yadav [mailto:y-arjun.az at srigroup.co.jp]
>Sent: Dienstag, 19. April 2011 08:10
>To: Albina, Frank
>Cc: Kevin H. Hobbs; David Partyka; paraview at paraview.org
>Subject: Re: [Paraview] Paraview v3.10.1/0 segmentation fault with MPI and
MESA support on.
>
>Try messa 7.7.1
>
>We use paraview3.10.0 and messa7.7.1 with mpi support. It does work.
>
>Arjun
>
>
>>差出人 : "Albina, Frank" <frank.albina at sauber-motorsport.com>
>>宛先 : "Kevin H. Hobbs" <hobbsk at ohio.edu>,David Partyka
><david.partyka at kitware.com>
>>件名 : Re: [Paraview] Paraview v3.10.1/0 segmentation fault with MPI and
>MESA support on.
>>送信日時 : 2011/04/19 15:00:32
>>
>>Hi Kevin!
>>
>>Thanks a lot for the offer. To be honest, I am still having trouble to
run
>paraview v3.10.0/v3.10.1 to have CPU rendering only with additional X
>support.
>>
>>On the one hand, I am performing the same configuration steps with CMake
>as for paraview 3.8.1, for which I have had no issues whatsoever wrt.
>running paraview in this configuration for the last 4 months. I am relying
>heavily on paraview for post-processing simulation results and it runs on
>my compute cluster daily in parallel.
>>
>>On the other hand, performing the same configuration steps with CMake for
>paraview 3.10.0 or 3.10.1 creates an executable which cannot run without
>producing a segmentation fault, which does appear just after the logo
>window has popped up. For information, I am compiling the paraview sources
>from scratch.
>>
>>I have been having the issue on two different computers now: one Linux
>x86_64 workstation running under SuSE SLES10 and one Linux x86_64 laptop
>running under OpenSuSE 11.1. It is not a compiler issue, since I have been
>able to reproduce the problem using different compilers versions (i.e. gcc
>v4.1.2, v4.5.1, v4.5.2 and v4.6.0) on the same architecture.
>>
>>Here are the settings I am using by default:
>>
>>//Path to a file.
>>OPENGL_INCLUDE_DIR:PATH=/code/CFD/develop/opt/share/Mesa-7.9.2/include
>>//Path to a library.
>>OPENGL_gl_LIBRARY:FILEPATH=/code/CFD/develop/opt/share/Mesa-7.9.2
>/lib/libGL.so
>>//Path to a library.
>>OPENGL_glu_LIBRARY:FILEPATH=/code/CFD/develop/opt/share/Mesa-7.9.2
>/lib/libGLU.so
>>//Path to a file.
>>OPENGL_xmesa_INCLUDE_DIR:PATH=/code/CFD/develop/opt/share/Mesa-7.9.2
>/include
>>//Path to a file.
>>OSMESA_INCLUDE_DIR:PATH=/code/CFD/develop/opt/share/Mesa-7.9.2/include
>>//Path to a library.
>>OSMESA_LIBRARY:FILEPATH=/code/CFD/develop/opt/share/Mesa-7.9.2
>/lib/libOSMesa.so
>>//Build classes for the X11 window system.
>>VTK_USE_X:BOOL=ON
>>//
>>VTK_OPENGL_HAS_OSMESA:BOOL=ON
>>
>>Note that the same problem arises also on the Linux workstation using
Mesa
>v7.10.1 and v7.10.2.
>>
>>Mesa v7.9.2 was compiled using the following steps:
>>
>>> make realclean
>>> ./configure --prefix=/code/CFD/develop/opt/share/Mesa-7.9.2 --with-x
>--enable-gl-osmesa --build=x86_64-suse-linux --with-driver=xlib
>--enable-glu --enable-glw --enable-pic --enable-opengl
>>> make -j 4
>>> make install
>>
>>Furthermore, the problem does not arise when I am disabling MPI support
>(i.e. VTK_USE_MPI:INTERNAL=OFF)  or having "conventional" OpenGL support
>with MPI enabled (i.e. using system OpenGL libraries and MPI support).
>>
>>Here is the list of libraries I am using for the build of paraview with
>MPI, MESA and PYTHON support:
>>+ Mesa v7.9.2
>>+ OpenMPI v1.4.3
>>+ Python v2.7.1
>>+ Qt v4.6.3
>>
>>Paraview v3.8.1 was compiled with the following library versions:
>>+ Mesa v7.7.1
>>+ OpenMPI v1.4.3
>>+ Python v2.7
>>+ Qt v4.6.2
>>
>>I would be very grateful if you could help me find out was I could be
>doing wrong. Again, the procedure works for paraview v3.8.1, so I am quite
>at loss when it does not work anymore for paraview v3.10.x.
>>
>>Please, let me know if you need more information.
>>
>>Cheers,
>>
>>Frank.
>>
>>-----Original Message-----
>>From: Kevin H. Hobbs [mailto:hobbsk at ohio.edu]
>>Sent: Montag, 18. April 2011 20:59
>>To: David Partyka
>>Cc: Albina, Frank; paraview at paraview.org
>>Subject: Re: [Paraview] Paraview v3.10.1/0 segmentation fault with MPI
and
>MESA support on.
>>
>>On 04/18/2011 07:50 AM, David Partyka wrote:
>>>  For
>>> example, here is how Kevin Hobes builds mesa and configures ParaView
>>> on his RedHat cluster.
>>>
>>
>>Frank,
>>
>>I am willing to help you out if you are still having trouble.
>>
>>_______________________________________________
>>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
>>
>
>