On Tuesday, 25 July 2017 13:13:41 CEST behrad eslami wrote:
> Jul 23 20:23:45 laptop kernel: [ 90.862717] [drm] GPU HANG: ecode
> 9:0:0xd23b808f, in chromium [1484], reason: Hang on render ring, action:
> resetJul 23 20:23:45 laptop kernel: [ 90.862721] [drm] GPU hangs can
> indicate a bug anywhere in the entire gfx stack, including userspace.Jul 23
> 20:23:45 laptop kernel: [ 90.862722] [drm] Please file a _new_ bug report
> on bugs.freedesktop.org against DRI -> DRM/IntelJul 23 20:23:45 laptop
> kernel: [ 90.862724] [drm] drm/i915 developers can then reassign to the
> right component if it's not a kernel issue.Jul 23 20:23:45 laptop kernel: [
> 90.862725] [drm] The gpu crash dump is required to analyze gpu hangs, so
> please always attach it.Jul 23 20:23:45 laptop kernel: [ 90.862727] [drm]
> GPU crash dump saved to /sys/class/drm/card0/errorJul 23 20:23:45 laptop
> kernel: [ 90.862802] drm/i915: Resetting chip after gpu hangJul 23
> 20:23:45 laptop kernel: [ 90.862878] [drm] RC6 onJul 23 20:23:45 laptop
> kernel: [ 90.880192] [drm] GuC firmware load skippedJul 23 20:23:56
> laptop kernel: [ 101.832839] drm/i915: Resetting chip after gpu hang
This seems very similar to my error, isn't it?