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 109819] Shadow of Mordor causes gpu freeze ryzen 2200g
Date: Mon, 04 Mar 2019 17:33:34 +0000	[thread overview]
Message-ID: <bug-109819-502-QejMSPgkub@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109819-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from Dominic <dominic.letz@berlin.de> ---
Per Linux Kernel 5.0 release here an updated report with that newest kernel and
updated head from git://anongit.freedesktop.org/mesa/drm

With the Linux Kernel 5.0 the dmesg log if full of amdgpu spam, that seems to
repeat itself all the time, independent of operation - not sure if it's related
to the grub debug line.

The the freeze though seems to still appear the same way but the error message
in dmesg has changed and now just shows two lines: that occur at the freeze
point:

[ 2501.329358] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=300047, emitted seq=300049
[ 2501.329419] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process ShadowOfMordor pid 3150 thread ShadowOfMo:cs0 pid 3152
[ 2501.329421] [drm] GPU recovery disabled.

Full dmesg log and glxinfo output in the new attached
dumps_from_dmesg_and_glxinfo_2

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

[-- Attachment #1.2: Type: text/html, Size: 1857 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-03-04 17:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-03 17:09 [Bug 109819] Shadow of Mordor causes gpu freeze ryzen 2200g bugzilla-daemon
2019-03-04 17:33 ` bugzilla-daemon [this message]
2019-03-04 17:35 ` bugzilla-daemon
2019-03-08  0:29 ` bugzilla-daemon
2019-03-08  0:43 ` [Bug 109819] [APITRACE] " bugzilla-daemon
2019-03-08  0:49 ` bugzilla-daemon
2019-03-08  0:50 ` bugzilla-daemon
2019-03-08 18:24 ` bugzilla-daemon
2019-03-10 17:40 ` bugzilla-daemon
2019-03-10 17:43 ` bugzilla-daemon
2019-03-10 17:45 ` bugzilla-daemon
2019-03-10 18:06 ` bugzilla-daemon
2019-09-16  7:50 ` bugzilla-daemon
2019-09-16  9:54 ` bugzilla-daemon
2019-11-19  9:15 ` 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-109819-502-QejMSPgkub@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