<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Random radeonsi crashes with mesa 10.3.x"
href="https://bugs.freedesktop.org/show_bug.cgi?id=85647">bug 85647</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;">Component</td>
<td>DRM/Radeon
</td>
<td>Drivers/Gallium/radeonsi
</td>
</tr>
<tr>
<td style="text-align:right;">Version</td>
<td>XOrg CVS
</td>
<td>git
</td>
</tr>
<tr>
<td style="text-align:right;">Product</td>
<td>DRI
</td>
<td>Mesa
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Random radeonsi crashes with mesa 10.3.x"
href="https://bugs.freedesktop.org/show_bug.cgi?id=85647#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Random radeonsi crashes with mesa 10.3.x"
href="https://bugs.freedesktop.org/show_bug.cgi?id=85647">bug 85647</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to Hannu from <a href="show_bug.cgi?id=85647#c5">comment #5</a>)
<span class="quote">> As I explained above, bisecting this is impossible due to random long time
> between occurrences of the bug.</span >
That doesn't make it impossible, it just means you need patience. Take your
time, and make sure you test each commit for at least as long (preferably
longer, to account for variation) as it's ever taken for the problem to occur
before declaring it good. On the bright side, when the problem occurs quickly,
you know that commit is bad and can move on to the next one.
(In reply to Hannu from <a href="show_bug.cgi?id=85647#c6">comment #6</a>)
<span class="quote">> I don't know much about xorg stacks inner workings but it might be that mesa
> isn't buggy, but has some added functionality between 10.3.x and 10.2.x that
> exercises buggy code path lower in the driver stack.</span >
It doesn't matter. Since the problem happens with Mesa 10.3.y but not with
10.2.y, once we know which change between them makes the difference, we'll be
at least a big step closer to solving the problem.</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>