<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - GPU HANG: ecode 8:0:0x85df7c3b, in vmd_LINUX [16526], reason: Ring hung, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94533">94533</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GPU HANG: ecode 8:0:0x85df7c3b, in vmd_LINUX [16526], reason: Ring hung, action: reset
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>tm@dev-zero.ch
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=122278" name="attach_122278" title="drm-card0-error dump">attachment 122278</a> <a href="attachment.cgi?id=122278&action=edit" title="drm-card0-error dump">[details]</a></span>
drm-card0-error dump
... mostly a duplicate of one of the other `GPU HANG: ecode` or `stuck on
render ring`, but I'm not sure which one.
Kernel Log is as follows:
[22006.326765] [drm] stuck on render ring
[22006.327216] [drm] GPU HANG: ecode 8:0:0x85df7c3b, in vmd_LINUX [16526],
reason: Ring hung, action: reset
[22006.327218] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[22006.327218] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[22006.327219] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[22006.327220] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[22006.327220] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[22006.327237] ------------[ cut here ]------------
[22006.327244] WARNING: CPU: 0 PID: 16608 at
drivers/gpu/drm/i915/intel_display.c:11289
intel_mmio_flip_work_func+0x388/0x3d0()
[22006.327246] WARN_ON(__i915_wait_request(mmio_flip->req,
mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
[22006.327247] Modules linked in:
[22006.327249] ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT
nf_reject_ipv4 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_filter
ebtable_broute bridge stp llc ebtables ip6table_mangle ip6table_security
ip6table_raw ip6table_nat nf_nat_ipv6 iptable_mangle iptable_security
iptable_raw iptable_nat nf_nat_ipv4 nf_nat rfcomm bnep hid_multitouch dell_wmi
dell_laptop dcdbas coretemp iwlmvm mac80211 kvm_intel kvm irqbypass psmouse
elan_i2c iwlwifi rtsx_pci_ms cfg80211 memstick uvcvideo videobuf2_v4l2
videobuf2_core videobuf2_vmalloc videobuf2_memops mei_me btusb btintel mei
i2c_designware_platform i2c_designware_core sch_fq_codel rtsx_pci_sdmmc
mmc_core i2c_hid
[22006.327285] CPU: 0 PID: 16608 Comm: kworker/0:1 Tainted: G U
4.4.5-gentoo #1
[22006.327286] Hardware name: Dell Inc. XPS 13 9343/0F5KF3, BIOS A04 05/15/2015
[22006.327289] Workqueue: events intel_mmio_flip_work_func
[22006.327291] 0000000000000000 ffff8801038dfd30 ffffffff8182803a
ffff8801038dfd78
[22006.327293] ffffffff81cc8378 ffff8801038dfd68 ffffffff81077912
ffff8800304e1a80
[22006.327296] ffff88021e414980 ffff88021e419300 ffff8800304e1a88
ffff8800304e1a80
[22006.327298] Call Trace:
[22006.327304] [<ffffffff8182803a>] dump_stack+0x4d/0x63
[22006.327307] [<ffffffff81077912>] warn_slowpath_common+0x82/0xc0
[22006.327311] [<ffffffff8107799c>] warn_slowpath_fmt+0x4c/0x50
[22006.327313] [<ffffffff814fdf58>] intel_mmio_flip_work_func+0x388/0x3d0
[22006.327315] [<ffffffff8182c0a5>] ? __schedule+0x3a5/0xb20
[22006.327318] [<ffffffff8108e4f7>] process_one_work+0x147/0x410
[22006.327320] [<ffffffff8108e80b>] worker_thread+0x4b/0x440
[22006.327322] [<ffffffff8108e7c0>] ? process_one_work+0x410/0x410
[22006.327323] [<ffffffff8108e7c0>] ? process_one_work+0x410/0x410
[22006.327325] [<ffffffff81093e79>] kthread+0xc9/0xe0
[22006.327327] [<ffffffff81093db0>] ? kthread_worker_fn+0x150/0x150
[22006.327329] [<ffffffff8183055f>] ret_from_fork+0x3f/0x70
[22006.327331] [<ffffffff81093db0>] ? kthread_worker_fn+0x150/0x150
[22006.327332] ---[ end trace a21a969e61ad96e6 ]---
[22006.329334] drm/i915: Resetting chip after gpu hang
[22024.334222] [drm] stuck on render ring
[22024.334905] [drm] GPU HANG: ecode 8:0:0x86d51c1a, in vmd_LINUX [16526],
reason: Ring hung, action: reset
[22024.334946] ------------[ cut here ]------------
[22024.334957] WARNING: CPU: 1 PID: 16596 at
drivers/gpu/drm/i915/intel_display.c:11289
intel_mmio_flip_work_func+0x388/0x3d0()
[22024.334962] WARN_ON(__i915_wait_request(mmio_flip->req,
mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
[22024.334964] Modules linked in:
[22024.334968] ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT
nf_reject_ipv4 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_filter
ebtable_broute bridge stp llc ebtables ip6table_mangle ip6table_security
ip6table_raw ip6table_nat nf_nat_ipv6 iptable_mangle iptable_security
iptable_raw iptable_nat nf_nat_ipv4 nf_nat rfcomm bnep hid_multitouch dell_wmi
dell_laptop dcdbas coretemp iwlmvm mac80211 kvm_intel kvm irqbypass psmouse
elan_i2c iwlwifi rtsx_pci_ms cfg80211 memstick uvcvideo videobuf2_v4l2
videobuf2_core videobuf2_vmalloc videobuf2_memops mei_me btusb btintel mei
i2c_designware_platform i2c_designware_core sch_fq_codel rtsx_pci_sdmmc
mmc_core i2c_hid
[22024.335034] CPU: 1 PID: 16596 Comm: kworker/1:0 Tainted: G U W
4.4.5-gentoo #1
[22024.335037] Hardware name: Dell Inc. XPS 13 9343/0F5KF3, BIOS A04 05/15/2015
[22024.335043] Workqueue: events intel_mmio_flip_work_func
[22024.335046] 0000000000000000 ffff8800065fbd30 ffffffff8182803a
ffff8800065fbd78
[22024.335051] ffffffff81cc8378 ffff8800065fbd68 ffffffff81077912
ffff88001dce8f80
[22024.335056] ffff88021e494980 ffff88021e499300 ffff88001dce8f88
ffff88001dce8f80
[22024.335060] Call Trace:
[22024.335068] [<ffffffff8182803a>] dump_stack+0x4d/0x63
[22024.335075] [<ffffffff81077912>] warn_slowpath_common+0x82/0xc0
[22024.335081] [<ffffffff8107799c>] warn_slowpath_fmt+0x4c/0x50
[22024.335086] [<ffffffff814fdf58>] intel_mmio_flip_work_func+0x388/0x3d0
[22024.335089] [<ffffffff8182c0a5>] ? __schedule+0x3a5/0xb20
[22024.335094] [<ffffffff8108e4f7>] process_one_work+0x147/0x410
[22024.335098] [<ffffffff8108e80b>] worker_thread+0x4b/0x440
[22024.335102] [<ffffffff8108e7c0>] ? process_one_work+0x410/0x410
[22024.335106] [<ffffffff8108e7c0>] ? process_one_work+0x410/0x410
[22024.335109] [<ffffffff81093e79>] kthread+0xc9/0xe0
[22024.335113] [<ffffffff81093db0>] ? kthread_worker_fn+0x150/0x150
[22024.335117] [<ffffffff8183055f>] ret_from_fork+0x3f/0x70
[22024.335120] [<ffffffff81093db0>] ? kthread_worker_fn+0x150/0x150
[22024.335123] ---[ end trace a21a969e61ad96e7 ]---
[22024.337130] drm/i915: Resetting chip after gpu hang
[22076.316619] [drm] stuck on render ring
[22076.317004] [drm] GPU HANG: ecode 8:0:0x86d51c1a, in vmd_LINUX [16526],
reason: Ring hung, action: reset
[22076.319146] drm/i915: Resetting chip after gpu hang
[22082.316863] [drm] stuck on render ring
[22082.317216] [drm] GPU HANG: ecode 8:0:0x85df7cfb, in vmd_LINUX [16526],
reason: Ring hung, action: reset
[22082.319329] drm/i915: Resetting chip after gpu hang
Kernel Version: 4.4.5(-gentoo)
(Relevant) Kernel cmdline: pcie_asm=force intel_iommu=igfx_off
i915.enable_psr=1 i915.i915_enable_fbc=1 i915.i915_enable_rc6=1
i915.lvds_downclock=1
X.Org drivers are from Git master on 2016-03-12</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>