From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104289] [regression][vega10] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout on exiting certain Steam games
Date: Mon, 08 Oct 2018 13:14:41 +0000 [thread overview]
Message-ID: <bug-104289-502-MxeRC0LFn1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104289-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1735 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104289
dallase <dallas@engelken.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|CLOSED |REOPENED
--- Comment #14 from dallase <dallas@engelken.net> ---
My Radeon Pro Duo (polaris) is experiencing ring sdma0 timeouts when trying to
move to newer kernels. I’m running
a custom build of 4.17.0-rc2-180424-fkxamd (from ROCm Kernel
https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/fkxamd/drm-next-wip)
without issues.
When I build either of these kernels, the card gets ring timeouts on boot.
Both amdgpu-pro 18.20 and 18.30 for userland, didnt matter.
amd-staging-drm-next (built Oct 7 2018)
[ 61.701281] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
signaled seq=888, emitted seq=890
[ 61.701285] [drm] GPU recovery disabled.
[ 61.701397] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
signaled seq=902, emitted seq=904
[ 61.701399] [drm] GPU recovery disabled.
drm-next-4.20-wip (built Oct 8 2018)
[ 60.840847] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
signaled seq=914, emitted seq=916
[ 60.840851] [drm] GPU recovery disabled.
[ 60.840962] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
signaled seq=907, emitted seq=909
[ 60.840964] [drm] GPU recovery disabled.
Both of these kernels work fine on my Vega 56 and Vega 64's, just the Pro Duo
has the ring timeouts.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3470 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-10-08 13:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 13:53 [Bug 104289] [regression][vega10] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout on exiting Hitman bugzilla-daemon
2017-12-16 22:13 ` [Bug 104289] [regression][vega10] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout on exiting certain Steam games bugzilla-daemon
2017-12-18 10:18 ` bugzilla-daemon
2017-12-19 2:38 ` bugzilla-daemon
2017-12-19 13:38 ` bugzilla-daemon
2017-12-21 12:27 ` bugzilla-daemon
2017-12-21 12:29 ` bugzilla-daemon
2017-12-21 14:03 ` bugzilla-daemon
2017-12-21 14:15 ` bugzilla-daemon
2017-12-21 14:50 ` bugzilla-daemon
2017-12-31 14:07 ` bugzilla-daemon
2018-01-03 18:36 ` bugzilla-daemon
2018-01-03 18:36 ` bugzilla-daemon
2018-01-07 17:57 ` bugzilla-daemon
2018-08-09 6:46 ` bugzilla-daemon
2018-10-08 13:14 ` bugzilla-daemon [this message]
2018-10-08 14:45 ` 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-104289-502-MxeRC0LFn1@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