Bug 97268 - [HSW GT2] GPU HANG in gnome-shell
Summary: [HSW GT2] GPU HANG in gnome-shell
Status: RESOLVED WORKSFORME
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-09 21:45 UTC by Riemer Palstra
Modified: 2016-11-01 23:49 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
[drm] GPU crash dump saved to /sys/class/drm/card1/error (bzip2 compressed) (249.40 KB, application/x-bzip)
2016-08-09 21:45 UTC, Riemer Palstra
Details

Description Riemer Palstra 2016-08-09 21:45:35 UTC
Created attachment 125653 [details]
[drm] GPU crash dump saved to /sys/class/drm/card1/error (bzip2 compressed)

[15850.745986] ------------[ cut here ]------------
[15850.746028] WARNING: CPU: 3 PID: 8716 at drivers/gpu/drm/i915/intel_display.c:11405 intel_mmio_flip_work_func+0x48f/0x4c0 [i915]
[15850.746031] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, ((void *)0), &mmio_flip->i915->rps.mmioflips))
[15850.746033] Modules linked in:
[15850.746036]  rfcomm fuse ccm xt_addrtype br_netfilter vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_broute bridge ebtable_nat ip6table_security ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle iptable_security iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep vfat fat arc4 intel_rapl x86_pkg_temp_thermal coretemp uvcvideo kvm_intel videobuf2_vmalloc videobuf2_memops iTCO_wdt videobuf2_v4l2 iTCO_vendor_support kvm videobuf2_core mei_wdt iwlmvm irqbypass crct10dif_pclmul crc32_pclmul mac80211
[15850.746089]  videodev ghash_clmulni_intel snd_hda_codec_realtek btusb snd_hda_codec_hdmi snd_hda_codec_generic iwlwifi btrtl btbcm media btintel bluetooth joydev i2c_i801 cfg80211 snd_hda_intel rtsx_pci_ms snd_hda_codec cdc_acm snd_hda_core memstick lpc_ich snd_hwdep snd_seq snd_seq_device snd_pcm ie31200_edac edac_core mei_me mei thinkpad_acpi snd_timer shpchp snd soundcore rfkill tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc cdc_mbim cdc_wdm cdc_ncm usbnet mii 8021q garp stp llc mrp nouveau i915 rtsx_pci_sdmmc mmc_core mxm_wmi ttm i2c_algo_bit drm_kms_helper crc32c_intel drm e1000e serio_raw rtsx_pci ptp pps_core wmi fjes video overlay
[15850.746145] CPU: 3 PID: 8716 Comm: kworker/3:1 Not tainted 4.6.5-300.fc24.x86_64 #1
[15850.746146] Hardware name: LENOVO 20BE00B8MS/20BE00B8MS, BIOS GMET70WW (2.18 ) 03/05/2015
[15850.746171] Workqueue: events intel_mmio_flip_work_func [i915]
[15850.746173]  0000000000000286 000000001cba4960 ffff880404fdbd10 ffffffff813dbcef
[15850.746176]  ffff880404fdbd60 0000000000000000 ffff880404fdbd50 ffffffff810a741b
[15850.746178]  00002c8d04fdbd20 ffff8802bcab0840 ffff8802a826af80 ffff8803fc106880
[15850.746181] Call Trace:
[15850.746186]  [<ffffffff813dbcef>] dump_stack+0x63/0x84
[15850.746190]  [<ffffffff810a741b>] __warn+0xcb/0xf0
[15850.746192]  [<ffffffff810a749f>] warn_slowpath_fmt+0x5f/0x80
[15850.746214]  [<ffffffffc0228eaf>] intel_mmio_flip_work_func+0x48f/0x4c0 [i915]
[15850.746218]  [<ffffffff810c0d74>] process_one_work+0x184/0x440
[15850.746221]  [<ffffffff810c107e>] worker_thread+0x4e/0x480
[15850.746224]  [<ffffffff810c1030>] ? process_one_work+0x440/0x440
[15850.746227]  [<ffffffff810c1030>] ? process_one_work+0x440/0x440
[15850.746229]  [<ffffffff810c6f78>] kthread+0xd8/0xf0
[15850.746232]  [<ffffffff817e1002>] ret_from_fork+0x22/0x40
[15850.746235]  [<ffffffff810c6ea0>] ? kthread_worker_fn+0x180/0x180
[15850.746237] ---[ end trace c2d62b011332b411 ]---
Comment 1 Ted 2016-08-12 14:43:15 UTC
I have the same problem.
I am currently using the 4.5.7 kernel.
I have not been able to use 4.6.4 or 4.6.5 kernels due to this problem.
Comment 2 Ted 2016-08-12 14:44:26 UTC
Aug 12 08:06:13 HP_17 kernel: [drm] stuck on render ring
Aug 12 08:06:13 HP_17 kernel: [drm] GPU HANG: ecode 8:0:0xf25dffff, reason: Ring hung, action: reset
Aug 12 08:06:13 HP_17 kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Aug 12 08:06:13 HP_17 kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Aug 12 08:06:13 HP_17 kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Aug 12 08:06:13 HP_17 kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Aug 12 08:06:13 HP_17 kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Aug 12 08:06:13 HP_17 kernel: drm/i915: Resetting chip after gpu hang
Comment 3 Chris Wilson 2016-08-12 17:01:57 UTC
(In reply to Ted from comment #2)
> Aug 12 08:06:13 HP_17 kernel: [drm] stuck on render ring
> Aug 12 08:06:13 HP_17 kernel: [drm] GPU HANG: ecode 8:0:0xf25dffff, reason:
> Ring hung, action: reset

That's a different issue (different hw with correspondingly different sw).
Comment 4 Kenneth Graunke 2016-08-12 23:57:14 UTC
Riemer, what version of Mesa are you using?
Comment 5 Riemer Palstra 2016-08-13 11:34:48 UTC
Mesa 12.0.1.
Comment 6 Matt Turner 2016-10-25 18:59:09 UTC
We don't have enough information.

- What kernel version are you using? (uname -a)
- What were you doing at the time of the hang? Is it reproducible?
Comment 7 Riemer Palstra 2016-11-01 22:29:30 UTC
Well, that was some time ago, currently I'm running:

# uname -a
Linux t540p.palstra.com 4.8.4-200.fc24.x86_64 #1 SMP Tue Oct 25 13:06:04 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

In August, when this was reported, I was probably running kernel 4.6.4-301.fc24.x86_64.

I haven't had the hang since then, but will report if it happens again of course.
Comment 8 Matt Turner 2016-11-01 23:49:56 UTC
Thanks. Please reopen if you can reproduce.


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.