https://bugs.freedesktop.org/show_bug.cgi?id=90871
Hans de Goede <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #35 from Hans de Goede <[email protected]> --- Hi, (In reply to Hans de Goede from comment #34) > Ok' I've received this card now, and I can reproduce the problem. I'll > investigate and try to fix this next week. Ok, so as promised I've been investigating this one the last couple a days. The fptest.c reproducer works to reproduce it, thanks. At first I've tried different pitches / to swizzle / tile or not to tile on various involved buffers on both the ddx and mesa side all to no good. Today I had the bright idea (should have done that earlier) to run fptest through apitrace and then glretrace, this resulted in the following messages: 27 @0 glXCreateWindow(dpy = 0x120b0f0, config = 0x125c9c0, win = 6291457, attri 27: warning: unsupported glXCreateWindow call 49: message: major api error 1: GL_INVALID_VALUE in glTexImage2D(invalid width 49 @0 glTexImage2D(target = GL_TEXTURE_2D, level = 0, internalformat = GL_RGBA, 49: warning: glGetError(glTexImage2D) = GL_INVALID_VALUE 88: message: major api error 1: GL_INVALID_VALUE in glTexImage2D(invalid width 88 @0 glTexImage2D(target = GL_TEXTURE_2D, level = 0, internalformat = GL_RGBA, 88: warning: glGetError(glTexImage2D) = GL_INVALID_VALUE Rendered 2 frames in 0.0754768 secs, average of 26.4982 fps The 27* messages are there when doing a glretrace on nv4x too, and the retrace works fine on nv4x, so I believe that this warning can be ignored. The problem is the next messages. It seems that something (not fptest directly) is calling glTexImage2D with a npot width / height, where as nv3x is not npot capable. I'm a bit lost as to where this call is coming from, and as to whether or not this is a fptest issue, or an issue with the code which is actually making the glTexImage2D call. I'll ask Ben / Ilia for help. Regards, Hans -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.
_______________________________________________ Nouveau mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/nouveau
