From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 80419] XCOM: Enemy Unknown Causes lockup Date: Tue, 22 Dec 2015 22:52:25 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1568001457==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 9F5096E479 for ; Tue, 22 Dec 2015 14:52:25 -0800 (PST) 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 --===============1568001457== Content-Type: multipart/alternative; boundary="1450824745.0BB83542.7855"; charset="UTF-8" --1450824745.0BB83542.7855 Date: Tue, 22 Dec 2015 22:52:25 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D80419 Jose Fonseca changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brianp@vmware.com, | |jfonseca@vmware.com --- Comment #88 from Jose Fonseca --- (In reply to Kamil P=C3=A1ral from comment #87) > The apitrace developer patched glretrace, so that it no longer crashes > during replay. He says it's a bug inside XCOM. He also says the problem > might likely cause the radeonsi driver crash as well. See his comment her= e: > https://github.com/apitrace/apitrace/issues/407#issuecomment-166619366 >=20 > (If this indeed turns out to be an XCOM bug, it would be nice if we could > put some safeguards into the driver and didn't crash for invalid commands, > but I'm saying that as someone who knows exactly zero about gpu driver > programming). Yep. We could add a new drirc hack for ignoring the start/end params of glDrawRangeElementsBaseVertex for applications like XCOM, ie, assume 0..~0. XCOM is not unique here -- we've seen this happening on a Direct3D9 once at VMware. It looks like some of the proprietary OpenGL/Direct3D drivers out there simply outright ignore the min/max index hints. --=20 You are receiving this mail because: You are the assignee for the bug. --1450824745.0BB83542.7855 Date: Tue, 22 Dec 2015 22:52:25 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Jose Fonseca changed bug 80419<= /a>
What Removed Added
CC   brianp@vmware.com, jfonseca@vmware.com

Commen= t # 88 on bug 80419<= /a> from Jose Fonseca 
(In reply to Kamil P=C3=A1ral from comment #87)
> The apitrace developer patched glretrace, so tha=
t it no longer crashes
> during replay. He says it's a bug inside XCOM. He also says the problem
> might likely cause the radeonsi driver crash as well. See his comment =
here:
> https://github.com/apitrace/apitrace/issues/407#issuecomment-1=
66619366
>=20
> (If this indeed turns out to be an XCOM bug, it would be nice if we co=
uld
> put some safeguards into the driver and didn't crash for invalid comma=
nds,
> but I'm saying that as someone who knows exactly zero about gpu driver
> programming).

Yep.  We could add a new drirc hack for ignoring the start/end params of
glDrawRangeElementsBaseVertex for applications like XCOM, ie, assume 0..~0.

XCOM is not unique here -- we've seen this happening on a Direct3D9 once at
VMware.  It looks like some of the proprietary OpenGL/Direct3D drivers out
there simply outright ignore the min/max index hints.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1450824745.0BB83542.7855-- --===============1568001457== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1568001457==--