Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932454AbVIEUC2 (ORCPT ); Mon, 5 Sep 2005 16:02:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932455AbVIEUC2 (ORCPT ); Mon, 5 Sep 2005 16:02:28 -0400 Received: from 66-23-228-155.clients.speedfactory.net ([66.23.228.155]:50094 "EHLO kevlar.burdell.org") by vger.kernel.org with ESMTP id S932454AbVIEUC1 (ORCPT ); Mon, 5 Sep 2005 16:02:27 -0400 Date: Mon, 5 Sep 2005 15:58:49 -0400 From: Sonny Rao To: Linus Torvalds Cc: Rolf Eike Beer , Linux Kernel Mailing List , Helge Hafting , Dave Airlie , Benjamin Herrenschmidt , Michael Ellerman , Greg Kroah-Hartman , Andrew Morton Subject: Re: rc5 seemed to kill a disk that rc4-mm1 likes. Also some X trouble. Message-ID: <20050905195849.GA8683@kevlar.burdell.org> References: <200508301007.11554@bilbo.math.uni-mannheim.de> <200509050949.38842@bilbo.math.uni-mannheim.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1308 Lines: 33 On Mon, Sep 05, 2005 at 01:45:28AM -0700, Linus Torvalds wrote: > > On Mon, 5 Sep 2005, Rolf Eike Beer wrote: > > > > The problem appeared between 2.6.12-git3 and 2.6.12-git4. > > Just for reference, that's git ID's > > 1d345dac1f30af1cd9f3a1faa12f9f18f17f236e..2a5a68b840cbab31baab2d9b2e1e6de3b289ae1e > > and that's 225 commits and the diff is 55,781 lines long. > > It would be very good if you could try to use raw git and narrow it down a > bit more. It's really easy these days with a recent git version, just do > > git bisect start > git bisect good 1d345dac1f30af1cd9f3a1faa12f9f18f17f236e > git bisect bad 2a5a68b840cbab31baab2d9b2e1e6de3b289ae1e > > and off you go.. That will select a new kernel for you to try, which > basically cuts down the commits to ~110 - and if you can test just a few > kernels and binary-search a bit more, we'd have it down to just a couple. Can this method detect breakages that are spread across more than one patch? I suppose it'll just trigger on the last patch commited in the set in this case? Sonny - 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/