From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 103370] `DRI_PRIME=1 glxgears -info` halts the system with Intel Graphics [8086:5917] + AMD Graphics [1002:6665]. Date: Fri, 17 Nov 2017 10:12:51 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0509447558==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 3D9006E31C for ; Fri, 17 Nov 2017 10:12:51 +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 --===============0509447558== Content-Type: multipart/alternative; boundary="15109135713.Fd8AFb.6710"; charset="UTF-8" --15109135713.Fd8AFb.6710 Date: Fri, 17 Nov 2017 10:12:51 +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=3D103370 --- Comment #27 from Michel D=C3=A4nzer --- Thanks for bisecting, but I don't think that commit can be directly respons= ible for a GPU hang. Before that commit, the DRI3 code in Mesa would only use one back buffer for glxgears, which means that the GPU could only start renderi= ng a new frame after the previous one had finished presenting. Maybe that somehow prevented the hang. A possible test for this theory is running vblank_mode=3D0 DRI_PRIME=3D1 glxgears with Mesa 12.0.3; does that also trigger the hang? --=20 You are receiving this mail because: You are the assignee for the bug.= --15109135713.Fd8AFb.6710 Date: Fri, 17 Nov 2017 10:12:51 +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

Comme= nt # 27 on bug 10337= 0 from Michel D=C3=A4nzer 
Thanks for bisecting, but I don't think that commit can be dir=
ectly responsible
for a GPU hang. Before that commit, the DRI3 code in Mesa would only use one
back buffer for glxgears, which means that the GPU could only start renderi=
ng a
new frame after the previous one had finished presenting. Maybe that somehow
prevented the hang.

A possible test for this theory is running

 vblank_mode=3D0 DRI_PRIME=3D1 glxgears

with Mesa 12.0.3; does that also trigger the hang?

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