Bug 91007 - [HSW] GPU HANG: ecode 7:0:0x85dffffc, in Xorg [1090], reason: Ring hung, action: reset
Summary: [HSW] GPU HANG: ecode 7:0:0x85dffffc, in Xorg [1090], reason: Ring hung, acti...
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: 12.0
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-17 10:37 UTC by Presian Yankulov
Modified: 2017-02-10 22:39 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error (472.08 KB, text/plain)
2015-06-17 10:38 UTC, Presian Yankulov
Details
/sys/class/drm/card0/error output (472.08 KB, application/gzip)
2015-06-17 10:43 UTC, Presian Yankulov
Details
/sys/class/drm/card0/error output on Ubuntu 16.04 (3.01 MB, text/plain)
2016-05-09 21:32 UTC, Eric Piel
Details
/sys/class/drm/card0/error (709.00 KB, text/plain)
2016-09-19 08:22 UTC, Łukasz Żarnowiecki
Details

Description Presian Yankulov 2015-06-17 10:37:01 UTC
dmesg log:
[11895.573925] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=714513 end=714514)
[13158.412791] [drm] stuck on render ring
[13158.413745] [drm] GPU HANG: ecode 7:0:0x85dffffc, in Xorg [1090], reason: Ring hung, action: reset
[13158.413747] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[13158.413747] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[13158.413748] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[13158.413749] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[13158.413749] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[13158.415765] drm/i915: Resetting chip after gpu hang

uname -a:
4.0.5-300.fc22.x86_64 #1 SMP Mon Jun 8 16:15:26 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

hardware:
Asus G551JM
Comment 1 Presian Yankulov 2015-06-17 10:38:45 UTC
Created attachment 116553 [details]
/sys/class/drm/card0/error

/sys/class/drm/card0/error
Comment 2 Presian Yankulov 2015-06-17 10:43:19 UTC
Created attachment 116554 [details]
/sys/class/drm/card0/error output
Comment 3 Chris Wilson 2015-06-17 10:46:14 UTC
The hang looks deep inside a mesa batch. First task is to find which application submitted that batch and how to reproduce the hang.
Comment 4 Presian Yankulov 2015-06-17 10:52:55 UTC
Hi,

I'm kinda new in this stuff. Can you guide me how to do it ?
Comment 5 Eric Piel 2016-05-09 21:31:54 UTC
I have something similar here, on a kernel 4.4.0 64 bits (from Ubuntu).

This happens easily when using LibreOffice (v5.1.2), with Unity 7 as window/composite manager.

This happens only since I've uninstalled 'xserver-xorg-video-intel', so Xorg is using the modesetting module.

