From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 88458] The monitor turns off when playing starcraft 2 in wine Date: Thu, 16 Jun 2016 16:41:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1019483289==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id AA7206E28D for ; Thu, 16 Jun 2016 16:41:22 +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 --===============1019483289== Content-Type: multipart/alternative; boundary="14660952820.4dd39BDa8.12906"; charset="UTF-8" --14660952820.4dd39BDa8.12906 Date: Thu, 16 Jun 2016 16:41:22 +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=3D88458 --- Comment #9 from Jaakko Niemi --- Good news! I got apitrace working, "apitrace trace wine .wine... Battle.net.exe", whic= h is the application from which you start the games. I got 26G file after 15 min= utes of playing one starcraft mission. Also looks like now the crashes have turned into VM faults: [456447.423707] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery tried 5 times [456447.423717] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [457965.078259] radeon 0000:01:00.0: GPU fault detected: 146 0x06c3d014 [457965.078262] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR=20= =20 0x0000A036 [457965.078263] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x030D0014 [457965.078265] VM fault (0x04, vmid 1) at page 41014, write from CB (208) [458184.091683] radeon 0000:01:00.0: GPU fault detected: 146 0x02e2500c [458184.091686] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR=20= =20 0x00009A97 [458184.091688] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0205000C [458184.091689] VM fault (0x0c, vmid 1) at page 39575, read from CB (80) [458201.097207] radeon 0000:01:00.0: GPU fault detected: 146 0x0023a014 [458201.097209] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR=20= =20 0x00009E81 [458201.097210] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x030A0014 [458201.097211] VM fault (0x04, vmid 1) at page 40577, write from CB (160) This happened after upgrading from kernel 4.6.0 (Mesa from June 1st), to ke= rnel 4.7.0-rc2, drm-next, Mesa from June 11th. Previously I got hang within 10 minutess, now spent bit over an hour with j= ust abovementioned log entries, no visible delays on screen. I'll continue test= ing. Would apitrace output still be interested on resolving this issue, or some = more information? --=20 You are receiving this mail because: You are the assignee for the bug.= --14660952820.4dd39BDa8.12906 Date: Thu, 16 Jun 2016 16:41:22 +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

Comment= # 9 on bug 88458<= /a> from Jaakko Niemi 
Good news!

I got apitrace working, "apitrace trace wine .wine... Battle.net.exe&q=
uot;, which is
the application from which you start the games. I got 26G file after 15 min=
utes
of playing one starcraft mission.

Also looks like now the crashes have turned into VM faults:

[456447.423707] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery
tried 5 times
[456447.423717] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery
failed
[457965.078259] radeon 0000:01:00.0: GPU fault detected: 146 0x06c3d014
[457965.078262] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR=20=
=20
0x0000A036
[457965.078263] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x030D0014
[457965.078265] VM fault (0x04, vmid 1) at page 41014, write from CB (208)
[458184.091683] radeon 0000:01:00.0: GPU fault detected: 146 0x02e2500c
[458184.091686] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR=20=
=20
0x00009A97
[458184.091688] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0205000C
[458184.091689] VM fault (0x0c, vmid 1) at page 39575, read from CB (80)
[458201.097207] radeon 0000:01:00.0: GPU fault detected: 146 0x0023a014
[458201.097209] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR=20=
=20
0x00009E81
[458201.097210] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x030A0014
[458201.097211] VM fault (0x04, vmid 1) at page 40577, write from CB (160)

This happened after upgrading from kernel 4.6.0 (Mesa from June 1st), to ke=
rnel
4.7.0-rc2, drm-next, Mesa from June 11th.

Previously I got hang within 10 minutess, now spent bit over an hour with j=
ust
abovementioned log entries, no visible delays on screen. I'll continue test=
ing.

Would apitrace output still be interested on resolving this issue, or some =
more
information?

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