[Bug 83677] [HSW] GPU hang on ctx load

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Sep 17 08:31:26 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=83677

--- Comment #10 from Chris Wilson <chris at chris-wilson.co.uk> ---
(In reply to comment #9)
> 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?

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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140917/d0cae26e/attachment-0001.html>


More information about the intel-gfx-bugs mailing list