On Tue, 17 Oct 2006, Jesper Juhl wrote:
>
> Ok, finally got to the end of the bisection (see below; quoting all of
> my previous email since my concerns from that one are still valid).
Ok. It does smell like you marked somethign good that wasn't. That commit
1db27c11 was the last one you claimed was bad, of course, so it's the one
git will claim caused it, when you've marked its parent good.
> Where do I go from here? The problem is still there... I'll test
> 2.6.19-rc2 tomorrow, but apart from that I don't know how to proceed
> apart from trying to capture a sysrq+t dump when the box locks up...
> any ideas?
Yeah, trying to do sysrq when it locks is probably worth it. As is
enabling debugging things (netconsole, page-alloc, slab alloc, lockdep
etc).
But if nothing seems to really give any clues, you might just try
to restart bisection with
git bisect reset
git bisect start
git bisect good v2.6.17
git bisect bad 1db27c11
and just run the resulting kernel version for a day or two. If an hour
wasn't really good enough, it's not as repeatable as we'd have wished, but
even if it takes a few days to narrow it down by just two bisections or
so, it will cut things down from ten thousand commits to "just" 2500..
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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
