<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [i915/hsw] Tropico 6 causes GPU hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=110315#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [i915/hsw] Tropico 6 causes GPU hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=110315">bug 110315</a> from <a class="email" href="mailto:manuel.lauss@gmail.com" title="Manuel Lauss <manuel.lauss@gmail.com>"> Manuel Lauss</a> <pre>Created <a href="attachment.cgi?id=143997" name="attach_143997" title="GPU crash dump #2">attachment 143997</a> <a href="attachment.cgi?id=143997&action=edit" title="GPU crash dump #2">[details]</a> 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</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>