Bug 73767 - Seriouss Sam 3 white screen, shader compiler fails
Summary: Seriouss Sam 3 white screen, shader compiler fails
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: glsl-compiler (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-18 16:56 UTC by kwahoo2
Modified: 2014-02-07 20:16 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
output with R600_DEBUG=sb,ps,vs (2.58 MB, text/plain)
2014-01-18 16:56 UTC, kwahoo2
Details
Screenshot (159.62 KB, image/jpeg)
2014-01-18 16:57 UTC, kwahoo2
Details
Serious Sam 3 log file (27.52 KB, text/plain)
2014-01-18 16:58 UTC, kwahoo2
Details

Description kwahoo2 2014-01-18 16:56:28 UTC
Created attachment 92345 [details]
output with R600_DEBUG=sb,ps,vs

Radeon 6670, almost all screen is white, except skyboxes.

OpenGL renderer string: Gallium 0.4 on AMD TURKS
OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.1.0-devel (git-1c5e296 saucy-oibaf-ppa+curaga)

uname -a
Linux adi-desktop 3.13.0-031300rc8-generic #201401120535 SMP Sun Jan 12 10:36:21 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Comment 1 kwahoo2 2014-01-18 16:57:24 UTC
Created attachment 92346 [details]
Screenshot
Comment 2 kwahoo2 2014-01-18 16:58:33 UTC
Created attachment 92347 [details]
Serious Sam 3 log file
Comment 3 Ian Romanick 2014-01-24 18:32:44 UTC
Can you bisect this by any chance?  There were some changes recently to #if handling in the GLSL preprocessor, and one of these probably caused this.
Comment 4 kwahoo2 2014-02-07 20:16:02 UTC
We should close the issue. The problem does not exist anymore.

OpenGL renderer string: Gallium 0.4 on AMD TURKS
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.2.0-devel (git-57f94bf saucy-oibaf-ppa)


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.