Bug 98151 - GPU hang
Summary: GPU hang
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-07 15:45 UTC by Lee Revell
Modified: 2016-10-10 15:46 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features: GPU hang


Attachments
Non-wordwrapped crash (4.71 KB, text/plain)
2016-10-07 15:46 UTC, Lee Revell
no flags Details

Description Lee Revell 2016-10-07 15:45:08 UTC
Sep 29 19:14:01 localhost kernel: [27470.107412] [drm] stuck on render ring
Sep 29 19:14:01 localhost kernel: [27470.108470] [drm] GPU HANG: ecode 7:0:0x85dffff8, in chromium-browse [3894], reason: Ring hung, action: reset
Sep 29 19:14:01 localhost kernel: [27470.108473] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Sep 29 19:14:01 localhost kernel: [27470.108474] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Sep 29 19:14:01 localhost kernel: [27470.108476] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Sep 29 19:14:01 localhost kernel: [27470.108477] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Sep 29 19:14:01 localhost kernel: [27470.108479] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Sep 29 19:14:01 localhost kernel: [27470.108495] ------------[ cut here ]------------
Sep 29 19:14:01 localhost kernel: [27470.108548] WARNING: CPU: 0 PID: 1217 at /build/linux-R0TiM8/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11309 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
Sep 29 19:14:01 localhost kernel: [27470.108551] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
Sep 29 19:14:01 localhost kernel: [27470.108554] Modules linked in: snd_seq_dummy ctr ccm rfcomm bnep dell_laptop dell_wmi sparse_keymap intel_rapl dcdbas x86_pkg_temp_thermal ax88179_178a usbnet intel_powerclamp mii coretemp dell_smm_hwmon drbg ansi_cprng kvm_intel dm_crypt kvm btusb btrtl btbcm irqbypass btintel crct10dif_pclmul crc32_pclmul bluetooth aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd arc4 iwldvm mac80211 iwlwifi snd_soc_rt5640 snd_soc_rl6231 joydev snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic input_leds serio_raw cfg80211 snd_soc_core snd_hda_intel snd_hda_codec snd_hda_core snd_compress snd_hwdep ac97_bus snd_pcm_dmaengine snd_seq_midi lpc_ich snd_pcm snd_seq_midi_event snd_rawmidi snd_seq mei_me ie31200_edac snd_seq_device mei shpchp edac_core snd_timer snd soundcore elan_i2c 8250_fintek dell_smo8800 i2c_designware_platform dw_dmac dw_dmac_core i2c_designware_core dell_rbtn binfmt_misc 8250_dw mac_hid spi_pxa2xx_platform snd_soc_sst_acpi parport_pc ppdev lp parport autofs4 hid_generic usbhid i915 psmouse i2c_algo_bit drm_kms_helper syscopyarea e1000e sysfillrect ahci sysimgblt fb_sys_fops libahci drm sdhci_pci ptp pps_core wmi video sdhci_acpi i2c_hid sdhci hid fjes
Sep 29 19:14:01 localhost kernel: [27470.108663] CPU: 0 PID: 1217 Comm: kworker/0:3 Not tainted 4.4.0-38-generic #57-Ubuntu
Sep 29 19:14:01 localhost kernel: [27470.108665] Hardware name: Dell Inc. Latitude E6440/0YX2X3, BIOS A10 02/02/2015
Sep 29 19:14:01 localhost kernel: [27470.108701] Workqueue: events intel_mmio_flip_work_func [i915]
Sep 29 19:14:01 localhost kernel: [27470.108704]  0000000000000286 00000000148b2af8 ffff88032f36fd20 ffffffff813f1b73
Sep 29 19:14:01 localhost kernel: [27470.108708]  ffff88032f36fd68 ffffffffc02cdab8 ffff88032f36fd58 ffffffff810811c2
Sep 29 19:14:01 localhost kernel: [27470.108711]  ffff88040af30d40 ffff88041ea16500 ffff88041ea1ae00 0000000000000000
Sep 29 19:14:01 localhost kernel: [27470.108715] Call Trace:
Sep 29 19:14:01 localhost kernel: [27470.108723]  [<ffffffff813f1b73>] dump_stack+0x63/0x90
Sep 29 19:14:01 localhost kernel: [27470.108729]  [<ffffffff810811c2>] warn_slowpath_common+0x82/0xc0
Sep 29 19:14:01 localhost kernel: [27470.108732]  [<ffffffff8108125c>] warn_slowpath_fmt+0x5c/0x80
Sep 29 19:14:01 localhost kernel: [27470.108737]  [<ffffffff8102d8c7>] ? __switch_to+0x437/0x5c0
Sep 29 19:14:01 localhost kernel: [27470.108771]  [<ffffffffc0266f0e>] intel_mmio_flip_work_func+0x38e/0x3d0 [i915]
Sep 29 19:14:01 localhost kernel: [27470.108777]  [<ffffffff8109a395>] process_one_work+0x165/0x480
Sep 29 19:14:01 localhost kernel: [27470.108783]  [<ffffffff8109a6fb>] worker_thread+0x4b/0x4c0
Sep 29 19:14:01 localhost kernel: [27470.108788]  [<ffffffff8109a6b0>] ? process_one_work+0x480/0x480
Sep 29 19:14:01 localhost kernel: [27470.108791]  [<ffffffff8109a6b0>] ? process_one_work+0x480/0x480
Sep 29 19:14:01 localhost kernel: [27470.108795]  [<ffffffff810a08d8>] kthread+0xd8/0xf0
Sep 29 19:14:01 localhost kernel: [27470.108798]  [<ffffffff810a0800>] ? kthread_create_on_node+0x1e0/0x1e0
Sep 29 19:14:01 localhost kernel: [27470.108803]  [<ffffffff81830a8f>] ret_from_fork+0x3f/0x70
Sep 29 19:14:01 localhost kernel: [27470.108806]  [<ffffffff810a0800>] ? kthread_create_on_node+0x1e0/0x1e0
Sep 29 19:14:01 localhost kernel: [27470.108823] ---[ end trace a32bec2dacf1e68f ]---
Sep 29 19:14:01 localhost kernel: [27470.111665] drm/i915: Resetting chip after gpu hang
Comment 1 Lee Revell 2016-10-07 15:46:21 UTC
Created attachment 127105 [details]
Non-wordwrapped crash
Comment 2 yann 2016-10-10 15:37:44 UTC
The information you are attaching is not enough to proceed here. As advised in the kernel log, can you attach gpu crash dump ? 
Once you see that a gpu hang is happening, execute the following to get this dump (and then attached to this bug):

cat /sys/class/drm/card0/error | gzip > error.gz
Comment 3 Lee Revell 2016-10-10 15:40:00 UTC
That file was empty by the time I got around to reporting the bug. Unless you have an idea of where Ubuntu 16.04 might have saved it, then you can close this bug.
Comment 4 yann 2016-10-10 15:46:24 UTC
(In reply to Lee Revell from comment #3)
> That file was empty by the time I got around to reporting the bug. Unless
> you have an idea of where Ubuntu 16.04 might have saved it, then you can
> close this bug.

The gpu error state is dumped dynamically and except by invoking that dump, it is not saved likes some log such as kernel. I don't think that Ubuntu is dumping and keeping it.

So I am closing it for now, but don't hesitate to re-open if this is occurring again.


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.