All of 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: Sun, 19 May 2019 20:06:49 +0000	[thread overview]
Message-ID: <bug-110713-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 110713
           Summary: A Hat in Time: GPU hang with gallium nine
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: lolisamurai@tfwno.gf
        QA Contact: dri-devel@lists.freedesktop.org

when using gallium nine, A Hat in Time locks up the entire system (requires a
hard reboot) on certain scenes.

I'm running a r9 270x with the amdgpu driver and mesa-git 110950.fc455797c1b-1
+ llvm-svn 360675-1

this issue was discussed with the gallium nine guys here:
https://github.com/iXit/wine-nine-standalone/issues/35 and they narrowed it
down to radeonsi

using AMD_DEBUG=mono fixes the issue

this is the apitrace for gallium nine
https://mega.nz/#!ZJhRhYaR!cVsMkRYkl6kPl0f43sMKu8NI4pvA4eE85cbLJyoQ-jE

the hang happens on the very last part of the trace, when the green goo in the
middle of the room is on screen. the area is chapter3, act6 and all other
challenges that take place there

playing back the trace also causes the same hang.

playing back the trace with AMD_DEBUG=mono works correctly without any hangs

other users report that turning off dynamic lights also fixes the issue

another user reported a similar hang in chapter 1, act 4 with this apitrace
https://kiwii.casa/downloads/d3d9.trace.xz

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

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

             reply	other threads:[~2019-05-19 20:06 UTC|newest]

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