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:51:59 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1828592872==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id CA0866E6DE for ; Thu, 6 Sep 2018 15:51:58 +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 --===============1828592872== Content-Type: multipart/alternative; boundary="15362491180.D5DAC.22128" Content-Transfer-Encoding: 7bit --15362491180.D5DAC.22128 Date: Thu, 6 Sep 2018 15:51:58 +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 #7 from Michel D=C3=A4nzer --- (In reply to Martin Peres from comment #4) > However, if it is scheduler bug, I would assume this issue to be > reproducible on any AMD GPU. Can you try running > igt@amdgpu/amd_cs_nop@sync-fork-gfx0 in a loop for an hour or so? Hmm, 'fork' sounded suspicious, and indeed AFAICT this test uses the same amdgpu_context_handle (and by extension the same DRM file descriptor) in multiple processes spawned by fork(). I'm afraid Christian is going to expl= ain why that's not supported. :) I suppose we should at least handle this more gracefully though, if possibl= e. --=20 You are receiving this mail because: You are the assignee for the bug.= --15362491180.D5DAC.22128 Date: Thu, 6 Sep 2018 15:51:58 +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 # 7 on bug 10776= 2 from Michel D=C3=A4nzer 
(In reply to Martin Peres from comment #4)
> However, if it is scheduler bug, I would assume =
this issue to be
> reproducible on any AMD GPU. Can you try running
> igt@amdgpu/amd_cs_nop@sync-fork-gfx0 in a loop for an hour or =
so?

Hmm, 'fork' sounded suspicious, and indeed AFAICT this test uses the same
amdgpu_context_handle (and by extension the same DRM file descriptor) in
multiple processes spawned by fork(). I'm afraid Christian is going to expl=
ain
why that's not supported. :)

I suppose we should at least handle this more gracefully though, if possibl=
e.

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