From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83319] [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) - RV730
Date: Thu, 14 Jan 2016 16:37:24 +0000 [thread overview]
Message-ID: <bug-83319-502-N1uSy4B15P@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83319-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 997 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=83319
--- Comment #15 from Dieter Nützel <Dieter@nuetzel-hh.de> ---
Update,
this one is NOT solved with current Mesa git.
For EG+ (Bug 91865) this is _fixed_ by 'accident' in Mesa git since:
commit 2239f3eaff5c72c4cb1d4a5be97feb4af3d08d25
Author: Dave Airlie <airlied@redhat.com>
Date: Mon Nov 30 15:48:22 2015 +1000
r600/shader: emit tessellation factors to GDS at end of TCS.
When we are finished the shader, we read back all the tess factors
from LDS and write them to special global memory storage using
GDS instructions.
This also handles adding NOP when GDS or ENDLOOP end the TCS.
Signed-off-by: Dave Airlie <airlied@redhat.com>
Dave and Marek any hints which could point in the right direction?
What is different in this case between R600/R700 and EG+ (NI/Turks in my case)
and what should I try next.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2094 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-01-14 16:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 22:59 [Bug 83319] New: [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) - RV730 bugzilla-daemon
2014-08-31 23:00 ` [Bug 83319] " bugzilla-daemon
2014-09-01 11:17 ` bugzilla-daemon
2014-09-01 11:37 ` bugzilla-daemon
2014-09-01 11:40 ` bugzilla-daemon
2014-09-01 11:40 ` bugzilla-daemon
2014-09-01 12:48 ` bugzilla-daemon
2014-10-23 18:34 ` bugzilla-daemon
2015-07-30 2:50 ` bugzilla-daemon
2015-09-02 18:23 ` bugzilla-daemon
2015-09-03 13:36 ` bugzilla-daemon
2015-11-25 1:46 ` bugzilla-daemon
2015-11-25 1:50 ` bugzilla-daemon
2015-11-25 6:34 ` bugzilla-daemon
2015-11-27 3:34 ` bugzilla-daemon
2016-01-14 10:10 ` bugzilla-daemon
2016-01-14 16:37 ` bugzilla-daemon [this message]
2016-01-14 21:58 ` bugzilla-daemon
2019-09-18 19:17 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-83319-502-N1uSy4B15P@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox