[Bug 97284] [SKL] GPU HANG: ecode 9:0:0x84dffff8, in X [1079], reason: Engine(s) hung, action: reset

[bugzilla-daemon at freedesktop.org]

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

Thomas Schneider <bugs.freedesktop.org at qsuscs.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |REOPENED

--- Comment #3 from Thomas Schneider <bugs.freedesktop.org at qsuscs.de> ---
Same bug just reappeared.
Mesa:      Installed versions:  13.0.0_rc1^d(13:40:13 2016-10-22)(classic dri3
egl gallium gbm gles2 llvm nptl wayland -bindist -d3d9 -debug -gles1 -opencl
-openmax -osmesa -pax_kernel -pic -selinux -vaapi -valgrind -vdpau -xa -xvmc
ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64
-x32" KERNEL="-FreeBSD" VIDEO_CARDS="intel nouveau -freedreno -i915 -i965 -ilo
-r100 -r200 -r300 -r600 -radeon -radeonsi -vc4 -vmware")

Nov 05 10:10:29 coruscant kernel: [drm] stuck on render ring
Nov 05 10:10:29 coruscant kernel: [drm] GPU HANG: ecode 9:0:0x84dffff8, in X
[1194], reason: Engine(s) hung, action: reset
Nov 05 10:10:29 coruscant kernel: [drm] GPU hangs can indicate a bug anywhere
in the entire gfx stack, including userspace.
Nov 05 10:10:29 coruscant kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Nov 05 10:10:29 coruscant kernel: [drm] drm/i915 developers can then reassign
to the right component if it's not a kernel issue.
Nov 05 10:10:29 coruscant kernel: [drm] The gpu crash dump is required to
analyze gpu hangs, so please always attach it.
Nov 05 10:10:29 coruscant kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Nov 05 10:10:29 coruscant kernel: drm/i915: Resetting chip after gpu hang
Nov 05 10:10:29 coruscant kernel: nouveau 0000:02:00.0: DRM: resuming kernel
object tree...
Nov 05 10:10:29 coruscant kernel: nouveau 0000:02:00.0: priv: HUB0: 6013d4
00005700 (1f408200)
Nov 05 10:10:29 coruscant kernel: nouveau 0000:02:00.0: priv: HUB0: 10ecc0
ffffffff (1f40822c)
Nov 05 10:10:29 coruscant kernel: nouveau 0000:02:00.0: DRM: resuming client
object trees...
Nov 05 10:10:31 coruscant kernel: [drm] RC6 on
Nov 05 10:10:34 coruscant kernel: ACPI Warning: \_SB.PCI0.PEG2.PEGP._DSM:
Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]
(20160422/nsarguments-95)
Nov 05 10:10:34 coruscant kernel: ACPI: \_SB_.PCI0.PEG2.PEGP: failed to
evaluate _DSM
Nov 05 10:10:34 coruscant kernel: ACPI Warning: \_SB.PCI0.PEG2.PEGP._DSM:
Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]
(20160422/nsarguments-95)
Nov 05 10:10:34 coruscant kernel: nouveau 0000:02:00.0: DRM: evicting
buffers...
Nov 05 10:10:34 coruscant kernel: nouveau 0000:02:00.0: DRM: waiting for kernel
channels to go idle...
Nov 05 10:10:34 coruscant kernel: nouveau 0000:02:00.0: DRM: suspending client
object trees...
Nov 05 10:10:34 coruscant kernel: nouveau 0000:02:00.0: DRM: suspending kernel
object tree...

I can’t exactly reproduce it, it just happens sometimes.

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