[   65.889647] [drm] stuck on render ring
[   65.890482] [drm] GPU HANG: ecode 7:0:0x86d2fffd, in Xorg [1090], reason: Ring hung, action: reset
[   65.890531] ------------[ cut here ]------------
[   65.890583] WARNING: CPU: 3 PID: 305 at /build/linux-UbQGH5/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11287 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
[   65.890586] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
[   65.890588] Modules linked in:
[   65.890590]  bnep binfmt_misc nls_iso8859_1 arc4 snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm irqbypass iwlmvm crct10dif_pclmul crc32_pclmul mac80211 aesni_intel uvcvideo aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_core hid_sensor_gyro_3d iwlwifi bluetooth snd_hda_codec_conexant snd_hda_codec_generic v4l2_common hid_sensor_als hid_sensor_rotation hid_sensor_accel_3d hid_sensor_magn_3d videodev cfg80211 hid_sensor_incl_3d hid_sensor_trigger snd_hda_intel snd_hda_codec industrialio_triggered_buffer kfifo_buf industrialio hid_multitouch snd_hda_core snd_hwdep hid_sensor_iio_common media snd_pcm joydev input_leds serio_raw snd_seq_midi snd_seq_midi_event snd_rawmidi rtsx_pci_ms
[   65.890644]  memstick snd_seq thinkpad_acpi shpchp snd_seq_device nvram snd_timer lpc_ich mei_me mei snd soundcore mac_hid intel_smartconnect soc_button_array parport_pc ppdev lp parport autofs4 hid_generic wacom bcache hid_sensor_custom hid_sensor_hub usbhid hid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci drm libahci rtsx_pci wmi fjes video
[   65.890673] CPU: 3 PID: 305 Comm: kworker/3:3 Not tainted 4.4.0-22-generic #39-Ubuntu
[   65.890675] Hardware name: LENOVO 20CD000MMH/20CD000MMH, BIOS GQET46WW (1.26 ) 07/29/2015
[   65.890709] Workqueue: events intel_mmio_flip_work_func [i915]
[   65.890711]  0000000000000286 000000009e71badf ffff880211013d20 ffffffff813e9c53
[   65.890715]  ffff880211013d68 ffffffffc022ba50 ffff880211013d58 ffffffff81080fb2
[   65.890717]  ffff8800d09a9100 ffff88021f2d6500 ffff88021f2dae00 00000000000000c0
[   65.890720] Call Trace:
[   65.890727]  [<ffffffff813e9c53>] dump_stack+0x63/0x90
[   65.890731]  [<ffffffff81080fb2>] warn_slowpath_common+0x82/0xc0
[   65.890734]  [<ffffffff8108104c>] warn_slowpath_fmt+0x5c/0x80
[   65.890739]  [<ffffffff8102d8c7>] ? __switch_to+0x437/0x5c0
[   65.890768]  [<ffffffffc01c4c9e>] intel_mmio_flip_work_func+0x38e/0x3d0 [i915]
[   65.890772]  [<ffffffff8109a052>] process_one_work+0x162/0x480
[   65.890775]  [<ffffffff8109a3bb>] worker_thread+0x4b/0x4c0
[   65.890778]  [<ffffffff8109a370>] ? process_one_work+0x480/0x480
[   65.890781]  [<ffffffff8109a370>] ? process_one_work+0x480/0x480
[   65.890783]  [<ffffffff810a0588>] kthread+0xd8/0xf0
[   65.890786]  [<ffffffff810a04b0>] ? kthread_create_on_node+0x1e0/0x1e0
[   65.890789]  [<ffffffff8182568f>] ret_from_fork+0x3f/0x70
[   65.890792]  [<ffffffff810a04b0>] ? kthread_create_on_node+0x1e0/0x1e0
[   65.890794] ---[ end trace 0700032d2f603712 ]---
[   65.892594] drm/i915: Resetting chip after gpu hang
[   66.702516] show_signal_msg: 48 callbacks suppressed
Comment 6 Eric Piel 2016-05-09 21:32:50 UTC
Created attachment 123584 [details]
/sys/class/drm/card0/error output on Ubuntu 16.04
Comment 7 Łukasz Żarnowiecki 2016-09-19 08:20:52 UTC
Same happened on 4.7.4 kernel with mesa 12.0.3 when using mysql-workbench.

[ 2307.465209] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=139194 end=139195) time 159 us, min 1073, max 1079, scanline start 1070, end 1080
[ 2495.103306] [drm] stuck on render ring
[ 2495.108857] [drm] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [472], reason: Engine(s) hung, action: reset
[ 2495.108859] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 2495.108860] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 2495.108860] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 2495.108861] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 2495.108862] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 2495.111107] drm/i915: Resetting chip after gpu hang
[ 2497.103798] [drm] RC6 on
Comment 8 Łukasz Żarnowiecki 2016-09-19 08:22:42 UTC
Created attachment 126613 [details]
/sys/class/drm/card0/error
Comment 9 Matt Turner 2016-11-03 02:24:13 UTC
Can someone capture and upload an apitrace (https://github.com/apitrace/apitrace) that reproduces the issue? Tell us how to reproduce? Try mesa-13.0.0?

Please test a new version of Mesa (13.0.0) and mark as REOPENED
if you can reproduce and RESOLVED/* if you cannot reproduce.
Comment 10 Annie 2017-02-10 22:39:20 UTC
Dear Reporter,

This Mesa bug has been in the "NEEDINFO" status for over 60 days. I am closing this bug based on lack of response but feel free to reopen if resolution is still needed. Please ensure you're supplying the correct information as requested.

Thank you.


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.