Re: Server segmentation fault at address 0x306 using ParaView
On 04/01/2011 16:08, Ken Olum wrote: From: Jon TURNEY jon.tur...@dronecode.org.uk Date: Sun, 02 Jan 2011 18:08:02 + I've updated them to fix the problem, and uploaded a Xserver snapshot at [1]. [1] ftp://cygwin.com/pub/cygwinx/XWin.20110102-git-29db9091c6ae4995.exe.bz2 This new snapshot works properly and does not crash. Thanks very much! Thanks for testing. I'll make an updated package with this change when I can. I would suggest that for an application like ParaView, you will probably get much better performance if you use the experimental hardware accelerated OpenGL -wgl mode I'll try this. Should I prefer direct rendering from remote machines that support that and only use AIGLX when I would have indirect rendering anyway, or should I explicitly request indirect rendering in order to use AIGLX in all cases? Thanks again. There's a trade-off here between rendering performance (software rending vs. hardware acceleration) and network latency (just sending the image vs. sending lots of OpenGL commands (some of which might be synchronous, requiring a round-trip for the response)) So, the short answer is, you should try both and see which performs best :-) Provided your server isn't on the moon, I would guess that ParaView would behave better with indirect but accelerated rendering, but that's just speculation. I'm not sure of the reasoning for mesa making direct using software rendering the default for remote clients, I'm not sure exactly what kind of client it helps with. Possibly the UG should have some words discussing this issue. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Server segmentation fault at address 0x306 using ParaView
From: Jon TURNEY jon.tur...@dronecode.org.uk Date: Sun, 02 Jan 2011 18:08:02 + I've updated them to fix the problem, and uploaded a Xserver snapshot at [1]. [1] ftp://cygwin.com/pub/cygwinx/XWin.20110102-git-29db9091c6ae4995.exe.bz2 This new snapshot works properly and does not crash. Thanks very much! I would suggest that for an application like ParaView, you will probably get much better performance if you use the experimental hardware accelerated OpenGL -wgl mode I'll try this. Should I prefer direct rendering from remote machines that support that and only use AIGLX when I would have indirect rendering anyway, or should I explicitly request indirect rendering in order to use AIGLX in all cases? Thanks again. Ken -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Server segmentation fault at address 0x306 using ParaView
On 15/12/2010 16:14, Ken Olum wrote: On the Mandriva 2010.1 host, /usr/lib64/libGL.so.1 is from lib64mesagl1-7.8.1-6mdv2010.1. On the RHEL host, it is from mesa-libGL-6.5.1-7.8.el5. Thanks. I was able to reproduce your problem using Centos 5.5 (no RHEL for me :-)) I have not tried other OpenGL programs, but I can run glxinfo without a crash on either machine. I attach the results. They are not the same. In particular, I was surprised to find that RHEL reports direct rendering: No while Mandriva reports direct rendering: Yes, although I don't know if this matters when one is running over the network anyway. Yes, this is the significant difference: The more recent libGL is able to provide direct rendering using the xlib driver, where the software OpenGL renderer is used at the client to render to a pixmap, which is then transferred using xlib to the server. Unfortunately, some rather fragile linkage tricks are used at the moment to make indirect rendering function dispatch work, and it seems they have been broken when we updated to mesa 7.8. I've updated them to fix the problem, and uploaded a Xserver snapshot at [1]. Please give that a try and see if it fixes your problem, if you can. I would suggest that for an application like ParaView, you will probably get much better performance if you use the experimental hardware accelerated OpenGL -wgl mode, see [2] for details. [1] ftp://cygwin.com/pub/cygwinx/XWin.20110102-git-29db9091c6ae4995.exe.bz2 [2] http://cygwin.com/ml/cygwin-xfree-announce/2010-11/msg0.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Server segmentation fault at address 0x306 using ParaView
On 14/12/2010 17:52, Ken Olum wrote: Here is the backtrace. Thanks again. Ken #0 0x0a3eb232 in swrast_dri!_mesa_GetProgramNamedParameterdvNV () from /usr/lib/dri/swrast_dri.so #1 0x004e4baa in _fu456___glapi_Dispatch () at indirect_dispatch.c:4854 #2 0x004d6975 in __glXDisp_Render (cl=0x1010ab4c, pc=0x10459170 \024) at glxcmds.c:1854 #3 0x004d2515 in __glXDispatch (client=0x1010aa88) at glxext.c:604 #4 0x00570ac0 in Dispatch () at dispatch.c:433 #5 0x0056af00 in main (argc=2, argv=0x6123d464, envp=0x100300f8) at main.c:298 Thanks. Can you compare the versions of libGL installed on the Mandriva 2010.1 and RHEL 5.5 hosts? Have you tried if other OpenGL programs on the RHEL host work? Does glxinfo work? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Server segmentation fault at address 0x306 using ParaView
On the Mandriva 2010.1 host, /usr/lib64/libGL.so.1 is from lib64mesagl1-7.8.1-6mdv2010.1. On the RHEL host, it is from mesa-libGL-6.5.1-7.8.el5. I have not tried other OpenGL programs, but I can run glxinfo without a crash on either machine. I attach the results. They are not the same. In particular, I was surprised to find that RHEL reports direct rendering: No while Mandriva reports direct rendering: Yes, although I don't know if this matters when one is running over the network anyway. Ken glxinfo.Mandriva Description: Binary data glxinfo.RHEL Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Server segmentation fault at address 0x306 using ParaView
On 29/11/2010 00:26, Ken Olum wrote: Running paraview 3.8.1 (see http://paraview.org) on a Linux client (Mandriva 2010.0 or Red Hat Enterprise Server 5.5) causes a crash of my Cygwin/X (release 1.9.2.0) with Segmentation fault at address 0x306. Any ideas? Thanks for the problem report. In a quick test, I wasn't able to reproduce this crash using paraview 3.8.1 on Fedora 14. Do you need to do anything other than just start paraview to demonstrate the problem? Paraview uses OpenGL. Perhaps that is related. Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Can you attach your /var/log/xwin/XWin.0.log, please. Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Server segmentation fault at address 0x306 using ParaView
On 14/12/2010 16:07, Ken Olum wrote: Thanks for looking into this. All I need to do to trigger the problem is to run paraview. However, it seems to depend on the details of the Linux installation -- system libraries, I suppose. On this system it works: Mandriva Linux release 2010.1 (Official) for x86_64 Linux cosmos.phy.tufts.edu 2.6.33.7-server-2mnb #1 SMP Mon Sep 20 19:01:10 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux Whereas on this one it crashes: Red Hat Enterprise Linux Client release 5.5 (Tikanga) Linux node12 2.6.18-194.17.4.el5 #1 SMP Wed Oct 20 13:03:08 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux These two systems are both running the exact same 3.8.1 x86_64 executable that I downloaded. I attach my Xwin.0.log showing the crash. Thanks. Can you try to obtain a backtrace for the crash using the instructions at [1], please? [1] http://x.cygwin.com/devel/backtrace.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Server segmentation fault at address 0x306 using ParaView
Here is the backtrace. Thanks again. Ken #0 0x0a3eb232 in swrast_dri!_mesa_GetProgramNamedParameterdvNV () from /usr/lib/dri/swrast_dri.so #1 0x004e4baa in _fu456___glapi_Dispatch () at indirect_dispatch.c:4854 #2 0x004d6975 in __glXDisp_Render (cl=0x1010ab4c, pc=0x10459170 \024) at glxcmds.c:1854 #3 0x004d2515 in __glXDispatch (client=0x1010aa88) at glxext.c:604 #4 0x00570ac0 in Dispatch () at dispatch.c:433 #5 0x0056af00 in main (argc=2, argv=0x6123d464, envp=0x100300f8) at main.c:298 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
