On Tue, Jul 21, 2015 at 11:07:20AM +0200, Daniel Vetter wrote: > On Tue, Jul 21, 2015 at 10:58:50AM +0200, Krzysztof Kolasa wrote: > > On 21.07.2015 10:41, Daniel Vetter wrote: > > > I meant whether you can reset the bad commit and it's immediate parent > > > extensively to make sure the bisect is really correct. gpu's occasionally > > > take a while to hang themselves, so could be that the bisect was > > > mislead somewhere. > > > > > > Again I will bisect, more testing good sections. > > > > At the moment on my old laptop, the latest official, properly working kernel is 4.1.2 > > You don't need to redo the full bisect, only retest the bad and the parent > of the bad extensively. That's enough to confirm the bisect result for > sure. The bisection is misleading. It's a missing write-barrier. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
