Bug 96447 - GPU HANG: ecode 7:0:0x85dffff8, in krunner [1214], reason: Ring hung, action: reset
Summary: GPU HANG: ecode 7:0:0x85dffff8, in krunner [1214], reason: Ring hung, action:...
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) other
: medium normal
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
Depends on:
Reported: 2016-06-09 07:46 UTC by
Modified: 2019-09-25 18:56 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

GPU crash dump from /sys/class/drm/card0/error (3.05 MB, text/plain)
2016-06-09 07:46 UTC,

Description 2016-06-09 07:46:36 UTC
Created attachment 124410 [details]
GPU crash dump from /sys/class/drm/card0/error

Kubuntu 16.04 LTS on a early 2014 MacBook Air. (Intel HD Graphics 5000)

[29404.084025] [drm] stuck on render ring
[29404.084979] [drm] GPU HANG: ecode 7:0:0x85dffff8, in krunner [1214], reason: Ring hung, action: reset
[29404.084981] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[29404.084982] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[29404.084984] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[29404.084985] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[29404.084987] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[29404.085027] ------------[ cut here ]------------
[29404.085084] WARNING: CPU: 3 PID: 13163 at /build/linux-FvcHlK/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11287 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
[29404.085088] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
[29404.085090] Modules linked in:
[29404.085093]  rfcomm bnep binfmt_misc nls_iso8859_1 joydev applesmc input_polldev snd_hda_codec_hdmi snd_hda_codec_cirrus intel_rapl snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_intel kvm snd_hda_codec snd_hda_core snd_hwdep irqbypass snd_pcm wl(POE) snd_seq_midi btusb snd_seq_midi_event cfg80211 btrtl btbcm thunderbolt snd_rawmidi btintel input_leds bluetooth bdc_pci mei_me lpc_ich shpchp mei snd_seq dw_dmac_pci bcm5974 dw_dmac_core snd_seq_device snd_timer snd soundcore sbs sbshc acpi_als kfifo_buf industrialio spi_pxa2xx_platform mac_hid apple_bl parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic hid_apple usbhid hid crct10dif_pclmul crc32_pclmul i915 aesni_intel aes_x86_64 lrw gf128mul glue_helper i2c_algo_bit
[29404.085171]  ablk_helper cryptd drm_kms_helper syscopyarea sysfillrect uas sysimgblt ahci fb_sys_fops libahci drm usb_storage fjes video
[29404.085188] CPU: 3 PID: 13163 Comm: kworker/3:1 Tainted: P           OE   4.4.0-22-generic #40-Ubuntu
[29404.085191] Hardware name: Apple Inc. MacBookAir6,2/Mac-7DF21CB3ED6977E5, BIOS MBA61.88Z.0099.B19.1506050547 06/05/2015
[29404.085236] Workqueue: events intel_mmio_flip_work_func [i915]
[29404.085240]  0000000000000286 00000000d57500ad ffff8800535d3d20 ffffffff813e9c53
[29404.085245]  ffff8800535d3d68 ffffffffc02fca50 ffff8800535d3d58 ffffffff81080fb2
[29404.085250]  ffff88016742cd80 ffff88016f2d6500 ffff88016f2dae00 00000000000000c0
[29404.085255] Call Trace:
[29404.085275]  [<ffffffff813e9c53>] dump_stack+0x63/0x90
[29404.085282]  [<ffffffff81080fb2>] warn_slowpath_common+0x82/0xc0
[29404.085287]  [<ffffffff8108104c>] warn_slowpath_fmt+0x5c/0x80
[29404.085294]  [<ffffffff8102d8c7>] ? __switch_to+0x437/0x5c0
[29404.085338]  [<ffffffffc0295c9e>] intel_mmio_flip_work_func+0x38e/0x3d0 [i915]
[29404.085345]  [<ffffffff8109a052>] process_one_work+0x162/0x480
[29404.085350]  [<ffffffff8109a3bb>] worker_thread+0x4b/0x4c0
[29404.085356]  [<ffffffff8109a370>] ? process_one_work+0x480/0x480
[29404.085361]  [<ffffffff8109a370>] ? process_one_work+0x480/0x480
[29404.085365]  [<ffffffff810a0588>] kthread+0xd8/0xf0
[29404.085370]  [<ffffffff810a04b0>] ? kthread_create_on_node+0x1e0/0x1e0
[29404.085375]  [<ffffffff8182568f>] ret_from_fork+0x3f/0x70
[29404.085380]  [<ffffffff810a04b0>] ? kthread_create_on_node+0x1e0/0x1e0
[29404.085384] ---[ end trace f5619ae4144d6ab4 ]---
[29404.086563] drm/i915: Resetting chip after gpu hang
[29410.095450] [drm] stuck on render ring
[29410.096726] [drm] GPU HANG: ecode 7:0:0x85dffff8, in krunner [1214], reason: Ring hung, action: reset
[29410.099192] drm/i915: Resetting chip after gpu hang
Comment 1 Elizabeth 2018-03-21 23:10:38 UTC
Hi, it seems that no new reports on this case were added since its opening. Were you able to fix it by for example updating or upgrading any component? Thank you.
Comment 2 GitLab Migration User 2019-09-25 18:56:47 UTC
-- 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/1522.

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.