At 10:01 AM -0800 11/10/03, Ian Romanick wrote:
Frank Gießler wrote:
with my current CVS snapshot (Changelog up to #530), glxgears gives me the following at startup:

X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Major opcode of failed request: 144 (GLX)
Minor opcode of failed request: 1 (X_GLXRender)
Serial number of failed request: 22
Current serial number in output stream: 23


This used to work before. I've seen this on both OS/2 and SuSE Linux 8.2 (XFree CVS built without DRI). Any idea what this means and/or where I should look?

Can you give any details to help reproduce this error? There is a reported bug in this area, but I thought that it was fixed. Your XF86Config would also be useful.


http://bugs.xfree86.org/show_bug.cgi?id=439

I'll put this on Bugzilla as well, but it is quite easy on XDarwin to reproduce this error. GLX fails consistently with indirect rendering and worked properly in 4.3.0. Only direct rendering works now.


[65:~] torrey% glxgears
2006 frames in 5.0 seconds = 401.200 FPS
^C
[65:~] torrey% setenv LIBGL_ALWAYS_INDIRECT 1
[65:~] torrey% glxgears
X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Major opcode of failed request: 151 (GLX)
Minor opcode of failed request: 1 (X_GLXRender)
Serial number of failed request: 22
Current serial number in output stream: 23


This bug is still present in the top of the tree.

--Torrey

_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Reply via email to