Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161096AbWLUNNx (ORCPT ); Thu, 21 Dec 2006 08:13:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161097AbWLUNNx (ORCPT ); Thu, 21 Dec 2006 08:13:53 -0500 Received: from smtp-104-thursday.noc.nerim.net ([62.4.17.104]:3267 "EHLO mallaury.nerim.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1161096AbWLUNNw (ORCPT ); Thu, 21 Dec 2006 08:13:52 -0500 Date: Thu, 21 Dec 2006 14:13:54 +0100 From: Jean Delvare To: Vivek Goyal Cc: "Eric W. Biederman" , Andi Kleen , LKML Subject: Re: Patch "i386: Relocatable kernel support" causes instant reboot Message-Id: <20061221141354.6d9ec3e6.khali@linux-fr.org> In-Reply-To: <20061221010814.GA30299@in.ibm.com> References: <20061220141808.e4b8c0ea.khali@linux-fr.org> <20061220214340.f6b037b1.khali@linux-fr.org> <20061221101240.f7e8f107.khali@linux-fr.org> <20061221102232.5a10bece.khali@linux-fr.org> <20061221010814.GA30299@in.ibm.com> X-Mailer: Sylpheed version 2.2.10 (GTK+ 2.8.20; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1304 Lines: 29 On Thu, 21 Dec 2006 06:38:14 +0530, Vivek Goyal wrote: > On Thu, Dec 21, 2006 at 03:32:33AM -0700, Eric W. Biederman wrote: > > Grr. I guessed the problem was to late in the game it seems the problem > > is in setup.S Before we switch to 32bit mode. > > > > Ok. There is almost enough for inference but here is a patch of stops > > for setup.S let's see if one of those will stop the reboots. > > > > I have a strong feeling that we are going to find a tool chain issue, > > but I'd like to find where we ware having problems before we declare > > that to be the case. > > Looks like it might be a tool chain issue. I took Jean's config file and > built my own kernel and I am able to boot the kernel. But I can't boot > his bzImage. I observed the same behaviour as jean is experiencing. It jumps > back to BIOS. I can only confirm that. I installed a more recent system on the same hardware, rebuilt a kernel from the same config file, and now it boots OK. So it's not related to the hardware. It has to be a compilation-time issue. -- Jean Delvare - 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/