Date: Sat, 19 Nov 2005 13:05:48 +0100
From: Voluspa <lista1@telia.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, rajesh.shah@intel.com, kjarvel@home.se,
       howarth@bromo.msbb.uc.edu
Subject: Re: PCI error on x86_64 2.6.13 kernel
Message-Id: <20051119130548.1d86e1d9.lista1@telia.com>
In-Reply-To: <20051119011840.GB28175@kroah.com>
References: <20051118080440.4aaf4a6d.lista1@telia.com>
	<20051119011840.GB28175@kroah.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 951
Lines: 23

On Fri, 18 Nov 2005 17:18:40 -0800 Greg KH wrote:
> Is there any way you could be able to run 'git bisect' between 2.6.12
> and 2.6.13 to try to find the offending changeset?  I would really
> appreciate it.

I'll take one beer (or in .ru: \u043f\u0438\u0432\u043e) for each hour ;-) This is a six-pack:

299de0343c7d18448a69c635378342e9214b14af is first bad commit
diff-tree 299de0343c7d18448a69c635378342e9214b14af (from 90b54929b626c80056262d9d99b3f48522e404d0)

Marvellous tool, that git. But it took less time - for us users - when we only had to
wave in a general -rc direction...

I've not tried to back the commit out from a 2.6.14 kernel, though. Will wait for a real fix.

Mvh
Mats Johannesson
--
-
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/