From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 93649] [radeonsi] Graphics lockup while playing tf2 Date: Fri, 02 Sep 2016 16:15:47 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0655319561==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 6D4086EAC7 for ; Fri, 2 Sep 2016 16:15:47 +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 --===============0655319561== Content-Type: multipart/alternative; boundary="14728329473.90Dfac8.4331"; charset="UTF-8" --14728329473.90Dfac8.4331 Date: Fri, 2 Sep 2016 16:15:47 +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=3D93649 --- Comment #27 from AmarildoJr --- (In reply to Marek Ol=C5=A1=C3=A1k from comment #26) > (In reply to AmarildoJr from comment #25) > > Marek, since you work for AMD, I wonder if you could get a few hints fo= r the > > fix on Catalyst's sources? >=20 > It's not so simple. This is a bug somewhere in the Mesa driver such that > looking at other drivers won't likely help. This is a very weird issue. I think it may not be in Mesa, and here's why: * On Debian Jessie with kernel 3.16 and Mesa 10.3, the problem doesn't happ= en; * On the same Debian, but with mesa backported, the problem also doesn't happen; * On the same Debian with Mesa backported and the Kernel backported, the problem still doesn't happen; * On Arch Linux with Mesa downgraded to 10.3, the problem happens; * On the same Arch Linux with Mesa and Kernel downgraded (Kernel to version 3.16 and even 3.10), the problem still happens; * I'm not 100% sure I downgraded the Firmware on Arch, but I'll try today s= ince I'm testing a few drivers in Linux; * On vanilla Arch with Catalyst/FGLRX, the problem doesn't happen; So I do think this issue is much bigger than everybody thinks and only happ= ens with a certain combination of Mesa, Kernel, Firmware, and possibly libdrm, llvm, and other pieces of software as well. What I really think is that VALVe should investigate this since this problem started happening after they introduced mandatory Texture Streaming. --=20 You are receiving this mail because: You are the assignee for the bug.= --14728329473.90Dfac8.4331 Date: Fri, 2 Sep 2016 16:15:47 +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 # 27 on bug 93649<= /a> from AmarildoJr
(In reply to Marek Ol=C5=A1=C3=A1k from comment #26)
> (In reply to AmarildoJr from comment #25)
> > Marek, since you work for AMD, I wonder if you could get a few hi=
nts for the
> > fix on Catalyst's sources?
>=20
> It's not so simple. This is a bug somewhere in the Mesa driver such th=
at
> looking at other drivers won't likely help.

This is a very weird issue. I think it may not be in Mesa, and here's why:

* On Debian Jessie with kernel 3.16 and Mesa 10.3, the problem doesn't happ=
en;
* On the same Debian, but with mesa backported, the problem also doesn't
happen;
* On the same Debian with Mesa backported and the Kernel backported, the
problem still doesn't happen;
* On Arch Linux with Mesa downgraded to 10.3, the problem happens;
* On the same Arch Linux with Mesa and Kernel downgraded (Kernel to version
3.16 and even 3.10), the problem still happens;
* I'm not 100% sure I downgraded the Firmware on Arch, but I'll try today s=
ince
I'm testing a few drivers in Linux;
* On vanilla Arch with Catalyst/FGLRX, the problem doesn't happen;

So I do think this issue is much bigger than everybody thinks and only happ=
ens
with a certain combination of Mesa, Kernel, Firmware, and possibly libdrm,
llvm, and other pieces of software as well.

What I really think is that VALVe should investigate this since this problem
started happening after they introduced mandatory Texture Streaming.


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