Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751848AbWCEVux (ORCPT ); Sun, 5 Mar 2006 16:50:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751853AbWCEVux (ORCPT ); Sun, 5 Mar 2006 16:50:53 -0500 Received: from ozlabs.org ([203.10.76.45]:42634 "EHLO ozlabs.org") by vger.kernel.org with ESMTP id S1751848AbWCEVuw (ORCPT ); Sun, 5 Mar 2006 16:50:52 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17419.23860.883220.80199@cargo.ozlabs.ibm.com> Date: Mon, 6 Mar 2006 08:50:44 +1100 From: Paul Mackerras To: Olaf Hering Cc: Linus Torvalds , linuxppc-dev@ozlabs.org, Linux Kernel Mailing List Subject: Re: Linux v2.6.16-rc5 In-Reply-To: <20060305204231.GA22002@suse.de> References: <20060305140932.GA17132@suse.de> <20060305185923.GA21519@suse.de> <20060305204231.GA22002@suse.de> X-Mailer: VM 7.19 under Emacs 21.4.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1051 Lines: 27 Olaf Hering writes: > I'm now at 03929c76f3e5af919fb762e9882a9c286d361e7d, which fails as > well. dmesg shows this: The range from git5 to there includes David Woodhouse's syscall entry/exit revamp (401d1f029bebb7153ca704997772113dc36d9527) and the follow-ons which fix it for 32-bit: 9687c587596b54a77f08620595f5686ea35eed97 623703f620453c798b6fa3eb79ad8ea27bfd302a There are also commits from Ben H that change the way we parse addresses from the OF device tree. If you can bisect a bit further that would be good, although you may strike problems between the 401d and 6237 commits I mentioned above. It would be interesting to take 401d and then apply 9687 and 6237 directly on top of it and try that, and if it fails, then try 1cd8e506209223ed10da805d99be55e268f4023c (the parent of 401d). Paul. - 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/