Created attachment 143235 [details]
[drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 668.446232] [drm] GPU HANG: ecode 6:0:0x85fffffc, in Civ4BeyondSword , reason: hang on rcs0, action: reset
[ 668.446235] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 668.446236] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 668.446236] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 668.446237] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 668.446238] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 668.446287] i915 0000:00:02.0: Resetting chip for hang on rcs0
Hi, is it reproducible issue or some kind of random?
We have plenty of such "random" hangs on SNB with the same error code. In all cases it was impossible to reproduce an issue :(
Provide please also mesa version in use.
It is random, I do not know how to reproduce it.
Mesa was 18.3.2 when the hang happened.
I am sorry, while mesa was 18.3.2, lib32-mesa was 18.3.1. After the upgrade there have been no hangs so far.
hm, if so, please wait for some time (play the game as usual) and if it is stable without hangs, please notify us so we will close an issue
Hangs have happened again with mesa and lib32-mesa 18.3.2.
hangs are on the same manner? Random? Or there is some specific place where it can be reproduced?
Also, how do you run the game? Thru the steam or directly via wine?
The hands happen randomly, nothing specific.
I play directly through wine.
With winetricks msxml and d3dx9.
Not in full-screen mode (in windowed mode).
With low graphics.
With single unit graphics, show health bars, detailed city info, no combat zoom, effects disabled, globe view buildings disabled, low resolution textures, no movies.
CORRECTION: msxml3, not msxml.
-- 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/1783.