<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BDW GPU hang] stuck on render ring, always reproducible" href="https://bugs.freedesktop.org/show_bug.cgi?id=97779#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BDW GPU hang] stuck on render ring, always reproducible" href="https://bugs.freedesktop.org/show_bug.cgi?id=97779">bug 97779</a> from <a class="email" href="mailto:regwz@seznam.cz" title="regwz <regwz@seznam.cz>"> regwz</a> <pre>I ran a bisect with the following result: 091b6156dd8553979336c15acdaf140e5419c483 is the first bad commit commit 091b6156dd8553979336c15acdaf140e5419c483 Author: Jason Ekstrand <<a href="mailto:jason.ekstrand@intel.com">jason.ekstrand@intel.com</a>> Date: Tue Dec 8 17:34:38 2015 -0800 i965/fs: Push small uniform arrays Unfortunately, this also means that we need to use a slightly different algorithm for assign_constant_locations. The old algorithm worked based on the assumption that each read of a uniform value read exactly one float. If it encountered a MOV_INDIRECT, it would immediately bail and push the whole thing. Since we can now read ranges using MOV_INDIRECT, we need to be able to push a series of floats without breaking them up. To do this, we use an algorithm similar to the on in split_virtual_grfs. I also verified that the bug can no longer be reproduced after reverting the commit from mesa 12.0.3.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>