After playing some seconds monitor is turned off (7 of 7 launches). Sometimes it is then turned back on, sometimes - no. Sometimes an image just hangs. Ctrl+alt+f1 do not work when hanged.
Linux 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64 GNU/Linux
Radeon 7850 2GB memory

Created attachment 112289 [details]
dmesg log

In this case, he was involved back

Does this issue will occur on current Mesa git?

Created attachment 124241 [details]
kernel log

I can repro this reliably.

[AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280]
Kernel 4.6 drm-next, LLVM 3.8

These days I just get hung screen, audio keeps playing on background, I can ssh in and reboot. 

This happens only with SC2, I don't see problems with other games. Typically I don't even get halfway through campaign mission, sometimes I get crash when the game is playing video (assuming it's done through the engine...).

--

(In reply to Jaakko Niemi from comment #5)
> I can repro this reliably.
> 
> [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280]
> Kernel 4.6 drm-next, LLVM 3.8
> 
> These days I just get hung screen, audio keeps playing on background, I can
> ssh in and reboot. 
> 
> This happens only with SC2, I don't see problems with other games. Typically
> I don't even get halfway through campaign mission, sometimes I get crash
> when the game is playing video (assuming it's done through the engine...).
> 
> --

Oh, and Mesa is 12.0 rc1.

Can you record an apitrace? If you get a trace file that hangs reliably on replay, that would be very useful. Upload to Google Drive or similar if the file is too big (which it usually will be).

Definately maybe. I run:

apitrace trace wine .wine/drive_c...path to sc.exe

With few minutes running the game I get small file called "wine-preloader.trace", which is 270k, so I'm not sure if this is right. These days the game invokes in any case the battle.net.exe application from which game can be started. I'll do some more digging on this, but if anyone knows how to do this right (wine with modern blizzard games..), please let me know. Also let me know if the small trace file is interesting.

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?

VM faults from CB, interesting.

If the VM faults are reproducible using the trace, I'd be interested in downloading it if you can manage to upload it somewhere despite the size (Google Drive?).

Original problem fixed as per comment 9. Additional information (apitrace) on VM faults was never supplied so closing bug.

Feel free to reopen if you still have the secondary errors and can provide the requested apitrace. Thanks.