<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [HSW] stuck on render ring (screen is repeatedly freezing)" href="https://bugs.freedesktop.org/show_bug.cgi?id=88411#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [HSW] stuck on render ring (screen is repeatedly freezing)" href="https://bugs.freedesktop.org/show_bug.cgi?id=88411">bug 88411</a> from <a class="email" href="mailto:iviktorin@fit.vutbr.cz" title="Jan Viktorin <iviktorin@fit.vutbr.cz>"> Jan Viktorin</a> <pre>Hello, for 4.11.3, there is an improvement, the Chromium now runs well. However there were more quite short but noticable freezes. Jun 01 14:32:43 kernel: Linux version 4.11.3-1-ARCH (builduser@tobias) (gcc version 7.1.1 20170516 (GCC) ) #1 SMP PREEMPT Sun May 28 10:40:17 CEST 2017 ... Jun 01 14:34:33 kernel: [drm] GPU HANG: ecode 7:0:0x85dffffd, in Xorg [418], reason: Hang on render ring, action: reset Jun 01 14:34:33 kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jun 01 14:34:33 kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jun 01 14:34:33 kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel iss Jun 01 14:34:33 kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Jun 01 14:34:33 kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error Jun 01 14:34:33 kernel: drm/i915: Resetting chip after gpu hang ... Jun 01 14:34:33 kernel: [drm] GPU HANG: ecode 7:0:0x85dffffd, in Xorg [418], reason: Hang on render ring, action: reset Jun 01 14:34:33 kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jun 01 14:34:33 kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jun 01 14:34:33 kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel iss Jun 01 14:34:33 kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Jun 01 14:34:33 kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error Jun 01 14:34:33 kernel: drm/i915: Resetting chip after gpu hang Jun 01 14:38:00 kernel: drm/i915: Resetting chip after gpu hang Jun 01 14:38:14 kernel: drm/i915: Resetting chip after gpu hang ... Jun 01 14:41:16 kernel: drm/i915: Resetting chip after gpu hang Jun 01 14:41:50 kernel: drm/i915: Resetting chip after gpu hang Jun 01 14:42:10 kernel: drm/i915: Resetting chip after gpu hang Jun 01 14:43:12 kernel: drm/i915: Resetting chip after gpu hang ... Jun 01 14:48:08 kernel: drm/i915: Resetting chip after gpu hang ... Jun 01 14:54:41 kernel: drm/i915: Resetting chip after gpu hang ... Jun 01 15:01:15 kernel: drm/i915: Resetting chip after gpu hang</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>