From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88458] The monitor turns off when playing starcraft 2 in wine
Date: Thu, 16 Jun 2016 16:41:23 +0000 [thread overview]
Message-ID: <bug-88458-502-GPVSMmSVYi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88458-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2002 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=88458
--- Comment #9 from Jaakko Niemi <jaakko.niemi@iki.fi> ---
Good news!
I got apitrace working, "apitrace trace wine .wine... Battle.net.exe", which is
the application from which you start the games. I got 26G file after 15 minutes
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
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
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
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 kernel
4.7.0-rc2, drm-next, Mesa from June 11th.
Previously I got hang within 10 minutess, now spent bit over an hour with just
abovementioned log entries, no visible delays on screen. I'll continue testing.
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.
[-- Attachment #1.2: Type: text/html, Size: 2803 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-06-16 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-88458-502@http.bugs.freedesktop.org/>
2015-01-15 13:08 ` [Bug 88458] The monitor turns off when playing starcraft 2 in wine bugzilla-daemon
2015-01-15 13:13 ` bugzilla-daemon
2015-08-02 11:35 ` bugzilla-daemon
2016-06-01 18:19 ` bugzilla-daemon
2016-06-01 18:22 ` bugzilla-daemon
2016-06-01 18:24 ` bugzilla-daemon
2016-06-02 15:50 ` bugzilla-daemon
2016-06-04 17:01 ` bugzilla-daemon
2016-06-16 16:41 ` bugzilla-daemon [this message]
2016-06-17 12:37 ` bugzilla-daemon
2018-04-10 11:55 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-88458-502-GPVSMmSVYi@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox