<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [regression, bisected][BDW, GPU hang] stuck on render ring, always reproducible" href="https://bugs.freedesktop.org/show_bug.cgi?id=97779#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [regression, bisected][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>(In reply to Jason Ekstrand from <a href="show_bug.cgi?id=97779#c17">comment #17</a>) > This bisect is bad. You were bisecting through the Vulkan merge. Back when > the Vulkan driver was still in development the i965 driver in the vulkan > branch was very unstable. In order to get a proper bisect, you need to do > so while ignoring the vulkan branch. Sorry about that and thank you for the explanation. I redid the bisect, here are the results: 963513bb24bdd542f1af3733fab53ad450d3221b is the first bad commit commit 963513bb24bdd542f1af3733fab53ad450d3221b 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. Reviewed-by: Kristian Høgsberg <<a href="mailto:krh@bitplanet.net">krh@bitplanet.net</a>> Acked-by: Kenneth Graunke <<a href="mailto:kenneth@whitecape.org">kenneth@whitecape.org</a>> > I doubt that given that I can't get that commit to revert cleanly. A > similar commit does exist in the main tree and happened shortly prior to > merging the vulkan branch. The commit you point to got lost in the merge. > In any case, please re-bisect. Yes, there were merge conflicts, but I resolved them manually (see attachment <a href="https://bugs.freedesktop.org/attachment.cgi?id=127344">https://bugs.freedesktop.org/attachment.cgi?id=127344</a>).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>