Fallout 4 in wine-staging 3.3.
Crash in random places with "[drm] GPU HANG: ecode 7:0:0x86edbff1, in Fallout4.exe , reason: Hang on rcs0, action: reset" in dmesg and "i965: Failed to submit batchbuffer: Input/output error" in konsole.
Created attachment 138076 [details]
dmesg with dri debug
Created attachment 138077 [details]
DRM error data
Linux tp0 4.15.0-1-amd64 #1 SMP Debian 4.15.4-1 (2018-02-18) x86_64 GNU/Linux
Short kernel log:
[ 539.857402] [drm:missed_breadcrumb [i915]] rcs0 missed breadcrumb at intel_breadcrumbs_hangcheck+0x59/0x80 [i915], irq posted? no, current seqno=1db90, last=1dbc0
[ 541.987182] [drm] GPU HANG: ecode 7:0:0x86edbff1, in Fallout4.exe , reason: Hang on rcs0, action: reset
[ 541.987186] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 541.987188] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 541.987189] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 541.987190] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 541.987191] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 541.987242] [drm:i915_reset_device [i915]] resetting chip
[ 541.987674] i915 0000:00:02.0: Resetting chip after gpu hang
[ 542.495237] [drm:intel_gpu_reset [i915]] rcs0: timed out on STOP_RING
[ 542.495260] [drm:i915_gem_reset_engine [i915]] context Fallout4.exe/2 marked guilty (score 10) banned? no
[ 542.495273] [drm:i915_gem_reset_engine [i915]] resetting rcs0 to restart from tail of request 0x1db91
[ 542.495309] [drm:intel_enable_gt_powersave [i915]] Enabling RC6 states: RC6 on RC6p on RC6pp off
[ 542.495375] [drm:init_workarounds_ring [i915]] rcs0: Number of context specific w/a: 0
Hello Andrew, does the hang occur with any other application open with wine besides Fallout4.exe? Does the game worked properly with a previous mesa version?
Hello Elizabeth, same issue with Mesa 18.0.0-rc4 and wine-staging 3.4.
I dont try another app with wine, but native Doom3 and Quake4 works fine.
I will try running Fallout4 in Mesa 13.0.6 from Debian stable.
-- 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/1706.