All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91865] [r600g] GPU hang in 'gsraytrace' - NI/Turks (6670)
Date: Thu, 14 Jan 2016 17:01:03 +0000	[thread overview]
Message-ID: <bug-91865-502-5hNCU3yZaO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91865-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 545 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=91865

--- Comment #10 from Dieter Nützel <Dieter@nuetzel-hh.de> ---
OK, 

is this SOLVED by 'accident'?

For RV730 GPU hang (Bug 83319) the above identified commit do NOT solve the
hang.
(Bug is updated, now.)

The observed issues with R600_DEBUG=nosb for all three 'raytrace' variants
(vsraytrace/fsraytrace/gsraytrace) stays.
latest: Mesa 11.2.0-devel (git-6470435)

I'll open a new ticket for this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1552 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

      parent reply	other threads:[~2016-01-14 17:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91865-502@http.bugs.freedesktop.org/>
2015-09-03 13:15 ` [Bug 91865] [r600g] GPU hang in 'gsraytrace' - NI/Turks (6670) bugzilla-daemon
2015-09-03 13:16 ` bugzilla-daemon
2015-09-03 13:17 ` bugzilla-daemon
2015-09-03 13:46 ` bugzilla-daemon
2015-10-08 16:25 ` bugzilla-daemon
2015-11-27  3:19 ` bugzilla-daemon
2015-11-27  3:19 ` bugzilla-daemon
2015-11-27  3:20 ` bugzilla-daemon
2015-12-18  4:30 ` bugzilla-daemon
2016-01-14 11:26 ` bugzilla-daemon
2016-01-14 17:01 ` bugzilla-daemon [this message]

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-91865-502-5hNCU3yZaO@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.