Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964900Ab0GPJrm (ORCPT ); Fri, 16 Jul 2010 05:47:42 -0400 Received: from mail-fx0-f46.google.com ([209.85.161.46]:50249 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964890Ab0GPJrk convert rfc822-to-8bit (ORCPT ); Fri, 16 Jul 2010 05:47:40 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=pEc6XmT9RimLPy9JwgxapjPyUYlkIDqlchFoXrEiXvUNYhBSA7Y96Ruri6AqjIOJE8 dxMaXZvFJunZsYLyK/yxryRXPXu3iMuQd0TEMywQyzdmgoZjptidXdaHQ7ZViLDSX8Nm ekUfD8hAWWkH9hPmXB2CVgzKOa8LYowCJ27TY= MIME-Version: 1.0 In-Reply-To: <4C40271E.9070809@cs.helsinki.fi> References: <1279100846.8592.53.camel@e102109-lin.cambridge.arm.com> <4C3D89AC.4040303@cs.helsinki.fi> <1279205891.6664.46.camel@e102109-lin.cambridge.arm.com> <4C3F2F52.2050101@cs.helsinki.fi> <20100715162805.GA10240@brouette> <20100715191638.GA3694@brouette> <20100715200012.GA4175@brouette> <4C40271E.9070809@cs.helsinki.fi> Date: Fri, 16 Jul 2010 11:47:39 +0200 Message-ID: Subject: Re: kmemleak, cpu usage jump out of nowhere From: Zeno Davatz To: Pekka Enberg Cc: Damien Wyart , Catalin Marinas , "linux-kernel@vger.kernel.org" , Andrew Morton , "x86@kernel.org" , "mingo@elte.hu" , "yinghai@kernel.org" , Peter Zijlstra Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1598 Lines: 49 On Fri, Jul 16, 2010 at 11:32 AM, Pekka Enberg 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/