<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - GPU hang while using X on Sandy Bridge notebook"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93033#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - GPU hang while using X on Sandy Bridge notebook"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93033">bug 93033</a>
from <span class="vcard"><a class="email" href="mailto:rbrito@ime.usp.br" title="Rogério Theodoro de Brito <rbrito@ime.usp.br>"> <span class="fn">Rogério Theodoro de Brito</span></a>
</span></b>
<pre>Dear Chris,
(In reply to Chris Wilson from <a href="show_bug.cgi?id=93033#c6">comment #6</a>)
<span class="quote">> Second look, and I finally found a pattern:
>
> When the ringbuffer wraps around at address 0, there is a chance that the
> GPU stops working. Marking as duplicate for tracking.
>
> *** This bug has been marked as a duplicate of <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [snb gt1] seqno writes stop after ringbuffer wraparound at address 0"
href="show_bug.cgi?id=93262">bug 93262</a> ***</span >
Excellent that you found the pattern. Unfortunately, I won't be able to test
this, as I don't have access to the computer anymore (it is now with my
ex-partner).
If, on the other hand, I could test it with a computer that has an hybrid Intel
Sandybridge + an AMD Radeon board (I sincerely don't have any clue on how the
switching between the cards happen or if I am only using one and not the
other), then I can do whatever you want me to.
On a second note, it does not seem to have been picked up by any of the
released trees that I have seen so far... Should I probe someone to get this
included, at least downstream?
Thanks,
Rogério.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>