Created attachment 106207 [details] /sys/class/drm/card0/error # dmesg | grep drm [ 1.266641] [drm] Initialized drm 1.1.0 20060810 [ 1.323547] [drm] Memory usable by graphics device = 2048M [ 1.323551] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver [ 1.358429] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 1.358430] [drm] Driver supports precise vblank timestamp query. [ 1.398185] fbcon: inteldrmfb (fb0) is primary device [ 1.607421] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 1.607462] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 [ 6309.481906] [drm] stuck on render ring [ 6309.481915] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 6309.481918] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 6309.481920] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 6309.481922] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 6309.481924] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 6309.485008] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x59bd000 ctx 0) at 0x59bd004 [ 6315.465052] [drm] stuck on render ring [ 6321.496263] [drm] stuck on render ring [ 6327.479412] [drm] stuck on render ring [ 6333.510594] [drm] stuck on render ring [ 6339.481741] [drm] stuck on render ring [ 6345.512976] [drm] stuck on render ring [ 6353.534565] [drm] stuck on render ring [ 6360.518951] [drm] stuck on render ring [ 6366.538102] [drm] stuck on render ring [ 6372.545275] [drm] stuck on render ring [ 6378.552456] [drm] stuck on render ring [ 6378.552545] [drm:intel_pipe_set_base] *ERROR* pin & fence failed [ 6384.571626] [drm] stuck on render ring [ 6391.556002] [drm] stuck on render ring [ 6397.587185] [drm] stuck on render ring [ 6403.582366] [drm] stuck on render ring [ 6409.589558] [drm] stuck on render ring [ 6415.596724] [drm] stuck on render ring [ 6421.591903] [drm] stuck on render ring [ 6427.611070] [drm] stuck on render ring [ 6433.630325] [drm] stuck on render ring [ 6441.603799] [drm] stuck on render ring [ 6447.647030] [drm] stuck on render ring [ 6454.619381] [drm] stuck on render ring [ 6460.650555] [drm] stuck on render ring [ 6466.645781] [drm] stuck on render ring [ 6472.640916] [drm] stuck on render ring [ 6478.684140] [drm] stuck on render ring [ 6484.655300] [drm] stuck on render ring [ 6490.662463] [drm] stuck on render ring [ 6496.693661] [drm] stuck on render ring [ 6502.712883] [drm] stuck on render ring [ 6508.684033] [drm] stuck on render ring [ 6514.727260] [drm] stuck on render ring [ 6520.722407] [drm] stuck on render ring [ 6526.717577] [drm] stuck on render ring [ 6532.748794] [drm] stuck on render ring [ 6538.743925] [drm] stuck on render ring [ 6544.763145] [drm] stuck on render ring [ 6550.746238] [drm] stuck on render ring [ 6556.777492] [drm] stuck on render ring [ 6562.772672] [drm] stuck on render ring
Created attachment 106208 [details] dmesg
*** Bug 79041 has been marked as a duplicate of this bug. ***
Duped the wrong one.
Please try kernel v4.4.
(In reply to Jani Nikula from comment #4) > Please try kernel v4.4. Timeout. Assuming that it is fixed by now. If this is not the case, please re-test with latest kernel & Mesa to see if this issue is still occurring since there were improvements pushed in kernel and Mesa that will benefit to your system.
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.