<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [g43] Missed irq leading to hard lockup"
href="https://bugs.freedesktop.org/show_bug.cgi?id=79009">bug 79009</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Assignee</td>
<td>chris@chris-wilson.co.uk
</td>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<td style="text-align:right;">Summary</td>
<td>Display hangs but mouse cursor moves, kernel reports "[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... render ring idle", G43 chipset
</td>
<td>[g43] Missed irq leading to hard lockup
</td>
</tr>
<tr>
<td style="text-align:right;">Product</td>
<td>xorg
</td>
<td>DRI
</td>
</tr>
<tr>
<td style="text-align:right;">Version</td>
<td>7.7 (2011)
</td>
<td>unspecified
</td>
</tr>
<tr>
<td style="text-align:right;">Component</td>
<td>Driver/intel
</td>
<td>DRM/Intel
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [g43] Missed irq leading to hard lockup"
href="https://bugs.freedesktop.org/show_bug.cgi?id=79009#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [g43] Missed irq leading to hard lockup"
href="https://bugs.freedesktop.org/show_bug.cgi?id=79009">bug 79009</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>Hard lock? Not even ssh'able? It would be really useful to get the kernel and
userspace stack traces of the stuck processes.
After a missed irq, we start busy-waiting for the GPU rather than rely on any
more interrupts being received. Obviously that should not lead to a lock up.</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>