From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 101731] System freeze with AMDGPU when playing The Witcher 3 Date: Tue, 11 Jul 2017 07:30:29 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1900606110==" 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 347226E2B5 for ; Tue, 11 Jul 2017 07:30:29 +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 --===============1900606110== Content-Type: multipart/alternative; boundary="14997582290.609DCa1.31988"; charset="UTF-8" --14997582290.609DCa1.31988 Date: Tue, 11 Jul 2017 07:30:29 +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=3D101731 --- Comment #5 from Philipp =C3=9Cberbacher --- I've managed to install amdgpu-pro and that has brought me a bit closer to narrowing this down. Just for reference, the software versions are amdgpu-p= ro 17.10.401251-2 and related packages (https://aur.archlinux.org/packages/?O=3D0&K=3Damdgpu), mesa-noglvnd 17.1.4, xorg-server 1.18.4-1. With amdgpu-pro I could narrow the freeze down to a specific option in the game: nvidia hairworks. With that option disabled I do not get the freeze. = As soon as it is enabled and a game loaded the machine freezes. I've used this to get a apitrace quickly and I have one with just 1.1 GB. However, replaying it does not produce the freeze. Maybe the actual freeze trigger didn't make it into the file. I'll provide you the file if you tell= me how. I do have a lot of warnings and errors on console when I replay that file (= see console_out). Nvidia hairworks does not trigger the freeze with amdgpu, but it does so immediately with amdgpu-pro. amdgpu triggers the freeze seemingly randomly,= at least in Velen, not in White Orchard. amdgpu-pro does not trigger the freez= e in Velen (unless hairworks is enabled of course). Since both amdgpu and amdgpu-pro use mesa and the non-mesa proprietary nvid= ia driver does not trigger this bug it is likely something in mesa. I hope the above helps to track it down. --=20 You are receiving this mail because: You are the assignee for the bug.= --14997582290.609DCa1.31988 Date: Tue, 11 Jul 2017 07:30:29 +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 # 5 on bug 10173= 1 from Philipp =C3=9Cberbacher
I've managed to install amdgpu-pro and that has brought me a b=
it closer to
narrowing this down. Just for reference, the software versions are amdgpu-p=
ro
17.10.401251-2 and related packages
(https=
://aur.archlinux.org/packages/?O=3D0&K=3Damdgpu), mesa-noglvnd 17.1=
.4,
xorg-server 1.18.4-1.

With amdgpu-pro I could narrow the freeze down to a specific option in the
game: nvidia hairworks. With that option disabled I do not get the freeze. =
As
soon as it is enabled and a game loaded the machine freezes.

I've used this to get a apitrace quickly and I have one with just 1.1 GB.
However, replaying it does not produce the freeze. Maybe the actual freeze
trigger didn't make it into the file. I'll provide you the file if you tell=
 me
how.
I do have a lot of warnings and errors on console when I replay that file (=
see
console_out).

Nvidia hairworks does not trigger the freeze with amdgpu, but it does so
immediately with amdgpu-pro. amdgpu triggers the freeze seemingly randomly,=
 at
least in Velen, not in White Orchard. amdgpu-pro does not trigger the freez=
e in
Velen (unless hairworks is enabled of course).

Since both amdgpu and amdgpu-pro use mesa and the non-mesa proprietary nvid=
ia
driver does not trigger this bug it is likely something in mesa. I hope the
above helps to track it down.


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