OpenGL tool getting a GLXBadRenderRequest error

Question

Hello - we are having a very strange OpenGL anomaly with our Solaris 10 systems. We have an OpenGL application we run on our workstations using Hummingbird Exceed 3D v9.0.0.21.
When running the app on our Solaris 10 systems that had the patch clusters I downloaded on 06/26/2006 installed, the application runs fine and never crashes.
When running the app on our Solaris 10 systems that had the patch clusters I downloaded on 06/26/2006 installed, registered with Sun Update Manager, and all subsequent patches applied using updatemanager, running the OpenGL application eventually crashes, throwing this error in the shell window:
X Error of failed request: GLXBadRenderRequest
Major opcode of failed request: 139 (GLX)
Minor opcode of failed request: 1 (X_GLXRender)
Serial number of failed request: 1886332
Current serial number in output stream: 1886333
Does anyone have an idea how we might be able to track down this problem? Is it a known Solaris 10 issue? Any information would be greatly appreciated. Thanks,
jeff davey

Answer 1

More problem information, in case it helps:
When running on Solaris 10 with the latest patches, an OpenGL application is crashing repeatedly on us. For example, we have two SunFire v490s, one fully patched, and the other only patched up to the patch clusters downloaded on 06/26/2006. This OpenGL application is run on our local workstations using Hummingbird Exceed 3D v9.0.0.21.
Our servers that have not been fully patched have no problems at all running this application, but all the servers that have been fully patched are behaving as follows:
The OpenGL application calls glVertexPointer and glTexCoordPointer generate GL_INVALID_ENUM errors (i.e. glGetError returns GL_INVALID_ENUM if it is called immeadiately after either of these calls). When this occurs the application dies shortly thereafter. It appears to be dying on glXSwapBuffers calls, but we did not prove that this was always the case.
The application does print out the following error message when it dies:
X Error of failed request: GLXBadRenderRequest
Major opcode of failed request: 139 (GLX)
Minor opcode of failed request: 1 (X_GLXRender)
Serial number of failed request: 1712888
Current serial number in output stream: 1712889
This only occurs Suns with the latest patches and if the display is being exported to another machine. In our case this is to our PCs which are running Exceed 3D v9.0.0.21. If the application is run directly on a fully-patched Sun (a Sun Blade 2500 in our case, since that's the only one we have that's capable of drawing OpenGL graphics) the pointer calls do not generate an error and the application runs just fine. It also runs just fine and doesn't report any errors when run on the Suns that have not yet been updated to the latest patches whether or not the display is exported.
The calls we're making that report GL_INVALID_ENUM are:
glVertexPointer (3, 0x1406, 0, vertext_pointer)
glTexCoordPointer (2, 0x1406, 0, texture_pointer)
0x1406 is GL_FLOAT from gl.h.