Created attachment 126887 [details] extracted from /var/log/syslog Lenovo X1 Carbon. Ubuntu 14.04 Worked fine since early 2015. Last couple of weeks have not been able to suspend/resume properly. First symptom was blacked-out menu text on windows. Updated kernel to 4.4.0-38-generic; now session dies immediately on resume. System runs OK while up, but have to shut down to transport. [drm] stuck on render ring [drm] GPU HANG: ecode 7:0:0x85dfbff8, in compiz [6944], reason: Ring hung, action: reset WARNING: CPU: 2 PID: 7617 at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/drivers/gpu/drm/i915/intel_display.c:11309 intel_mmio_flip_work_func+0x385/0x3d0 [i915]()
can you attach kernel log from the boot time? Moreover, would you mind to attach gpu crash dump located in /sys/class/drm/card0/error?
that kernel comes with a backported i915 driver (i915_bpo) from 4.7, so try to replicate the problem with a mainline build: http://kernel.ubuntu.com/~kernel-ppa/mainline/ test with v4.7 first, and you only need to install 'linux-image-...-generic...' for your arch
Created attachment 126909 [details] Sept. 30 entries from /var/log/kern.log showing gpu hang Most recent event from kern.log attached. Similar to previous in the syslog. The "error" file was empty, so not attached: $ ll /sys/class/drm/card0/error -rw------- 1 root root 0 Sep 30 10:06 /sys/class/drm/card0/error Thanks for investigating.
(In reply to Mark from comment #3) > Created attachment 126909 [details] > Sept. 30 entries from /var/log/kern.log showing gpu hang > > Most recent event from kern.log attached. Similar to previous in the syslog. > The "error" file was empty, so not attached: > $ ll /sys/class/drm/card0/error > -rw------- 1 root root 0 Sep 30 10:06 /sys/class/drm/card0/error > > Thanks for investigating. Mark this is normal that it is indicated 0 because error state is going to dump dynamically, try: cat /sys/class/drm/card0/error | gzip > error.gz
Created attachment 126910 [details] cat /sys/class/drm/card0/error | gzip > error.gz
There were 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. In parallel, assigning to Mesa product (please let me know if I am mistaken with this GPU Hang). Kernel: 4.4.0-38-generic Platform: Haswell-ULT (pci id: 0x0a16) Mesa: [Please confirm your mesa version] From this error dump, hung is happening in render ring batch with active head at 0x00dd02ec, with 0x7a000003 (PIPE_CONTROL) as IPEHR. Batch extract (around 0x00dd02ec): 0x00dd02bc: 0x7b000005: 3DPRIMITIVE: 0x00dd02c0: 0x00000004: tri list sequential 0x00dd02c4: 0x00000006: vertex count 0x00dd02c8: 0x00000000: start vertex 0x00dd02cc: 0x00000001: instance count 0x00dd02d0: 0x00000000: start instance 0x00dd02d4: 0x00000000: index bias 0x00dd02d8: 0x7a000003: PIPE_CONTROL 0x00dd02dc: 0x00101c11: no write, cs stall, render target cache flush, instruction cache invalidate, texture cache invalidate, vf fetch invalidate, depth cache flush, 0x00dd02e0: 0x00000000: destination address 0x00dd02e4: 0x00000000: immediate dword low 0x00dd02e8: 0x00000000: immediate dword high 0x00dd02ec: 0x780e0000: 3DSTATE_CC_STATE_POINTERS 0x00dd02f0: 0x00007f01: pointer to COLOR_CALC_STATE at 0x00007f00 (changed) 0x00dd02f4: 0x7a000003: PIPE_CONTROL 0x00dd02f8: 0x00101000: no write, cs stall, render target cache flush, 0x00dd02fc: 0x00000000: destination address 0x00dd0300: 0x00000000: immediate dword low 0x00dd0304: 0x00000000: immediate dword high
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/772.
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.