Bug 102397 - [HSW] GPU HANG: ecode 7:0:0x84dfbffe, in chrome [32469], reason: Ring hung, action: reset
Summary: [HSW] GPU HANG: ecode 7:0:0x84dfbffe, in chrome [32469], reason: Ring hung, a...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-24 22:09 UTC by Peter Goodman
Modified: 2018-06-15 21:10 UTC (History)
2 users (show)

See Also:
i915 platform: HSW
i915 features: GPU hang


Attachments
/var/log/kern.log (377.77 KB, text/x-log)
2017-08-25 19:05 UTC, Peter Goodman
no flags Details

Description Peter Goodman 2017-08-24 22:09:19 UTC
Linux sloth 4.4.14-040414-generic #201606241434 SMP Fri Jun 24 18:36:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Hardware:
System76 Gazelle Professional, model gazp9b
Intel® Core™ i7-4910MQ CPU @ 2.90GHz × 8 

Graphics:
Intel® Haswell Mobile 
Using the System76 driver 14.04.32

Note:
I recently upgraded the kernel version 4.4 (from Canonical) to be able to use an Eizo monitor.

From dmesg:

[139231.105009] [drm] stuck on render ring
[139231.105875] [drm] GPU HANG: ecode 7:0:0x84dfbffe, in chrome [32469], reason: Ring hung, action: reset
[139231.105877] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[139231.105878] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[139231.105879] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[139231.105880] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[139231.105881] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[139231.105909] ------------[ cut here ]------------
[139231.105956] WARNING: CPU: 0 PID: 23745 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:11289 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
[139231.105958] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
[139231.105959] Modules linked in:
[139231.105961]  sctp libcrc32c nls_iso8859_1 uas usb_storage ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 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 overlay vmnet(OE) vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) drbg ansi_cprng ctr ccm rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) ec_sys bnep vboxdrv(OE) binfmt_misc arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi snd_hda_codec_via snd_hda_codec_generic kvm_intel uvcvideo videobuf2_vmalloc videobuf2_memops kvm videobuf2_v4l2 videobuf2_core snd_hda_intel v4l2_common videodev snd_hda_codec media irqbypass snd_hda_core snd_hwdep btusb btrtl
[139231.106032]  crct10dif_pclmul btbcm crc32_pclmul snd_pcm btintel aesni_intel iwlmvm bluetooth aes_x86_64 lrw gf128mul glue_helper mac80211 ablk_helper cryptd snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev input_leds iwlwifi snd_seq_device serio_raw snd_timer cfg80211 rtsx_pci_ms memstick snd lpc_ich mei_me soundcore mei ie31200_edac shpchp edac_core tpm_infineon mac_hid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid hid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci r8169 drm libahci rtsx_pci mii wmi video fjes
[139231.106090] CPU: 0 PID: 23745 Comm: kworker/0:1 Tainted: G     U  W  OE   4.4.14-040414-generic #201606241434
[139231.106092] Hardware name: System76, Inc.                   Gazelle Professional            /Gazelle Professional           , BIOS 1.03.06RS761 07/28/2014
[139231.106123] Workqueue: events intel_mmio_flip_work_func [i915]
[139231.106125]  0000000000000286 00000000062d5bf4 ffff880210087d20 ffffffff813d0743
[139231.106129]  ffff880210087d68 ffffffffc025cae8 ffff880210087d58 ffffffff8107ff12
[139231.106133]  ffff8802f65176c0 ffff88041fa16300 ffff88041fa1ac00 0000000000000000
[139231.106137] Call Trace:
[139231.106144]  [<ffffffff813d0743>] dump_stack+0x63/0x90
[139231.106150]  [<ffffffff8107ff12>] warn_slowpath_common+0x82/0xc0
[139231.106154]  [<ffffffff8107ffac>] warn_slowpath_fmt+0x5c/0x80
[139231.106158]  [<ffffffff810168c7>] ? __switch_to+0x437/0x5c0
[139231.106185]  [<ffffffffc01f5bfe>] intel_mmio_flip_work_func+0x38e/0x3d0 [i915]
[139231.106189]  [<ffffffff81098f45>] process_one_work+0x165/0x480
[139231.106191]  [<ffffffff810992ab>] worker_thread+0x4b/0x4c0
[139231.106194]  [<ffffffff81099260>] ? process_one_work+0x480/0x480
[139231.106196]  [<ffffffff81099260>] ? process_one_work+0x480/0x480
[139231.106200]  [<ffffffff8109f448>] kthread+0xd8/0xf0
[139231.106203]  [<ffffffff8109f370>] ? kthread_create_on_node+0x1a0/0x1a0
[139231.106207]  [<ffffffff81808b0f>] ret_from_fork+0x3f/0x70
[139231.106210]  [<ffffffff8109f370>] ? kthread_create_on_node+0x1a0/0x1a0
[139231.106212] ---[ end trace 8f4ec287e4f1f5de ]---
[139231.108037] drm/i915: Resetting chip after gpu hang
Comment 1 Elizabeth 2017-08-25 18:37:48 UTC
Hello, could you please attach error state: /sys/class/drm/card0/error and full dmesg. Thank you.
Comment 2 Peter Goodman 2017-08-25 19:05:48 UTC
Created attachment 133787 [details]
/var/log/kern.log
Comment 3 Peter Goodman 2017-08-25 19:07:05 UTC
Unfortunately I had to reboot for other reasons so I lost /sys/class/drm/card0/error :-(

D'oh I should have noticed the message in the log that said I should attach it.
Comment 4 Elizabeth 2017-10-26 20:22:50 UTC
Hello Peter, can you try to reproduce with latest stable or mainline, and if possible share a log with debug information (drm.debug=0x1e log_bug_len=2M on grub) or error state. Thank you.
https://www.kernel.org
Comment 5 Jani Saarinen 2018-03-29 07:11:22 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 6 Jani Saarinen 2018-04-20 14:22:18 UTC
Closing, please re-open if still occurs.


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.