Comment 97 for bug 727620

@Ap. Syvertsen: Let's try to lay out everything clearly to make sure there isn't any confusion. The swapping of the meanings of "good" and "bad" are bound to cause confusion, so let's use the usual meanings for any discussion with the understanding that the meanings are swapped *only in the bisect logs.*

You said, "My linux crashes occasionally during startup with kernel 2.6.39-1 with this kernel BUG, while I'm unable to produce this on 3.0-rc1." I took that to mean 2.6.39.1 is bad, i.e. exhibits an oops message similar to that in the bug description. And version 3.0-rc1 does not exhibit the oops. Is that understanding correct?

It's a little problematic to bisect between 2.6.39.1 and 3.0-rc1. The stable kernels (anything with the fourth component of the version number, i.e. 2.6.39.y) are somewhat of a branch off of normal kernel development, and the bisection will go more quickly if we start with 2.6.39. This version should still have the bug if 2.6.39.1 does, unless it was fixed and then broken again, but that's unlikely. It can't hurt to verify that 2.6.39 really does have the problem however.

So I started the bisection by marking 2.6.39 as bad (i.e. "good" in the bisect log) and 3.0-rc1 as good (i.e. "bad" in the bisect logs). git picked an intermediate version for testing, and that is what the bisect000 build represents. That is correct so far as my understanding of the situation as communicated above is correct. Does that make sense?