dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110713] A Hat in Time: GPU hang with gallium nine
Date: Mon, 20 May 2019 17:03:22 +0000	[thread overview]
Message-ID: <bug-110713-502-7BsQ3sG993@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110713-502@http.bugs.freedesktop.org/>


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

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

kiwii@lytoria.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kiwii@lytoria.de

--- Comment #1 from kiwii@lytoria.de ---
I'd like to add, besides the R9 270X, this also affects Vega (both traces hang
my Vega 64) and Polaris (one user reports the chapter 1, act 4 hang to be 100%
reproducible on his RX 580).

I can also confirm both traces to play fine on my card with AMD_DEBUG=mono on
mesa-git and R600_DEBUG=mono on mesa 19.0.4.

With the NIR backend (R600_DEBUG=nir) it still hangs the same way as with
default TGSI on both 19.0.4 and git.

Note: Both traces are recorded on x64 and may need to be replayed with x64
apitrace to prevent running out of memory during shader compilation.

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

[-- Attachment #1.2: Type: text/html, Size: 2240 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-05-20 17:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-19 20:06 [Bug 110713] A Hat in Time: GPU hang with gallium nine bugzilla-daemon
2019-05-19 20:07 ` bugzilla-daemon
2019-05-20 17:03 ` bugzilla-daemon [this message]
2019-09-25 18:50 ` 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-110713-502-7BsQ3sG993@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