Created attachment 120005 [details] cat /sys/class/drm/card0/error [ 31.385362] [drm] Initialized drm 1.1.0 20060810 [ 31.797907] [drm] Memory usable by graphics device = 128M [ 31.797923] fb: switching to inteldrmfb from VESA VGA [ 31.798760] [drm] Replacing VGA console driver [ 31.801404] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 31.801411] [drm] Driver supports precise vblank timestamp query. [ 31.822545] [drm] initialized overlay support [ 31.823395] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 0 [ 31.894944] fbcon: inteldrmfb (fb0) is primary device [ 31.895817] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 83.704043] [drm] stuck on render ring [ 83.743458] [drm] GPU HANG: ecode 2:0:0x540fffc7, in X [844], reason: Ring hung, action: reset [ 83.743468] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 83.743471] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 83.743473] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 83.743475] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 83.743477] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 83.747972] drm/i915: Resetting chip after gpu hang [ 83.748020] [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -19
*** This bug has been marked as a duplicate of bug 90259 ***
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.