<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [drm] GPU HANG: ecode 9:0:0x859ffffb, in Xorg [2092], reason: hang on rcs0, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=106443#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [drm] GPU HANG: ecode 9:0:0x859ffffb, in Xorg [2092], reason: hang on rcs0, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=106443">bug 106443</a> from <a class="email" href="mailto:simeon.miteff@gmail.com" title="Simeon Miteff <simeon.miteff@gmail.com>"> Simeon Miteff</a> <pre>The old kernel was Ubuntu's 4.4.0-122.146-generic. Based on what is currently in Xenial, I believe the old userspace had: Intel driver: 2.99.917+git20160325 Mesa: 11.2.0 Let me know if accuracy is critical (I think can search /var/log/apt/ to find the exact versions). I booted the old kernel (same upgraded userspace), and reproduced the error. This time Xorg crashed once after login and then started again. This time kernel messages where a little more colorful than before: [ 54.764325] [drm] stuck on render ring [ 54.764435] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [2102], reason: Engine(s) hung, action: reset [ 54.764436] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 54.764437] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 54.764438] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 54.764438] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 54.764439] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 54.766472] drm/i915: Resetting chip after gpu hang [ 56.764626] [drm] RC6 on [ 72.756913] [drm] stuck on render ring [ 72.757189] [drm] GPU HANG: ecode 9:0:0x86dffffd, in Xorg [2102], reason: Engine(s) hung, action: reset [ 72.759030] drm/i915: Resetting chip after gpu hang [ 73.792203] [drm] RC6 on [ 75.850856] usb 1-8: reset high-speed USB device number 3 using xhci_hcd [ 84.749848] [drm] stuck on render ring [ 84.750103] [drm] GPU HANG: ecode 9:0:0x86dffffd, in Xorg [2102], reason: Engine(s) hung, action: reset [ 84.751978] drm/i915: Resetting chip after gpu hang [ 86.748842] [drm] RC6 on [ 165.726069] [drm] stuck on render ring [ 165.726437] [drm] GPU HANG: ecode 9:0:0x86dffffd, in Xorg [3066], reason: Engine(s) hung, action: reset [ 165.728202] drm/i915: Resetting chip after gpu hang [ 167.724909] [drm] RC6 on [ 185.713779] [drm] stuck on render ring [ 185.714098] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [3066], reason: Engine(s) hung, action: reset [ 185.715884] drm/i915: Resetting chip after gpu hang [ 187.712852] [drm] RC6 on I uploaded the corresponding error state.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>