From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 107762] [Intel GFX CI] *ERROR* ring sdma0 timeout, signaled seq=137, emitted seq=137 Date: Thu, 06 Sep 2018 15:33:05 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0387138688==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 7E5FC6E6D4 for ; Thu, 6 Sep 2018 15:33:05 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0387138688== Content-Type: multipart/alternative; boundary="15362479850.2fC0DD1.16158" Content-Transfer-Encoding: 7bit --15362479850.2fC0DD1.16158 Date: Thu, 6 Sep 2018 15:33:05 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D107762 --- Comment #5 from Martin Peres --- (In reply to Lucas Stach from comment #3) > We've just fixed a bug in the scheduler timeout handling, which might lead > to the timeout worker being armed for the wrong job. >=20 > Does this issue still occur on a recent kernel with > 4823e5da2ea9061011242db81334d6ebbd2ed0a5 (drm/scheduler: fix timeout work= er > setup for out of order job completions) present? I see! We are using drmtip, which does not yet include 4823e5da2ea9061011242db81334d6ebbd2ed0a5. I assume we'll get it very soon, = but given the reproduction rate of the issue, we will not know for sure if the issue is fixed for at least another month (it happened twice in a week, 2% = of our runs). --=20 You are receiving this mail because: You are the assignee for the bug.= --15362479850.2fC0DD1.16158 Date: Thu, 6 Sep 2018 15:33:05 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 5 on bug 10776= 2 from Martin Peres 
(In reply to Lucas Stach from comment #3)
> We've just fixed a bug in the scheduler timeout =
handling, which might lead
> to the timeout worker being armed for the wrong job.
>=20
> Does this issue still occur on a recent kernel with
> 4823e5da2ea9061011242db81334d6ebbd2ed0a5 (drm/scheduler: fix timeout w=
orker
> setup for out of order job completions) present?

I see! We are using drmtip, which does not yet include
4823e5da2ea9061011242db81334d6ebbd2ed0a5. I assume we'll get it very soon, =
but
given the reproduction rate of the issue, we will not know for sure if the
issue is fixed for at least another month (it happened twice in a week, 2% =
of
our runs).

You are receiving this mail because:
  • You are the assignee for the bug.
= --15362479850.2fC0DD1.16158-- --===============0387138688== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0387138688==--