Messages in this thread |  | | | Date | Fri, 16 Jul 2010 11:47:39 +0200 | | Subject | Re: kmemleak, cpu usage jump out of nowhere | | From | Zeno Davatz <> |
| |
On Fri, Jul 16, 2010 at 11:32 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> Zeno Davatz wrote: >> >> This version has some problem with the DRM but no CPU eater yet. >> >> http://www.flickr.com/photos/zrr/4798885756/ >> >> This version boots again just fine: >> >> Linux zenogentoo 2.6.34-rc5-00059-gc2b4127 #105 SMP Fri Jul 16 >> 11:13:21 CEST 2010 i686 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz >> GenuineIntel GNU/Linux > > You're going into the wrong direction. If 2.6.34-rc7 works just fine, you > shouldn't be testing 2.6.34-rc5. > >> >> As I understand I am bisecting upwards. Every time it does not boot >> correctly I do >> >> git bisect bad after the next boot. > > 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. This one looks good to:
Linux zenogentoo 2.6.34-06562-gd79df0b #107 SMP Fri Jul 16 11:44:36 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |