Desktop Effects were Restarting due to graphcal reset in Kubuntu 16:04

[Murali krishnan]

Desktop effects got hung intermittently while browsing videos in browser. This is happening after Kernel Update, tried reinstalling xserver-xorg-video-intel package as per https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1575301 but it did not help either, I am using Kubuntu 16.04

dmesg output:

 1420.773494] [drm] GPU HANG: ecode 7:0:0x85dffffc, in kwin_x11 [2055], reason: Ring hung, action: reset
[ 1420.773496] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1420.773497] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1420.773497] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1420.773498] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1420.773499] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1420.775585] drm/i915: Resetting chip after gpu hang
[ 1522.762995] [drm] stuck on render ring
[ 1522.764133] [drm] GPU HANG: ecode 7:0:0x85dffffc, in kwin_x11 [2055], reason: Ring hung, action: reset
[ 1522.764305] ------------[ cut here ]------------
[ 1522.764366] WARNING: CPU: 1 PID: 3092 at /build/linux-W6HB68/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
[ 1522.764369] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
[ 1522.764371] Modules linked in:
[ 1522.764374] ipt_MASQUERADE nf_nat_masquerade_ipv4 vmw_vsock_vmci_transport vsock vmw_vmci iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs eeepc_wmi asus_wmi sparse_keymap snd_hda_codec_realtek snd_hda_codec_generic uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev snd_hda_intel snd_hda_codec intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_core snd_hwdep snd_pcm media snd_seq_midi snd_seq_midi_event snd_rawmidi kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_seq snd_seq_device snd_timer input_leds snd cryptd serio_raw soundcore shpchp tpm_infineon mei_me mei mac_hid 8250_fintek lpc_ich binfmt_misc
[ 1522.764437] nfsd auth_rpcgss nfs_acl lockd grace sunrpc parport_pc ppdev lp parport autofs4 hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper ahci libahci r8169 mii syscopyarea sysfillrect sysimgblt fb_sys_fops drm video fjes wmi
[ 1522.764468] CPU: 1 PID: 3092 Comm: kworker/1:1 Not tainted 4.4.0-62-generic #83-Ubuntu
[ 1522.764471] Hardware name: ASUS All Series/H81M-CS, BIOS 0401 03/09/2015
[ 1522.764515] Workqueue: events intel_mmio_flip_work_func [i915]
[ 1522.764518] 0000000000000286 000000008e417408 ffff880119f67d20 ffffffff813f7c63
[ 1522.764523] ffff880119f67d68 ffffffffc0203ab8 ffff880119f67d58 ffffffff810812d2
[ 1522.764528] ffff880048c039c0 ffff88011fb165c0 ffff88011fb1af00 0000000000000040
[ 1522.764532] Call Trace:
[ 1522.764540] [<ffffffff813f7c63>] dump_stack+0x63/0x90
[ 1522.764547] [<ffffffff810812d2>] warn_slowpath_common+0x82/0xc0
[ 1522.764551] [<ffffffff8108136c>] warn_slowpath_fmt+0x5c/0x80
[ 1522.764558] [<ffffffff8102d8c7>] ? __switch_to+0x437/0x5c0
[ 1522.764597] [<ffffffffc019cf3e>] intel_mmio_flip_work_func+0x38e/0x3d0 [i915]
[ 1522.764603] [<ffffffff8109a515>] process_one_work+0x165/0x480
[ 1522.764608] [<ffffffff8109a87b>] worker_thread+0x4b/0x4c0
[ 1522.764613] [<ffffffff8109a830>] ? process_one_work+0x480/0x480
[ 1522.764617] [<ffffffff8109a830>] ? process_one_work+0x480/0x480
[ 1522.764621] [<ffffffff810a0ba8>] kthread+0xd8/0xf0
[ 1522.764625] [<ffffffff810a0ad0>] ? kthread_create_on_node+0x1e0/0x1e0
[ 1522.764632] [<ffffffff8183898f>] ret_from_fork+0x3f/0x70
[ 1522.764636] [<ffffffff810a0ad0>] ? kthread_create_on_node+0x1e0/0x1e0
[ 1522.764640] ---[ end trace b709120738fd081c ]---
[ 1522.766309] drm/i915: Resetting chip after gpu hang

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1666365

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Murali krishnan (muralikris39)]

Changed in linux (Ubuntu):
status: New → Confirmed

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10

[Murali krishnan (muralikris39)]

@ Joseph Salisbury I am afraid to do so,since it is my personal desktop machine,Will there are any consequences while installing latest upstream kernel. How can i go back to current kernel after testing it with latest one if there are any issues. is it like we can uninstall upstream kernal after testing as per the section "Uninstalling upstream kernels".

 I have followed the steps till applying patches (upto 0006-configs-based-on-Ubuntu-4.10.0-6.8.patch) but bit hesitant to do the final step.

