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] amdgpu: ring sdma0 timeout
Date: Thu, 12 Sep 2019 12:51:13 +0000	[thread overview]
Message-ID: <bug-204683-2300-vXi6whVIe8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204683-2300@https.bugzilla.kernel.org/>

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

--- Comment #9 from Matthias Heinz (mh@familie-heinz.name) ---
A small update.

I managed to go down even further. I'm currently at e6d2421343a7 in drm-next
and I see the following error:

Sep 12 14:32:44 egalite kernel: [drm:drm_atomic_helper_wait_for_flip_done
[drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out
Sep 12 14:32:44 egalite kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
gfx timeout, signaled seq=1023042, emitted seq=1023043
Sep 12 14:32:44 egalite kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
Process information: process 7DaysToDie.x86_ pid 6696 thread 7DaysToDie:cs0 pid
6698

Now it looks a lot like #201957, but I have no problems with kernels before and
5.0. It started with 5.1. So I'm not sure how similar it is.


I have one last idea what to do. The commit before e6d2421343a7 results in a
similar problem, but the display doesn't go blank and to standby. Only the
picture freezes and that's it.
I will try to find the commit that results in this bug and then see, if the
kernel of the commit before that one still has my main problem in it. If not
I'll post the range, probably somewhere inbetween is the error itself hidden.
Otherwise testing is not possible, since it freezes pretty fast and the ring
timeout bug takes up to 45 minutes to appear.

Since I'm at the 40th kernels so far, any help or even a hint is highly
appreciated. (I could use a faster testing solution.)

-- 
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

  parent reply	other threads:[~2019-09-12 12:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-24  9:28 [Bug 204683] New: amdgpu: ring sdma0 timeout bugzilla-daemon
2019-08-25  8:44 ` [Bug 204683] " 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 [this message]
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-vXi6whVIe8@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.