* Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:

quoted text
> On Fri, 21 Mar 2008 20:58:13 BST, Ingo Molnar said:
> 
> > no, we frequently regenerate the x86.git tree so the dates have little 
> > relevance. If for any particular pull, x86/base is good and x86/latest 
> > is bad, then the bug is somewhere in those 200-300 patches inbetween. 
> > They are lined up linearly so should be perfectly bisectable.
> 
> OK, off to go try the last few bisects then...

well ... your git bisection log does look suspiciously 'good', so 
something is wrong thee i think :-(

the chance to get 8 'good' bisection points in a row is 1:256. OTOH, the 
freshest x86 patches are always at the 'end' of the queue - which are 
also the ones most likely to break anything.

Are you sure the x86/base point is indeed 'good'? You can check it via:

 git-checkout -b tmp x86/base

and build+boot it.

	Ingo
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/