On Thursday, I was debugging an issue between 3.6.2, 3.8.0RC2 and the
3.9.0 development tree. My version of Paraview built against the GL
libraries (not Mesa) and the command "pvbatch --use-offscreen-rendering"
worked using 3.6.2 and 3.9.0, but failed against 3.8.0RC1 and RC2.
There were a couple of error messages pointing to the GL libraries, so I
upgraded my nVidia driver, and the problem went away. Does it make
sense - no. But, sometimes, you just go with whatever works ......
Josef Dubsky wrote:
Hi,
Ok, so this is what I found in the Xorg.0.log file:
Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x71) [0x488931]
1: /lib64/libc.so.6 [0x30748302d0]
2:
/usr/lib64/xorg/modules/extensions/libGLcore.so(_swrast_depth_test_span+0x6b
f) [0x2afe58a0b1bf]
3:
/usr/lib64/xorg/modules/extensions/libGLcore.so(_swrast_write_rgba_span+0x5b
e) [0x2afe589ee69e]
4: /usr/lib64/xorg/modules/extensions/libGLcore.so [0x2afe589f1d2c]
5: /usr/lib64/xorg/modules/extensions/libGLcore.so [0x2afe58a1c13f]
6: /usr/lib64/xorg/modules/extensions/libGLcore.so [0x2afe58a1ffda]
7:
/usr/lib64/xorg/modules/extensions/libGLcore.so(_tnl_run_pipeline+0x12b)
[0x2afe58a38feb]
8:
/usr/lib64/xorg/modules/extensions/libGLcore.so(_tnl_playback_vertex_list+0x
1e4) [0x2afe58a20834]
9: /usr/lib64/xorg/modules/extensions/libGLcore.so [0x2afe589a0707]
10: /usr/lib64/xorg/modules/extensions/libGLcore.so(_mesa_CallList+0x47)
[0x2afe589a3117]
11: /usr/lib64/xorg/modules/extensions/libglx.so(__glXRender+0xd7)
[0x2afe4e7ed7e7]
12: /usr/lib64/xorg/modules/extensions/libglx.so [0x2afe4e7f2008]
13: /usr/bin/Xorg(Dispatch+0x1ca) [0x44b20a]
14: /usr/bin/Xorg(main+0x44e) [0x43351e]
15: /lib64/libc.so.6(__libc_start_main+0xf4) [0x307481d994]
16: /usr/bin/Xorg(FontFileCompleteXLFD+0x229) [0x4327f9]
Fatal server error:
Caught signal 11. Server aborting
So you think it might be GL problem after all? I don't have much
experience
with that. The strange thing is it really never happens with the 3.6.2
version.
The bad thing for me is, that I cannot really experiment with the
driver, as
I'm using VMware. (I fully aware of the fact that I lose on
performance, but
the flexibility that VMware offers me is more valuable in my situation and
also my models are really small).
Josef
-----Original Message-----
From: Paul McIntosh [mailto:paul.mcint...@internetscooter.com]
Sent: Friday, May 14, 2010 11:53 AM
To: 'Josef Dubsky'; 'Rick Angelini'
Cc: paraview@paraview.org
Subject: RE: [Paraview] Paraview 3.8 RC2 makes the whole X restart
You might find some clues in the /var/log/Xorg.0.log and Xorg.0.log.old
As far has glx, I'd still update/downgrade the OpenGL driver even just to
rule that out.
Paul
-----Original Message-----
From: Josef Dubsky [mailto:josef.dub...@gcsc.uni-frankfurt.de]
Sent: Friday, 14 May 2010 7:24 PM
To: 'Paul McIntosh'; 'Rick Angelini'
Cc: paraview@paraview.org
Subject: RE: [Paraview] Paraview 3.8 RC2 makes the whole X restart
Well, I can confirm the problem doesn't occur with 3.6.2 (using the
precompiled vision, downloaded directly from the web). However the 3.8 RC2
(also the precompiled version from the web) does crash after some time
exactly as the 3.7CVS does.
So I think this shouldn't be a glx issue, right?
Josef
-----Original Message-----
From: Paul McIntosh [mailto:paul.mcint...@internetscooter.com]
Sent: Friday, May 14, 2010 12:58 AM
To: 'Rick Angelini'; 'Josef Dubsky'
Cc: paraview@paraview.org
Subject: RE: [Paraview] Paraview 3.8 RC2 makes the whole X restart
Another thought - just try the precompiled RC2 binaries and see what the
difference is.
I also agree with checking the driver, the last issue I had was caused by
this (an upgrade fixed it).
For the list - are there any debug options that make ParaView
print/log what
it is doing? E.g. export DEBUG_INFO=TRUE
There seems to be a few instances like this where something goes wrong and
there is no information. Even if there isn't ParaView should make use
of the
QStatusBar to give some hints.
Cheers,
Paul
-----Original Message-----
From: Rick Angelini [mailto:rick.angel...@us.army.mil]
Sent: Thursday, 13 May 2010 10:39 PM
To: Josef Dubsky
Cc: 'Paul McIntosh'; paraview@paraview.org
Subject: Re: [Paraview] Paraview 3.8 RC2 makes the whole X restart
Any chance you have a GL driver issue? Was your driver updated recently?
Can you *still* run 3.6.2 without problems?
Josef Dubsky wrote:
>
> Hi Paul,
>
> Thanks for your hint, but I do have enough disk space (~10 GB). I've
> already tried to look in /var/log/ but didn't really find anything
> suspicious.
>
> The strange thing is that it never happened with 3.6.2 or 3.6.1. The
> problem started to appear as of 3.7 (which I compiled from source) and
> remains also for 3.8 RC2 too
>
> Josef
>
> *From:* Paul McIntosh [mailto:paul.mcint...@internetscooter.com]
> *Sent:* Thursday, May 13, 2010 1:23 PM
> *To:* 'Josef Dubsky'
> *Subject:* RE: [Paraview] Paraview 3.8 RC2 makes the whole X restart
>
> A thought - do you have enough disk space? I am using 3.8 RC1/2 on
> Centos 5.5 with no issues. However I have noticed that if you run out
> of disk space, you get no warning and the session just crashes. Maybe
> ParaView is generating some file (swap?) that pushes your system to
> the limit of disk.
>
> I am not sure how to debug ParaView (yet) so I don't know if there is
> anything in the /var/log directory to look for.
>
> Paul
>
> ----------------------------------------------------------------------
> --
>
> *From:* paraview-boun...@paraview.org
> [mailto:paraview-boun...@paraview.org] *On Behalf Of *Josef Dubsky
> *Sent:* Thursday, 13 May 2010 8:37 PM
> *To:* paraview@paraview.org
> *Subject:* [Paraview] Paraview 3.8 RC2 makes the whole X restart
>
> Dear all,
>
> I have the following problem with Paraview 3.8 RC2. Actually the
> problem already appeared with the version 3.7 which I built from
> source. However, as it was a development version, I thought there
> might be still some bugs. But the 3.8 RC2 which I've installed just
> today behaves the same.
>
> So the problem is the following: After a few minutes (can really reach
> from ~30 seconds to ~20 minutes) of working with Paraview suddenly my
> whole Linux session restarts and I have to login again. Of course by
> this I lose all the opened applications (not just Paraview), which is
> pretty bad.
>
> There's no real way, how to exactly reproduce the problem. I mean the
> time when the crash occurs seems more or less random. But after max
> ~30 mins of working with Paraview, you can be almost sure it crashes.
>
> The only thing I can say is, that if I just leave Paraview minimized
> and do something else, the crash doesn't occur. Thus it really happens
> only if you actively do something in Paraview.
>
> I'm using CentOS 5.5.
>
> Are there any logs or error messages you could help to analyze the
> situation more? I'm not sure where I could find something relevant.
>
> Regards
>
> Josef
>
> ----------------------------------------------------------------------
> --
>
> _______________________________________________
> 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
>
_______________________________________________
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
