<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 - [drm] stuck on bsd ring (bisected)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97396">97396</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[drm] stuck on bsd ring (bisected)
</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>minor
</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>mymailclone@t-online.de
</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>Since kernel 4.3 and up to 4.7.1, dmesg shows the following or similar messages
after resuming from hibernation, here for 4.7.1:
[drm] stuck on bsd ring
[drm] GPU HANG: ecode 5:2:0x01000000, reason: Engine(s) hung, action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including
userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI ->
DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not
a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always
attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
drm/i915: Resetting chip after gpu hang
Interestingly, with 4.4.18 I only see this:
[drm] stuck on bsd ring
[drm] GPU HANG: ecode 5:1:0x01000000, reason: Ring hung, action: reset
drm/i915: Resetting chip after gpu hang
Other than the messages, I haven't noticed any negative impact on my system
(Core i3). But this may be different for other setups (see
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Gpu Hang After Resume From Hibernate State With 4.4 and up to 4.6"
href="show_bug.cgi?id=94203">https://bugs.freedesktop.org/show_bug.cgi?id=94203</a>).
I bisected between 4.2 and 4.3, "bad/good" strictly according to whether "[drm]
stuck on bsd ring" occurred or not - disregarding all the other numerous
warnings in connection with i915. The result this produced was:
<span class="quote">> git bisect good</span >
ba01cc9346bce45a8861f36bce2c4c5d44b800b2 is the first bad commit
commit ba01cc9346bce45a8861f36bce2c4c5d44b800b2
Author: John Harrison <<a href="mailto:John.C.Harrison@Intel.com">John.C.Harrison@Intel.com</a>>
Date: Fri May 29 17:43:41 2015 +0100
drm/i915: Update i915_switch_context() to take a request structure
Now that the request is guaranteed to specify the context, it is possible
to
update the context switch code to use requests rather than ring and context
pairs. This patch updates i915_switch_context() accordingly.
Also removed the warning that the request's context must match the last
context
switch's context. As the context switch now gets the context object from
the
request structure, there is no longer any scope for the two to become out
of
step.
For: VIZ-5115
Signed-off-by: John Harrison <<a href="mailto:John.C.Harrison@Intel.com">John.C.Harrison@Intel.com</a>>
Reviewed-by: Tomas Elf <<a href="mailto:tomas.elf@intel.com">tomas.elf@intel.com</a>>
Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
:040000 040000 3717675a773aafd62ff883278f0a9dd0b4747af9
0f32cac1cb40d7d1f757495a85e77bf39863862a M drivers
---</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>