Re: kmemleak, cpu usage jump out of nowhere
From: Zeno Davatz
Date: Fri Jul 16 2010 - 05:42:46 EST
On Fri, Jul 16, 2010 at 11:32 AM, Pekka Enberg <penberg@xxxxxxxxxxxxxx> wrote:
> No, you should only do "git bisect bad" if you find a CPU eater and "git
> bisect good" if you don't. For the non-booting kernels you should do "git
> bisect skip"; otherwise git gets confused as we can see here.
>
> Did you test v2.6.35-rc1? Does it have the CPU eater problem? If yes, please
> just reset your bisection
>
> git bisect reset
> git bisect start
> git bisect good v2.6.34-rc7
> git bisect bad v2.6.35-rc1
>
> and use 'git bisect skip' for kernels that don't boot or build.
Ok I done above and reboot onto the new bzImage:
This version looks fine.
Linux zenogentoo 2.6.34-04401-gf896546 #106 SMP Fri Jul 16 11:37:04
CEST 2010 i686 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel
GNU/Linux
Best
Zeno
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/