Created attachment 118061 [details] /sys/class/drm/card0/error During a CS:GO game, I've experienced a following gpu hang (/sys/class/drm/card0/error attached): [ 6989.665948] [drm] stuck on render ring [ 6989.670066] [drm] GPU HANG: ecode 8:0:0xfdb58705, in csgo_linux [4099], reason: Ring hung, action: reset [ 6989.670068] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 6989.670069] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 6989.670070] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 6989.670070] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 6989.670071] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 6989.671215] drm/i915: Resetting chip after gpu hang [ 6995.649659] [drm] stuck on render ring [ 6995.653487] [drm] GPU HANG: ecode 8:0:0xfedffffe, in Xorg [539], reason: Ring hung, action: reset [ 6995.655628] drm/i915: Resetting chip after gpu hang [ 7001.673344] [drm] stuck on render ring [ 7001.677169] [drm] GPU HANG: ecode 8:0:0xfedffffe, in Xorg [539], reason: Ring hung, action: reset [ 7001.677225] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning! [ 7001.679296] drm/i915: Resetting chip after gpu hang [ 7007.677043] [drm] stuck on render ring [ 7007.681075] [drm] GPU HANG: ecode 8:0:0xfedffffe, in csgo_linux [4099], reason: Ring hung, action: reset [ 7007.683098] drm/i915: Resetting chip after gpu hang distribution: arch linux kernel: 4.1.6 libdrm: 2.4.64 xf86-video-intel: 1:2.99.917+381+g5772556-1 mesa: git as of f30cf3258e495a583e011e07d5b4a19031c5518f cpu: Intel(R) Core(TM) i7-5600U CPU
Could you try with Mesa from today? I committed the following patch commit f01d92f4734a7ca62926dceda1d004c0cb10548c Author: Matt Turner <mattst88@gmail.com> Date: Mon May 2 23:32:13 2016 -0700 i965/fs: Don't follow pow with an instruction with two dest regs. which fixed a GPU hang in Unigine Valley. So it's possible that is the same bug you're seeing...
Please reopen the bug if you can still reproduce.
Dear Reporter, This Mesa bug has been in the "NEEDINFO" status for over 60 days. I am closing this bug based on lack of response but feel free to reopen if resolution is still needed. Please ensure you're supplying the correct information as requested. Thank you.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.