Bug 38085

Summary:	Mesa: User error: GL_INVALID_ENUM in glTexParameter(param=0x2901)
Product:	Mesa	Reporter:	Alexandre Demers <alexandre.f.demers>
Component:	Mesa core	Assignee:	mesa-dev
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	medium	Keywords:	NEEDINFO
Version:	git
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Alexandre Demers 2011-06-08 13:59:22 UTC

When using some applications launched in console, I receive the following error:

Mesa: User error: GL_INVALID_ENUM in glTexParameter(param=0x2901)

I was able to reproduce it at least with Wine and RendererFeatTest.bin64.

Comment 1 Brian Paul 2011-06-08 14:20:10 UTC

Looks like an application bug to me.  My guess is the app is trying to set GL_REPEAT wrap mode for a GL_TEXTURE_RECTANGLE target.

Comment 2 Alexandre Demers 2011-06-08 14:40:38 UTC

I could try to find the culprit commit, I was not having this issue before and I'm still using the same application (no update, same version). I'll try to find it out. Also, I receive the following error under Wine when launching Diablo 2:

Mesa: User error: GL_INVALID_ENUM in glDisable(0x8920)

Could it be related? If not, I'll open a different bug report.

Comment 3 Brian Paul 2011-06-08 15:13:04 UTC

0x8920 = GL_FRAGMENT_SHADER_ATI which is part of the GL_ATI_fragment_shader extension.  The app probably isn't properly checking if the extension is supported by the driver.  I don't think it's related to the first issue.

Comment 4 Ian Romanick 2011-06-09 10:20:41 UTC

Can you set a breakpoint at _mesa_error and get a backtrace?  Brian is probably right, and this will help confirm.

Comment 5 Alexandre Demers 2011-06-09 19:08:38 UTC

Maybe you can help me on that one. When adding a break point at _mesa_error, it is catched, but then I lose the possibility to use my keyboard and mouse. So I can't get a backtrace. If I switch to a different console and kill gdb from there, I recover control over my input devices, but I can't have the backtrace...

Comment 6 Brian Paul 2011-06-10 06:44:06 UTC

It's best to ssh in from another computer and do your debugging from there.

Comment 7 Alexandre Demers 2011-06-13 17:26:28 UTC

(In reply to comment #6)
> It's best to ssh in from another computer and do your debugging from there.

That will be a problem, since my netbook was stolen a couple of months ago. Any other suggestion?

Comment 8 Alexandre Demers 2012-08-28 14:55:59 UTC

Closing since I can't physically reproduce it and no one seems to have encountered this problem.

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.