Bug 61883

Summary:	wine shader_generate_glsl_declarations fail
Product:	Mesa	Reporter:	Victor Aurélio <victoraur.santos>
Component:	Drivers/Gallium/r300	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium	CC:	pavel.ondracka
Version:	9.1
Hardware:	All
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	full dmesg output Xorg.0.log

Description Victor Aurélio 2013-03-06 01:36:40 UTC

Trying to run RE4 on my r300 freeze completely system

Submitted on wine bug tracker and suggested to report here.

----
err:winediag:shader_generate_glsl_declarations The hardware does not support enough uniform components to run this shader, it may not render correctly.
----

and lot of:

----
r300: ERROR: FS input fog unassigned, not enough hardware slots. (it's not a bug, do not report it)
----

for more details and full log see: http://bugs.winehq.org/show_bug.cgi?id=33129

Comment 1 Pavel Ondračka 2013-03-06 08:29:14 UTC

This is a known issue. Wine internally needs some extra uniforms for doing fixups, and when the shader already uses all of them, there isn't anything you can do about it. Wine still generates the shader in blind hope, that the constants near the end, which are removed, aren't actually used... 

On the other side, in my experience this usually causes only corruption (r300g driver produces dummy shaders in place of the failed ones), not complete system freeze, so maybe there is more going on.

You should try to obtain dmesg after the freeze and also the Xorg.0.log and attach them here.

Comment 2 Victor Aurélio 2013-03-06 15:43:24 UTC

Created attachment 76024 [details]
full dmesg output

Comment 3 Victor Aurélio 2013-03-06 15:43:57 UTC

Created attachment 76025 [details]
Xorg.0.log

Comment 4 GitLab Migration User 2019-09-18 18:51:54 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/354.

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.