Below is my current kernel images:
dpkg --list | grep "linux-image"
rc linux-image-4.4.0-62-generic 4.4.0-62.83 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-63-generic 4.4.0-63.84 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-64-generic 4.4.0-64.85 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
rc linux-image-extra-4.4.0-62-generic 4.4.0-62.83 amd64 Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
ii linux-image-extra-4.4.0-63-generic 4.4.0-63.84 amd64 Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
ii linux-image-extra-4.4.0-64-generic 4.4.0-64.85 amd64 Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
ii linux-image-generic 4.4.0.64.68 amd64 Generic Linux kernel image

[Murali krishnan (muralikris39)]

Testing of Upstream kernel completed now, Bug is reproduced also in latest upstream kernel version:

dmesg command output:

[ 965.815868] [drm] GPU HANG: ecode 7:0:0x85dffffc, in kwin_x11 [2476], reason: Hang on render ring, action: reset
[ 965.815870] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 965.815871] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 965.815872] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 965.815872] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 965.815873] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 965.815931] drm/i915: Resetting chip after gpu hang
[ 981.835855] intel_pstate: Turbo disabled by BIOS or unavailable on processor
[ 985.774379] drm/i915: Resetting chip after gpu hang
[ 995.758768] drm/i915: Resetting chip after gpu hang
[ 999.769168] intel_pstate: Turbo disabled by BIOS or unavailable on processor
[ 1006.767233] drm/i915: Resetting chip after gpu hang
murali@murali-PC:~$ uname -r
4.10.0-041000-generic

[Murali krishnan (muralikris39)]

'kernel-bug-exists-upstream'.

[Joseph Salisbury (jsalisbury)]

Does this bug go away if you boot back into the kernel prior to the kernel update?

[Murali krishnan (muralikris39)]

Nope Same result

dmesg Output:

 5090.109460] [drm] GPU HANG: ecode 7:0:0x85dffffc, in kwin_x11 [2329], reason: Ring hung, action: reset
[ 5090.109465] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 5090.109468] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 5090.109470] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 5090.109472] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 5090.109475] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 5090.109658] ------------[ cut here ]------------
[ 5090.109758] WARNING: CPU: 0 PID: 3943 at /build/linux-1hW8mg/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
[ 5090.109762] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
[ 5090.109766] Modules linked in:
[ 5090.109770] ipt_MASQUERADE nf_nat_masquerade_ipv4 vmw_vsock_vmci_transport vsock vmw_vmci iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs eeepc_wmi asus_wmi sparse_keymap snd_hda_codec_realtek snd_hda_codec_generic uvcvideo snd_hda_intel videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_hda_codec videobuf2_core snd_hda_core snd_hwdep v4l2_common videodev snd_pcm snd_seq_midi snd_seq_midi_event media intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_rawmidi kvm snd_seq snd_seq_device snd_timer irqbypass snd crct10dif_pclmul crc32_pclmul soundcore ghash_clmulni_intel cryptd input_leds serio_raw lpc_ich tpm_infineon shpchp mei_me 8250_fintek mei mac_hid binfmt_misc
[ 5090.109852] nfsd auth_rpcgss nfs_acl lockd grace sunrpc parport_pc ppdev lp parport autofs4 hid_generic usbhid hid ahci libahci r8169 mii i915 wmi i2c_algo_bit fjes drm_kms_helper syscopyarea sysfillrect video sysimgblt fb_sys_fops drm
[ 5090.109891] CPU: 0 PID: 3943 Comm: kworker/0:2 Not tainted 4.4.0-64-generic #85-Ubuntu
[ 5090.109895] Hardware name: ASUS All Series/H81M-CS, BIOS 0401 03/09/2015
[ 5090.109950] Workqueue: events intel_mmio_flip_work_func [i915]
[ 5090.109954] 0000000000000286 0000000035a5cc36 ffff88005610bd20 ffffffff813f8083
[ 5090.109961] ffff88005610bd68 ffffffffc01c8ab8 ffff88005610bd58 ffffffff810812d2
[ 5090.109966] ffff88007b34cec0 ffff88011fa165c0 ffff88011fa1af00 0000000000000000
[ 5090.109972] Call Trace:
[ 5090.109983] [<ffffffff813f8083>] dump_stack+0x63/0x90
[ 5090.109992] [<ffffffff810812d2>] warn_slowpath_common+0x82/0xc0
[ 5090.109998] [<ffffffff8108136c>] warn_slowpath_fmt+0x5c/0x80
[ 5090.110005] [<ffffffff8102d8c7>] ? __switch_to+0x437/0x5c0
[ 5090.110057] [<ffffffffc0161f3e>] intel_mmio_flip_work_func+0x38e/0x3d0 [i915]
[ 5090.110065] [<ffffffff8109a515>] process_one_work+0x165/0x480
[ 5090.110071] [<ffffffff8109a87b>] worker_thread+0x4b/0x4c0
[ 5090.110077] [<ffffffff8109a830>] ? process_one_work+0x480/0x480
[ 5090.110083] [<ffffffff8109a830>] ? process_one_work+0x480/0x480
[ 5090.110088] [<f...

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel