<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:lists@andyfurniss.entadsl.com" title="Andy Furniss <lists@andyfurniss.entadsl.com>"> <span class="fn">Andy Furniss</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW --- - kernel Oops when provoking GPU lock."
href="https://bugs.freedesktop.org/show_bug.cgi?id=60254">bug 60254</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;">Summary</td>
<td>agd5f wip kernel Oops when provoking GPU lock.
</td>
<td>kernel Oops when provoking GPU lock.
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - kernel Oops when provoking GPU lock."
href="https://bugs.freedesktop.org/show_bug.cgi?id=60254#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - kernel Oops when provoking GPU lock."
href="https://bugs.freedesktop.org/show_bug.cgi?id=60254">bug 60254</a>
from <span class="vcard"><a class="email" href="mailto:lists@andyfurniss.entadsl.com" title="Andy Furniss <lists@andyfurniss.entadsl.com>"> <span class="fn">Andy Furniss</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=60254#c0">comment #0</a>)
<span class="quote">> The GPU lock with Rv670 and openarena is nothing new - it seems to have been
> a feature for almost a year (I haven't used rv670 for most of that time).
>
> On noticing the new gpu reset code in drm-next-3.9-wip I decided to provoke
> it on my AGP box and got -</span >
Hmm I just managed to get the same running drm-fixes so it's not wip maybe it's
because I am now using llvm. In the (no llvm) past with other kernels this GPU
lock normally went quite well - the game often just continued for a while,
until it hit another one.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>