<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 - [HSW] stuck on render ring, WARN_ON(__i915_wait_request(…))"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91452">91452</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[HSW] stuck on render ring, WARN_ON(__i915_wait_request(…))
</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>andreas.reis@gmail.com
</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=117342" name="attach_117342" title="/sys/class/drm/card0">attachment 117342</a> <a href="attachment.cgi?id=117342&action=edit" title="/sys/class/drm/card0">[details]</a></span>
/sys/class/drm/card0
Haswell 4770, 4.2-rc3 + drm-intel-nightly @ 07.22.15, xserver + xf86 intel git
versions
Occurs randomly, this with nothing but browsing with Chromium 46.0.2459.0
(started with --ignore-gpu-blacklist though).
[ 6209.976368] [drm] stuck on render ring
[ 6209.976895] [drm] GPU HANG: ecode 7:0:0x85dffffc, in chromium-dev [29630],
reason: Ring hung, action: reset
[ 6209.976896] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 6209.976896] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 6209.976897] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 6209.976897] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 6209.976898] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 6209.976915] ------------[ cut here ]------------
[ 6209.976931] WARNING: CPU: 0 PID: 5475 at
drivers/gpu/drm/i915/intel_display.c:11278
intel_mmio_flip_work_func+0x3ac/0x3c0()
[ 6209.976932] WARN_ON(__i915_wait_request(mmio_flip->req,
mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
[ 6209.976933] Modules linked in:
[ 6209.976934]
[ 6209.976939] CPU: 0 PID: 5475 Comm: kworker/0:1 Tainted: G W
4.2.0-1-cu #1
[ 6209.976956] Hardware name: Gigabyte Technology Co., Ltd. G1.Sniper
M5/G1.Sniper M5, BIOS T01 02/03/2015
[ 6209.976958] Workqueue: events intel_mmio_flip_work_func
[ 6209.976959] 0000000000000000 00000000dc92c46d ffff880348fa7cd8
ffffffff8193c4aa
[ 6209.976960] 0000000000000000 ffff880348fa7d30 ffff880348fa7d18
ffffffff810e5366
[ 6209.976961] ffff880348fa7ce8 ffff880348f24f00 ffff880039daf540
ffff88042f21a400
[ 6209.976963] Call Trace:
[ 6209.976966] [<ffffffff8193c4aa>] dump_stack+0x4c/0x6e
[ 6209.976969] [<ffffffff810e5366>] warn_slowpath_common+0x86/0xc0
[ 6209.976970] [<ffffffff810e53f5>] warn_slowpath_fmt+0x55/0x70
[ 6209.976982] [<ffffffff8162b04c>] intel_mmio_flip_work_func+0x3ac/0x3c0
[ 6209.976984] [<ffffffff81109d12>] ? finish_task_switch+0x62/0x190
[ 6209.976987] [<ffffffff810fcc5e>] process_one_work+0x14e/0x440
[ 6209.976988] [<ffffffff810fcf98>] worker_thread+0x48/0x4a0
[ 6209.976989] [<ffffffff810fcf50>] ? process_one_work+0x440/0x440
[ 6209.976990] [<ffffffff810fcf50>] ? process_one_work+0x440/0x440
[ 6209.976991] [<ffffffff81102838>] kthread+0xd8/0xf0
[ 6209.977009] [<ffffffff81102760>] ? kthread_worker_fn+0x170/0x170
[ 6209.977010] [<ffffffff8194321f>] ret_from_fork+0x3f/0x70
[ 6209.977011] [<ffffffff81102760>] ? kthread_worker_fn+0x170/0x170
[ 6209.977012] ---[ end trace 2b0c2f22f1687665 ]---
[ 6209.979035] drm/i915: Resetting chip after gpu hang</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 on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>