All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110509] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout
Date: Sun, 28 Apr 2019 15:42:07 +0000	[thread overview]
Message-ID: <bug-110509-502-UI82wGyyiR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110509-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from James.Dutton@gmail.com ---
This is a result of trying to play games in wine and dxvk.
It used to work, but the latest mesa git fails.
Games that fails are:
Assassin's creed odyssey
Devil May Cry 5

Both these games get through the title sequences, but fail when you reach the
actual game play. The GPU hangs and tries to reset, but fails to reset.

So, there are two problems:
1) Why does it hang in the first place
2) Why does it fail to recover and reset itself.

I can ssh into the PC.
poweroff   <-  Attempts to power off but never actually reaches off state.
echo b > /proc/sysrq-trigger    <-  reboots the box, and everything is then ok
again, so long as one does not try to play a game.

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

[-- Attachment #1.2: Type: text/html, Size: 1663 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-04-28 15:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 17:26 [Bug 110509] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout bugzilla-daemon
2019-04-24 17:31 ` bugzilla-daemon
2019-04-24 17:32 ` bugzilla-daemon
2019-04-24 17:33 ` bugzilla-daemon
2019-04-24 17:35 ` bugzilla-daemon
2019-04-28 15:42 ` bugzilla-daemon [this message]
2019-04-29 13:41 ` bugzilla-daemon
2019-04-29 18:30 ` bugzilla-daemon
2019-04-29 22:41 ` bugzilla-daemon
2019-04-30  1:26 ` bugzilla-daemon
2019-04-30 10:40 ` bugzilla-daemon
2019-04-30 10:44 ` bugzilla-daemon
2019-04-30 14:22 ` bugzilla-daemon
2019-04-30 14:26 ` bugzilla-daemon
2019-04-30 14:43 ` bugzilla-daemon
2019-08-13 20:56 ` bugzilla-daemon
2019-08-13 21:20 ` bugzilla-daemon
2019-09-25 18:49 ` 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-110509-502-UI82wGyyiR@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.