Bug 96891 - GPU hang after resuming from suspend
Summary: GPU hang after resuming from suspend
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: low normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-11 07:57 UTC by 林博仁
Modified: 2017-02-10 22:38 UTC (History)
1 user (show)

See Also:
i915 platform: HSW
i915 features: GPU hang, power/suspend-resume


Attachments
GPU crash dump (313.61 KB, application/x-bzip)
2016-07-11 07:57 UTC, 林博仁
Details

Description 林博仁 2016-07-11 07:57:05 UTC
Recieve GPU hang message after playing a video, pause/stop it, suspend to ram then resume.  GPU dump attached.

Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857108] ------------[ cut here ]------------
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857144] WARNING: CPU: 3 PID: 12590 at /build/linux-BvkamA/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11287 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857146] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857148] Modules linked in: uas usb_storage nvram msr vmw_vsock_vmci_transport vsock vmw_vmci bnep xt_multiport iptable_filter ip_tables x_tables input_leds joydev pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bluetooth binfmt_misc nls_utf8 nls_cp950 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul aesni_intel snd_hda_codec_hdmi aes_x86_64 lrw gf128mul snd_hda_codec_realtek glue_helper ablk_helper snd_hda_codec_generic cryptd snd_soc_rt5640 serio_raw snd_soc_ssm4567 snd_hda_intel snd_soc_rl6231 snd_soc_core snd_hda_codec snd_compress snd_hda_core ac97_bus snd_hwdep snd_pcm_dmaengine lpc_ich snd_pcm mei_me mei snd_seq_midi shpchp snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer elan_i2c snd soundcore dw_dmac dw_dmac_core i2c_designware_platform i2c_designware_core 8250_dw spi_pxa2xx_platform snd_soc_sst_acpi mac_hid kvm_intel acpi_pad intel_smartconnect kvm irqbypass parport_pc ppdev lp parport autofs4 hid_generic usbhid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt psmouse fb_sys_fops ahci drm r8169 libahci mii video sdhci_acpi sdhci fjes i2c_hid hid
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857205] CPU: 3 PID: 12590 Comm: kworker/3:0 Tainted: G           OE   4.4.0-28-generic #47-Ubuntu
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857206] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H97M Anniversary, BIOS P2.10 07/27/2015
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857227] Workqueue: events intel_mmio_flip_work_func [i915]
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857229]  0000000000000286 0000000039b94e21 ffff880160237d20 ffffffff813eb1a3
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857231]  ffff880160237d68 ffffffffc0265a70 ffff880160237d58 ffffffff81081102
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857233]  ffff880026434e00 ffff88041fb96500 ffff88041fb9ae00 00000000000000c0
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857235] Call Trace:
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857240]  [<ffffffff813eb1a3>] dump_stack+0x63/0x90
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857244]  [<ffffffff81081102>] warn_slowpath_common+0x82/0xc0
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857246]  [<ffffffff8108119c>] warn_slowpath_fmt+0x5c/0x80
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857249]  [<ffffffff8102d8c7>] ? __switch_to+0x437/0x5c0
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857268]  [<ffffffffc01fedfe>] intel_mmio_flip_work_func+0x38e/0x3d0 [i915]
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857271]  [<ffffffff8109a2c5>] process_one_work+0x165/0x480
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857273]  [<ffffffff8109a62b>] worker_thread+0x4b/0x4c0
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857275]  [<ffffffff8109a5e0>] ? process_one_work+0x480/0x480
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857277]  [<ffffffff8109a5e0>] ? process_one_work+0x480/0x480
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857279]  [<ffffffff810a0808>] kthread+0xd8/0xf0
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857281]  [<ffffffff810a0730>] ? kthread_create_on_node+0x1e0/0x1e0
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857284]  [<ffffffff81827a4f>] ret_from_fork+0x3f/0x70
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857285]  [<ffffffff810a0730>] ? kthread_create_on_node+0x1e0/0x1e0
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.857287] ---[ end trace 4021392db79d33d1 ]---
Jul 11 13:58:00 Buo-Ren-SSD-B kernel: [75922.859182] drm/i915: Resetting chip after gpu hang
Jul 11 13:58:06 Buo-Ren-SSD-B kernel: [75928.855663] [drm] stuck on render ring
Jul 11 13:58:06 Buo-Ren-SSD-B kernel: [75928.856314] [drm] GPU HANG: ecode 7:0:0x85dffffc, in totem [15837], reason: Ring hung, action: reset
Jul 11 13:58:06 Buo-Ren-SSD-B kernel: [75928.856359] ------------[ cut here ]------------

Operating System: Ubuntu 16.04 AMD64
Linux Kernel: 4.4.0-28-generic from Ubuntu software archive
xserver-xorg-video-driver: 2.99.917+git1607041932.26f8ab~gd~x from [Updated and Optimized Open Graphics Drivers : Oibaf](https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers)
libdrm-intel1: 2.4.68+git1607070630.8c8d5d~gd~x from [Updated and Optimized Open Graphics Drivers : Oibaf](https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers)
i965-va-driver: 1.7.0-1 from Ubuntu software archive

Quite sure it's not 100% reproducible.
Comment 1 林博仁 2016-07-11 07:57:27 UTC
Created attachment 125002 [details]
GPU crash dump
Comment 2 yann 2016-08-30 15:01:50 UTC
assigning to Mesa product (please let me know if I am mistaken with this GPU Hang).

From this error dump, hung is happening in render ring batch with active head at 0x7f29655c, with 0x7a000003 (PIPE_CONTROL) as IPEHR.

Batch extract (around 0x7f29655c):

0x7f29652c:      0x7b000005: 3DPRIMITIVE:
0x7f296530:      0x0000000f:    rect list sequential
0x7f296534:      0x00000003:    vertex count
0x7f296538:      0x00000000:    start vertex
0x7f29653c:      0x00000001:    instance count
0x7f296540:      0x00000000:    start instance
0x7f296544:      0x00000000:    index bias
0x7f296548:      0x7a000003: PIPE_CONTROL
0x7f29654c:      0x00101001:    no write, cs stall, render target cache flush, depth cache flush,
0x7f296550:      0x00000000:    destination address
0x7f296554:      0x00000000:    immediate dword low
0x7f296558:      0x00000000:    immediate dword high
0x7f29655c:      0x7a000003: PIPE_CONTROL
0x7f296560:      0x00000c10:    no write, instruction cache invalidate, texture cache invalidate, vf fetch invalidate,
0x7f296564:      0x00000000:    destination address
0x7f296568:      0x00000000:    immediate dword low
0x7f29656c:      0x00000000:    immediate dword high
0x7f296570:      0x78230000: 3DSTATE_VIEWPORT_STATE_POINTERS_CC
0x7f296574:      0x00007de0:    pointer to CC viewport
Comment 3 Matt Turner 2016-11-03 00:01:19 UTC
Please test a new version of Mesa (12 or 13) and mark as REOPENED
if you can reproduce and RESOLVED/* if you cannot reproduce. If it's not reproducible, there's not really any way we can debug it.
Comment 4 Annie 2017-02-10 22:38:23 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.