<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Dell 7440 i7 4600U HD4400 ERROR* Kicking stuck wait on blitter ring"
href="https://bugs.freedesktop.org/show_bug.cgi?id=79302">79302</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>Dell 7440 i7 4600U HD4400 ERROR* Kicking stuck wait on blitter ring
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>maks@manichord.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=99943" name="attach_99943" title="dump from /sys/class/drm/card0/error">attachment 99943</a> <a href="attachment.cgi?id=99943&action=edit" title="dump from /sys/class/drm/card0/error">[details]</a></span>
dump from /sys/class/drm/card0/error
I got this in my dmesg today:
[Tue May 27 13:54:44 2014] [drm:ring_stuck] *ERROR* Kicking stuck wait on
blitter ring
[Tue May 27 13:54:44 2014] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
[Tue May 27 13:54:44 2014] [drm] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
[Tue May 27 13:54:44 2014] [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
[Tue May 27 13:54:44 2014] [drm] drm/i915 developers can then reassign to the
right component if it's not a kernel issue.
[Tue May 27 13:54:44 2014] [drm] The gpu crash dump is required to analyze gpu
hangs, so please always attach it.
[Tue May 27 14:00:39 2014] kvm: zapping shadow pages for mmio generation
wraparound
So I attached the output from there to this bug report.
But my laptop seemed to still be working fine and the display seemed ok, though
at some point later in time (not sure when) the laptops screen was black and
but the back light was still off. Enabling and disabling the laptop screen in
ubuntu (xrandr) display manager brought the display back - it was connected to
an external monitor via the eDocks DVI port and that remained fine the whole
time.
Note that this is after my LCD and cabling were replaced today for 2nd time due
to the LCD turning itself off though pretty sure the hardware fault due to the
lvds cable is now fixed.</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>