| Summary: | Using FlightGear and Open Radeon Driver causes GLXUnsupportedPrivateRequest error in Xorg | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | popolon | ||||||
| Component: | Driver/Radeon | Assignee: | mesa-dev | ||||||
| Status: | RESOLVED NOTABUG | QA Contact: | |||||||
| Severity: | major | ||||||||
| Priority: | highest | CC: | ago | ||||||
| Version: | git | ||||||||
| Hardware: | x86 (IA32) | ||||||||
| OS: | Linux (All) | ||||||||
| URL: | http://mail.flightgear.org/pipermail/flightgear-users/2005-November/012990.html | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
popolon
2005-11-24 08:25:22 UTC
Created attachment 3915 [details]
Outputs obtained from gdb
This problem is plaguing quite a few ATI users. We launch FlightGear, and got
a GLXUnsupportedPrivateRequest errors while FlightGear is still displaying the
Splash Screen.
Qutie a few developers have looked into this issue at FlightGear, and none is
able to come up with a solution within FlightGear/SimGear.
Some people think it is a driver problem. However, I have never got a crash
like this when I was still using XFree (before I made a switch to Xorg).
Therefore, I think this error is more Xorg related. Please see the attached
gdb's output for more information.
Here are some discussions on the Devel-List that may help:
http://mail.flightgear.org/pipermail/flightgear-devel/2005-November/040030.html
http://mail.flightgear.org/pipermail/flightgear-devel/2005-November/040855.html
(In reply to comment #0) > X Error of failed request: GLXUnsupportedPrivateRequest > Major opcode of failed request: 142 (GLX) > Minor opcode of failed request: 16 (X_GLXVendorPrivate) > Serial number of failed request: 32 > Current serial number in output stream: 33 Any clue what FG was trying to do when this was generated? All of the various FG mailing list threads referenced in this bug talk about RenderTexture. That makes me suspicious that FG is trying to do something with pbuffers or some other unsupported GLX functionality. > Mesa warning: GL User Error: called without context: DeleteTextures That seems suspicious. > Any clue what FG was trying to do when this was generated? All of the various > FG mailing list threads referenced in this bug talk about RenderTexture. That > makes me suspicious that FG is trying to do something with pbuffers or some > other unsupported GLX functionality. Here is a reply from the person who did a lot of work in RenderTexture.cpp: http://mail.flightgear.org/pipermail/flightgear-devel/2005-December/041211.html Created attachment 4008 [details] gdb's output obtained from test case included with SimGear The attached file is another output from gdb, obtained by compiling and running a program called TestRenderTexture. The source of the test program is called TestRenderTexture.cpp. This file, along with RenderTexture.cpp, can be found here: http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/SimGear/simgear/screen/?cvsroot=SimGear-0.3 The above test was done using: Linux Distribution: Debian Kernel: 2.6.11 compiled with gcc3.4 Driver: r200 open source driver Xorg: CVS from last week compiled with gcc4.0 Mesa: CVS from last week compiled with gcc4.0 Simgear: Latest CVS compiled with gcc4.0 FlightGear: CVS from last week compiled with gcc4.0 Hardware: ATI 9200SE (PCI) Ian, Ampere,
Let me jump in here, as my comments on the flightgear-devel list might be one of
the main reasons that this ended up here.
I put togehter several sources of information here. Some from private mails from
Ampere and some from prevous experiences of myself from the 6.8.* fedora core
rpm's on an other r200.
What is done is that we choose a framebuffer configuration via GLX_SGIX_fbconfig
or, if available via the glx-1.4 aequivalent, and past that create a
GLX_SGIX_pbuffer or, if available via the glx-1.4 aequivalent.
At the time I had that problem, it did not matter if the SGIX extensions or the
glx versions of that functions are used.
Now, Ampere's glxinfo claims have GLX_SGIX_pbuffer and GLX_SGIX_fbconfig (He
sent me in a private mail, Ampere you might attach the output here to be sure).
Now I believe that it is safe to call these functions. At lest they should not
abort.
Greetings
Mathias
(In reply to comment #6) > Now I believe that it is safe to call these functions. At lest they should not > abort. If the extension isn't supported, and no version of any open-source drivers has ever supported GLX_SGIX_pbuffer, it's not safe to call. To determine whether or not the extension is supported, you have to look at the extensions listed under "GLX extensions", *NOT* "server glx extensions" or "client glx extensions". This is the output of the glXQueryExtensionsString function. (In reply to comment #6) > Now, Ampere's glxinfo claims have GLX_SGIX_pbuffer and GLX_SGIX_fbconfig (He > sent me in a private mail, Ampere you might attach the output here to be sure). See below for the glxinfo. There is no GLX_SGIX_pbuffer under "GLX extensions". name of display: :0.0 Disabling HW TCL support display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig client glx vendor string: SGI client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI R200 20040929 x86/MMX/SSE2 NO-TCL OpenGL version string: 1.3 Mesa 6.2.1 OpenGL extensions: GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_rectangle, GL_ARB_transpose_matrix, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint, GL_EXT_compiled_vertex_array, GL_EXT_convolution, GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_histogram, GL_EXT_packed_pixels, GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels, GL_ATI_blend_equation_separate, GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_window_pos, GL_NV_blend_square, GL_NV_light_max_exponent, GL_NV_texture_rectangle, GL_NV_texgen_reflection, GL_SGI_color_matrix, GL_SGI_color_table, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod glu version: 1.3 glu extensions: GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat ---------------------------------------------------------------------- 0x23 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x24 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x25 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x26 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x27 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x28 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x29 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x2a 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x2b 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x2c 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x2d 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x2e 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x2f 24 dc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x30 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x31 24 dc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x32 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow Hello I have this bug too on r200 xorg 6.9 rc2 Ian, sorry for the noise. Thanks for the fast response! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.