All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204683] New: amdgpu: ring sdma0 timeout
Date: Sat, 24 Aug 2019 09:28:31 +0000	[thread overview]
Message-ID: <bug-204683-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=204683

            Bug ID: 204683
           Summary: amdgpu: ring sdma0 timeout
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.3.0-rc5
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: mh@familie-heinz.name
        Regression: No

Hi,

when playing some games I randomly (sometimes after 5 minutes, sometimes after
2 hours) get a blank screen, sometimes audio still works, sometimes the whole
system locks up. I've seen this with Rise of the Tomb Raider and 7 Days to Die
so far.

I finally managed to sync the log files to disk to get an error, before whole
thing locked up:

Aug 24 11:13:33 egalite kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
sdma0 timeout, signaled seq=368056, emitted seq=368057
Aug 24 11:13:33 egalite kernel: [drm:drm_atomic_helper_wait_for_flip_done
[drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out
Aug 24 11:13:33 egalite kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
Process information: process 7DaysToDie.x86_ pid 8108 thread 7DaysToDie:cs0
Aug 24 11:13:33 egalite kernel: amdgpu 0000:0c:00.0: GPU reset begin!
Aug 24 11:13:33 egalite kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
gfx timeout, but soft recovered

Only a hard reset made me recover from that.


This is with a self-built kernel 5.3.0-rc5. Also happens with 5.2.1.
Mesa: 19.1.4-1
GPU: Vega 56

Best
Matthias

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-08-24  9:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-24  9:28 bugzilla-daemon [this message]
2019-08-25  8:44 ` [Bug 204683] amdgpu: ring sdma0 timeout bugzilla-daemon
2019-08-26 15:25 ` bugzilla-daemon
2019-08-26 16:25 ` bugzilla-daemon
2019-08-28 19:40 ` bugzilla-daemon
2019-08-28 19:41 ` bugzilla-daemon
2019-09-05 12:08 ` bugzilla-daemon
2019-09-06 20:22 ` bugzilla-daemon
2019-09-07 13:44 ` bugzilla-daemon
2019-09-12 12:51 ` bugzilla-daemon
2019-09-12 22:18 ` bugzilla-daemon
2019-10-05  9:25 ` bugzilla-daemon
2019-10-11 15:02 ` bugzilla-daemon
2019-10-14 17:18 ` 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-204683-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.