Summary: | [IVB] Lightsmark fails to run with "Variable shadowMap0 disappeared from shader" | ||
---|---|---|---|
Product: | Mesa | Reporter: | libo <bo.c.li> |
Component: | Drivers/DRI/i965 | Assignee: | Ian Romanick <idr> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | high | CC: | kenneth |
Version: | git | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 42993 |
Description
libo
2012-02-15 00:32:52 UTC
Is this regression? If so, can you provide a good commit? How about mesa master? It's a regression. and it's caused by mesa. such is a good mesa commit: (8.0)9489ae8938b74551913337876656bcb9178a8905 This bug also exists with the latest master mesa. Ian/Ken, do you have idea which commits may bring this? Otherwise we may have to bisect. This bug only exists on IVB ,not exists on other platforms. There was a short time when Lightsmark was broken on 8.0. The break started at 1b5e151ffae3ff50e9012243b7fcbbb60c3a0042, but was fixed with 99f9c9789a2d316d97ca6791343fb697f220929e. I can verify that libo's original reported revision, 65526d54aa2599b069bd443d3e6e9762e613042d, failed to compile one of the shaders partway through the run. This resulted in an assertion failure. Perhaps if you aren't compiling in debug mode, you'd see a "shadowMap0 disappeared" message. I don't know. (You should use --enable-debug.) However, Lightsmark works fine on IVB with the latest 8.0 branch (0aadb240e191538b07c45733dc2597235a52d274) and with master (709f50928e1d4df755ffb90ec9f33ba6c9605a32). It ran to completion and produces a FPS value with no complaints in both cases. yes.this bug doesn't exists on the latest master and 8.0 branch. |
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.