<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [HSW] GPU HANG: ecode 0:0x87d3bffa on ctx load" href="https://bugs.freedesktop.org/show_bug.cgi?id=83677#c64">Comment # 64</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [HSW] GPU HANG: ecode 0:0x87d3bffa on ctx load" href="https://bugs.freedesktop.org/show_bug.cgi?id=83677">bug 83677</a> from <a class="email" href="mailto:hugegreenbug@gmail.com" title="Hugh Greenberg <hugegreenbug@gmail.com>"> Hugh Greenberg</a> <pre>I just noticed that if I use this kernel option: i915.enable_ppgtt=0, I get a different hang: 8.562995] [drm] stuck on render ring [ 498.564286] [drm] GPU HANG: ecode 0:0x85dffffd, in Xorg [1161], reason: Ring hung, action: reset [ 498.564289] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 498.564290] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 498.564291] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 498.564293] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 498.564294] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 507.545019] [drm] stuck on render ring [ 507.546315] [drm] GPU HANG: ecode 0:0x85dffffd, in Xorg [1161], reason: Ring hung, action: reset [ 507.546921] [drm:i915_context_is_banned] *ERROR* gpu hanging too fast, banning! It seems like this hang has been fixed here: <a href="https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78533">https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78533</a> , but when I compare the patch in that post with the kernel 3.17.1, there are things missing. For example, I see that this doesn't fully match up: --- a/drivers/gpu/drm/i915/i915_drv.h +++ b/drivers/gpu/drm/i915/i915_drv.h @@ -2139,13 +2139,16 @@ void i915_init_vm(struct drm_i915_private *dev_priv, void i915_gem_free_object(struct drm_gem_object *obj); void i915_gem_vma_destroy(struct i915_vma *vma); -#define PIN_MAPPABLE 0x1 -#define PIN_NONBLOCK 0x2 -#define PIN_GLOBAL 0x4 +#define PIN_OFFSET_FIXED 0x1 +#define PIN_OFFSET_BIAS 0x2 +#define PIN_MAPPABLE 0x4 +#define PIN_NONBLOCK 0x8 +#define PIN_GLOBAL 0x10 +#define PIN_OFFSET_MASK (~4095) Is this something worth investigating, or am I wasting my time?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>