Created attachment 127946 [details] GPU crash dump saved to /sys/class/drm/card0/error [ 944.741128] [drm] stuck on render ring [ 944.741867] [drm] GPU HANG: ecode 9:0:0x84dffff8, in X [263], reason: Ring hung, action: reset [ 944.741873] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 944.741876] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 944.741879] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 944.741882] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 944.741886] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 944.744367] drm/i915: Resetting chip after gpu hang [ 946.741318] [drm] RC6 on My system is Gentoo Linux ved-hp-gentoo 4.4.26-gentoo #1 SMP Sat Oct 22 19:25:38 MSK 2016 x86_64 Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz GenuineIntel GNU/Linux
There were workaround for SKL and improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring: mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce. In parallel, assigning to Mesa product. Kernel: 4.4.26-gentoo Platform: Skylake (pci id: 0x1916) Mesa: [Please confirm your mesa version] From this error dump, hung is happening in render ring batch with active head at 0xfd021644, with 0x7b000005 (3DPRIMITIVE) as IPEHR. Batch extract (around 0xfd021644): 0xfd021624: 0x78090005: 3DSTATE_VERTEX_ELEMENTS 0xfd021628: 0x02000000: buffer 0: invalid, type 0x0000, src offset 0x0000 bytes 0xfd02162c: 0x22220000: (0.0, 0.0, 0.0, 0.0), dst offset 0x00 bytes 0xfd021630: 0x02f60000: buffer 0: invalid, type 0x00f6, src offset 0x0000 bytes 0xfd021634: 0x11230000: (X, Y, 0.0, 1.0), dst offset 0x00 bytes 0xfd021638: 0x02f60004: buffer 0: invalid, type 0x00f6, src offset 0x0004 bytes 0xfd02163c: 0x11230000: (X, Y, 0.0, 1.0), dst offset 0x00 bytes Bad length 7 in (null), expected 6-6 0xfd021640: 0x7b000005: 3DPRIMITIVE: fail sequential 0xfd021644: 0x00000000: vertex count 0xfd021648: 0x00000003: start vertex 0xfd02164c: 0x0000001a: instance count 0xfd021650: 0x00000001: start instance 0xfd021654: 0x00000000: index bias 0xfd021658: 0x00000000: MI_NOOP 0xfd02165c: 0x784d0000: 3D UNKNOWN: 3d_965 opcode = 0x784d
Mesa version is from emerge --info mesa: media-libs/mesa-12.0.1::gentoo was built with the following: USE="classic dri3 egl gallium gbm llvm nptl udev wayland -bindist -d3d9 -debug -gles1 -gles2 -opencl -openmax -osmesa -pax_kernel -pic (-selinux) -vaapi -valgrind -vdpau -xa -xvmc" ABI_X86="64 -32 -x32" VIDEO_CARDS="i965 intel -freedreno -i915 -ilo -nouveau -r100 -r200 -r300 -r600 -radeon -radeonsi -vc4 -vmware" May be my mistake that VIDEO_CARDS is only i965 and intel but not i915? May be I also need to use vdpau? In addition to provided info: the hardware platform is HP ProBook 450
(In reply to Vladislav Dembskiy from comment #2) > Mesa version is from emerge --info mesa: > media-libs/mesa-12.0.1::gentoo was built with the following: > USE="classic dri3 egl gallium gbm llvm nptl udev wayland -bindist -d3d9 > -debug -gles1 -gles2 -opencl -openmax -osmesa -pax_kernel -pic (-selinux) > -vaapi -valgrind -vdpau -xa -xvmc" ABI_X86="64 -32 -x32" VIDEO_CARDS="i965 > intel -freedreno -i915 -ilo -nouveau -r100 -r200 -r300 -r600 -radeon > -radeonsi -vc4 -vmware" > > May be my mistake that VIDEO_CARDS is only i965 and intel but not i915? > May be I also need to use vdpau? > > In addition to provided info: the hardware platform is HP ProBook 450 Nope, VIDEO_CARDS="i965 intel" is fine for SKL. VDPAU is only for Gallium (which you don't need for Intel).
Current Gentoo version does not have such issues.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.