[Bug 96525] Display Freeze

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96525

--- Comment #4 from yann <yann.argotti at intel.com> ---
(In reply to John Trengrove from comment #3)
> I've attached an additional GPU dump and journalctl log below. Having
> similar problems. Hard freeze which slowly comes back to life.. Jittery
> mouse cursor when it comes back.
> 
> [drm] stuck on render ring
> [drm] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [297], reason: Ring hung,
> action: reset
> [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack,
> including userspace.
> [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI ->
> DRM/Intel
> [drm] drm/i915 developers can then reassign to the right component if it's
> not a kernel issue.
> [drm] The gpu crash dump is required to analyze gpu hangs, so please always
> attach it.
> [drm] GPU crash dump saved to /sys/class/drm/card0/error
>  drm/i915: Resetting chip after gpu hang
> [drm] stuck on render ring
> [drm] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [297], reason: Ring hung,
> action: reset
> [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning!
> drm/i915: Resetting chip after gpu hang
> [drm] stuck on render ring
> [drm] GPU HANG: ecode 8:0:0xfffffffe, in compton [301], reason: Ring hung,
> action: reset

John, even if you are facing display freeze, Jean's gpu crash dump shows that
this is different issue (for instance IPEHR (Instruction Parser Error Header
Register) are different and your issue is not happening in batch likes Jean's
one) . So If this issue is still occuring, I suggest to fill a new bug and
attached both gpu crash dump & dmesg

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160901/d960e625/attachment.html>