From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107762] [Intel GFX CI] *ERROR* ring sdma0 timeout, signaled seq=137, emitted seq=137
Date: Thu, 06 Sep 2018 15:16:07 +0000 [thread overview]
Message-ID: <bug-107762-502-486hSLxaWR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107762-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1645 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107762
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ckoenig.leichtzumerken@gmai
| |l.com, dev@lynxeye.de
--- Comment #2 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Martin Peres from comment #0)
> [ 358.292609] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=137, emitted seq=137
> [ 358.292635] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=145, emitted seq=145
(In reply to Martin Peres from comment #1)
> [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=137, emitted seq=137
> [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=147, emitted seq=147
Hmm, signalled and emitted sequence numbers are always the same, meaning the
hardware hasn't actually timed out?
I can think of two possibilities:
* A GPU scheduler bug causing the job timeout handling to be triggered
spuriously. (Could something be stalling the system work queue, so the items
scheduled by drm_sched_job_finish_cb can't call drm_sched_job_finish in time?)
* A problem with the handling of the GPU's interrupts. Do the numbers on the
amdgpu line in /proc/interrupts still increase after these messages appeared,
or at least in the ten seconds before they appear?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3158 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-09-06 15:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 16:20 [Bug 107762] [Intel GFX CI] *ERROR* ring sdma0 timeout, signaled seq=137, emitted seq=137 bugzilla-daemon
2018-09-06 14:39 ` bugzilla-daemon
2018-09-06 15:16 ` bugzilla-daemon [this message]
2018-09-06 15:27 ` bugzilla-daemon
2018-09-06 15:30 ` bugzilla-daemon
2018-09-06 15:33 ` bugzilla-daemon
2018-09-06 15:34 ` bugzilla-daemon
2018-09-06 15:51 ` bugzilla-daemon
2018-09-06 16:15 ` bugzilla-daemon
2018-09-06 17:54 ` bugzilla-daemon
2019-03-08 15:58 ` bugzilla-daemon
2019-03-08 16:27 ` 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-107762-502-486hSLxaWR@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;
as well as URLs for NNTP newsgroup(s).