From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109102] At dual monitor intel_do_flush_locked failed: Resource deadlock avoided Date: Sat, 26 Jan 2019 10:50:53 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0181742469==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 983336E690 for ; Sat, 26 Jan 2019 10:50:53 +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 --===============0181742469== Content-Type: multipart/alternative; boundary="15484998530.F2cfca.23884" Content-Transfer-Encoding: 7bit --15484998530.F2cfca.23884 Date: Sat, 26 Jan 2019 10:50:53 +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=3D109102 --- Comment #3 from Gert vd Kraats --- I am using intel i915 gen 3 with 16 fence registers. When displaying the variable total_fences at function drm_intel_gem_check_aperture_space at libdrm-2.4.95/intel/intel_bufmgr_gem.c, it is seen that the deadlock-abort is occurring at total_fences =3D=3D 16, where the previous display shows total_fences =3D=3D 14, so there is an increment of 2 fences in stead of the usual increment of 1. Apparently the deadlock occurs at the "freeing fences phase", that is start= ed if total_fences is too high. I decided to lower the available_fences from 14 to 13 (see proposed patch). This solved the problem. After this patch I still saw sometimes total_fences =3D=3D 16, where the previous display shows total_fences =3D=3D 13, so there is an inc= rement of 3 fences. This did not cause a deadlock at the "freeing fences phase". --=20 You are receiving this mail because: You are the assignee for the bug.= --15484998530.F2cfca.23884 Date: Sat, 26 Jan 2019 10:50:53 +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 # 3 on bug 10910= 2 from Gert vd Kraats
I am using intel i915 gen 3 with 16 fence registers.
When displaying the variable total_fences
at function drm_intel_gem_check_aperture_space at
libdrm-2.4.95/intel/intel_bufmgr_gem.c,
it is seen that the deadlock-abort is occurring at total_fences =3D=3D 16,
where the previous display shows total_fences =3D=3D 14,
so there is an increment of 2 fences in stead of the usual increment of 1.
Apparently the deadlock occurs at the "freeing fences phase", tha=
t is started
if total_fences is too high.
I decided to lower the available_fences from 14 to 13 (see proposed patch).
This solved the problem.
After this patch I still saw sometimes total_fences =3D=3D 16,
where the previous display shows total_fences =3D=3D 13, so there is an inc=
rement
of 3 fences. This did not cause a deadlock at the "freeing fences phas=
e".


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