<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - GPU HANG: ecode 9:0:0x85dffffb, in Borderlands2 [3497], reason: Engine(s) hung, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=97692#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - GPU HANG: ecode 9:0:0x85dffffb, in Borderlands2 [3497], reason: Engine(s) hung, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=97692">bug 97692</a> from <a class="email" href="mailto:cjdonahue@gmail.com" title="Chad <cjdonahue@gmail.com>"> Chad</a> <pre>I've been having the exact same issue at the same point in the game. Running a Dell XPS 13 9350 Ubuntu 16.04 w/ kernels up to the latest mainline 4.8RC6. All have same issue. dmesg and gpu crash info below: DMESG: [ 761.526619] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Borderlands2 [2831], reason: Hang on render ring, action: reset [ 761.526622] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 761.526623] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 761.526624] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 761.526625] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 761.526627] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 761.534566] drm/i915: Resetting chip after gpu hang [ 761.534955] [drm] GuC firmware load skipped [ 763.499353] [drm] RC6 on [ 777.523471] drm/i915: Resetting chip after gpu hang [ 777.523951] [drm] GuC firmware load skipped [ 779.530766] [drm] RC6 on [ 787.501268] drm/i915: Resetting chip after gpu hang [ 787.501702] [drm] GuC firmware load skipped [ 787.550160] show_signal_msg: 36 callbacks suppressed [ 787.550165] Borderlands2[2831]: segfault at 72a5c ip 00000</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>