<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [HSW] GPU hang on ctx load"
href="https://bugs.freedesktop.org/show_bug.cgi?id=83677#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [HSW] GPU hang on ctx load"
href="https://bugs.freedesktop.org/show_bug.cgi?id=83677">bug 83677</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>(In reply to <a href="show_bug.cgi?id=83677#c9">comment #9</a>)
<span class="quote">> I think I done wrong. It looks like I tried your *master* branch, not your
> *requests* branch, and bisect won't work:
>
> : sfarnsworth host64 $ git bisect start
>
> : sfarnsworth host64 $ git bisect good
> 3a5e1e6176fb61735a98f16a80c756b3cc69f125
>
> : sfarnsworth host64 $ git bisect bad
> 257d90d13794c2eb545ab0d6c708f21e2a0378b6
> Some good revs are not ancestor of the bad rev.
> git bisect cannot work properly in this case.
> Maybe you mistake good and bad revs?</span >
It's just that git is very ethical and doesn't have a loose definition of good
and bad that we do. In its opinion old code is always good and bugs are only
ever introduced. To get around this you have to do a "reverse git bisect" and
declare good as bad and vice versa.
i.e.
git bisect start
git bisect good 257d90d13794c2eb545ab0d6c708f21e2a0378b6
git bisect bad 3a5e1e6176fb61735a98f16a80c756b3cc69f125
then hang -> git bisect good, working -> git bisect bad.
I wish git bisect had a switch for that so that you didn't have to run the risk
of mixing up good/bad on each step.</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>