Bug 110315

Created attachment 143992 [details]
bad_screenshot_from_HSW

hi, thank you for the report. I checked this game on HSW also, and didn't reproduce hang (kernel is 5.0.7, OS Fedora 29)
Mesa version was taken from today's git master.

Could you please clarify - what steps did you do to reproduce hang?

>The game mostly works, but it has a lot of triangles blinking.
According to this - in my case I would say that game is completely not playable in 2 reasons - first one is performance - too slow and laggy, second one - a lot of huge graphic artifacts.

But interesting that not all these artifacts can be recorded into apitrace. Here are few screenshots, recorded on HSW and replayed on KBL.
https://drive.google.com/open?id=1yD1auM-WA8pLY3qKINKcOF7yzAWo4jIA

Created attachment 143997 [details]
GPU crash dump #2

I tried again with a fresh mesa HEAD, Linux-5.0.7.  The GPU hangs appear as soon as the "postcard" loading screen is shown. It gets to the main menu eventually, but as you already found out, it's very slow and with tons of graphics artifacts.
(Unsurprisingly, it's playable with the nvidia card).

[  498.568025] [drm] GPU HANG: ecode 7:0:0x87d53d10, in Tropico6-Linux- [15839], reason: hang on rcs0, action: reset
[  498.568028] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  498.568028] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  498.568029] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  498.568029] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  498.568030] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  498.568067] i915 0000:00:02.0: Resetting chip for hang on rcs0
[  502.580665] Asynchronous wait on fence i915:rcs0:2abd timed out (hint:intel_atomic_commit_ready+0x0/0x50)
[  506.420698] i915 0000:00:02.0: Resetting chip for hang on rcs0
[  514.527364] i915 0000:00:02.0: Resetting chip for hang on rcs0
[  516.660602] Asynchronous wait on fence i915:rcs0:2ad3 timed out (hint:intel_atomic_commit_ready+0x0/0x50)
[  522.420684] i915 0000:00:02.0: Resetting chip for hang on rcs0
[  530.527273] i915 0000:00:02.0: Resetting chip for hang on rcs0
[  533.513855] Asynchronous wait on fence i915:rcs0:2aea timed out (hint:intel_atomic_commit_ready+0x0/0x50)
[  538.420647] i915 0000:00:02.0: Resetting chip for hang on rcs0
[  546.527074] i915 0000:00:02.0: Resetting chip for hang on rcs0
[  549.513633] Asynchronous wait on fence i915:rcs0:2b04 timed out (hint:intel_atomic_commit_ready+0x0/0x50)
[  554.420338] i915 0000:00:02.0: Resetting chip for hang on rcs0
[  562.526852] i915 0000:00:02.0: Resetting chip for hang on rcs0
[  570.420119] i915 0000:00:02.0: Resetting chip for hang on rcs0
[  578.526676] i915 0000:00:02.0: Resetting chip for hang on rcs0
[  586.419943] i915 0000:00:02.0: Resetting chip for hang on rcs0
[  589.619838] Asynchronous wait on fence i915:rcs0:2b3a timed out (hint:intel_atomic_commit_ready+0x0/0x50)
[  594.526510] i915 0000:00:02.0: Resetting chip for hang on rcs0

thank you for clarification. Finally reproduced hang. But in my case I got them between splash screens and main game menu. Investigating and trying to reproduce them (they were not stable unfortunately)

I have tested Tropico 6 on Kaby Lake and while there is no such issues as on Haswell it has geometry flickering caused by compute workload, see https://gitlab.freedesktop.org/mesa/mesa/merge_requests/621

Regarding the graphical artifacts on HSW - the artifacts of water are caused by TCS shader most probably it has the same cause as artifacts in Downward (https://bugs.freedesktop.org/show_bug.cgi?id=104297), they could be reproduced by launching game with INTEL_SCALAR_TCS=0 on skylake or kabylake.

The causes of hang and flickering shadows are still unknown to me.

Shadows flickering on HSW are caused by the same issue as in SuperTuxKart (https://bugs.freedesktop.org/show_bug.cgi?id=110395). There is a fix/workaround https://gitlab.freedesktop.org/mesa/mesa/merge_requests/660

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1803.