Jul 23 20:23:45 laptop kernel: [ 90.862717] [drm] GPU HANG: ecode 9:0:0xd23b808f, in chromium [1484], reason: Hang on re
nder ring, action: reset
Jul 23 20:23:45 laptop kernel: [ 90.862721] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, includi
ng userspace.
Jul 23 20:23:45 laptop kernel: [ 90.862722] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI ->
DRM/Intel
Jul 23 20:23:45 laptop kernel: [ 90.862724] [drm] drm/i915 developers can then reassign to the right component if it's n
ot 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/error
Jul 23 20:23:45 laptop kernel: [ 90.862802] drm/i915: Resetting chip after gpu hang
Jul 23 20:23:45 laptop kernel: [ 90.862878] [drm] RC6 on
Jul 23 20:23:45 laptop kernel: [ 90.880192] [drm] GuC firmware load skipped
Jul 23 20:23:56 laptop kernel: [ 101.832839] drm/i915: Resetting chip after gpu hang
On Tuesday, July 25, 2017, 4:27:53 PM GMT+4:30, Zenaan Harkness <zenaan@freedbms.net> wrote:
On Sun, Jul 23, 2017 at 09:30:30AM +0200, Hans wrote:
> The only thing, I wondered by myself, why hibernate did not stop
> the release of stretch, as everyone knew, it is badly broken.
> Maybe, hibernate is no essential package/function, that would of
> course explain it.
Perhaps your particular combination of hardware has not been tested
hibernating before and so then it's a "new" bug?
It is possible that backports kernel/ custom kernel or newer kernel
version may work better for you.. just a possibility, good luck.