On Tue, 16 Aug 2005, Helge Hafting wrote:
>
> This was interesting. At first, lots of kernels just kept working,
> I almost suspected I was doing something wrong. Then the second last kernel
> recompiled a lot of DRM stuff - and the crash came back!
> The kernel after that worked again, and so the final message was:
>
> 561fb765b97f287211a2c73a844c5edb12f44f1d is first bad commit
Ok, that definitely looks bogus.
That commit should not matter at _all_, it only changes ppc64 specific
things.
If the bug is sometimes hard to trigger, maybe one of the "good" kernels
wasn't good after all. That would definitely throw a wrench in the
bisection.
Anyway, with something like this, where there may be false positives
(false "good" kernels), the only thing you can _really_ trust is a kernel
that got marked bad, because that one definitely has the problem. So make
sure that you remember all known-bad kernels.
Btw, we haven't had a lot of testign of the termination condition for "git
bisect", so it's possible it's off by a commit or two. However, the commit
you actually ended up on is literally just two commits before 2.6.13-rc5,
which makes me suspect that it's not the termination condition, as much as
the fact that it really was an earlier kernel that had the problem, but
you bisected it as "good" because the problem just didn't trigger quickly
enough..
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |