Can anyone help me understand where the error messages, especially the major and minor opcodes, come from in an error like this one? Are these defined by Xorg, by the driver (Nvidia, in this case), or somewhere else entirely?
> X Error of failed request: BadAlloc (insufficient resources for > operation) > Major opcode of failed request: 135 (GLX) > Minor opcode of failed request: 34 () > Serial number of failed request: 26 > Current serial number in output stream: 27 > So, here's the background. I'm launching Xorg to manage the GLX context for some processing applications. When I use things like glxgears, glxspheres64 (from the VirtualGL project), glxinfo, or glmark2, everything works well. But when I use the actual user application (pvserver, part of Paraview), it gives me this error shortly after I connect my paraview frontend, to the pvserver backend. Running the pvserver inside gdb, with a "break exit", lets me backtrace it, but all it really tells me is that it's occurring when the application is trying to establish it's context. I can continue to dink around with it, but if anyone can at least point me in the right direction, that would be helpful. Thanks, -- Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu _______________________________________________ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
