[Bug 97779] [regression, bisected][BDW, GPU hang] stuck on render ring, always reproducible
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Oct 29 04:39:46 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=97779
Jason Ekstrand <jason at jlekstrand.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #20 from Jason Ekstrand <jason at jlekstrand.net> ---
This bug should be fixed by the following commit:
commit 2a4a86862c949055c71637429f6d5f2e725d07d8
Author: Jason Ekstrand <jason.ekstrand at intel.com>
Date: Fri Oct 28 14:48:53 2016 -0700
i965/fs/generator: Don't use the address immediate for MOV_INDIRECT
The address immediate field is only 9 bits and, since the value is in
bytes, the highest GRF we can point to with it is g15. This makes it
pretty close to useless for MOV_INDIRECT. There were already piles of
restrictions preventing us from using it prior to Broadwell, so let's get
rid of the gen8+ code path entirely.
Signed-off-by: Jason Ekstrand <jason at jlekstrand.net>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97779
Cc: "12.0 13.0" <mesa-stable at lists.freedesktop.org>
Reviewed-by: Matt Turner <mattst88 at gmail.com>
I've tagged it for stable so it should be in 13.0 and it may even get into a
12.0 stable release.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161029/5fabd1d3/attachment.html>
More information about the intel-gfx-bugs
mailing list