From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030406AbWGaVBe (ORCPT ); Mon, 31 Jul 2006 17:01:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030452AbWGaVBd (ORCPT ); Mon, 31 Jul 2006 17:01:33 -0400 Received: from e3.ny.us.ibm.com ([32.97.182.143]:64979 "EHLO e3.ny.us.ibm.com") by vger.kernel.org with ESMTP id S1030449AbWGaVBb (ORCPT ); Mon, 31 Jul 2006 17:01:31 -0400 Date: Mon, 31 Jul 2006 17:00:50 -0400 From: Vivek Goyal To: "Eric W. Biederman" Cc: fastboot@osdl.org, Horms , Jan Kratochvil , "H. Peter Anvin" , Magnus Damm , linux-kernel@vger.kernel.org Subject: Re: [Fastboot] [CFT] ELF Relocatable x86 and x86_64 bzImages Message-ID: <20060731210050.GC11790@in.ibm.com> Reply-To: vgoyal@in.ibm.com References: <20060706081520.GB28225@host0.dyn.jankratochvil.net> <20060707133518.GA15810@in.ibm.com> <20060707143519.GB13097@host0.dyn.jankratochvil.net> <20060710233219.GF16215@in.ibm.com> <20060711010815.GB1021@host0.dyn.jankratochvil.net> <20060731202520.GB11790@in.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060731202520.GB11790@in.ibm.com> User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 31, 2006 at 04:25:20PM -0400, Vivek Goyal wrote: > On Mon, Jul 31, 2006 at 10:19:04AM -0600, Eric W. Biederman wrote: > > > > I have spent some time and have gotten my relocatable kernel patches > > working against the latest kernels. I intend to push this upstream > > shortly. > > > > Could all of the people who care take a look and test this out > > to make certain that it doesn't just work on my test box? > > > Hi Eric, > > Currently I am testing your patches on i386. With CONFIG_RELOCATABLE=y > kernel boots fine and kexec also works. > > But my kernel hangs on kexec on panic case. It hangs early in > decompress_kernel(). Kernel hangs at following condition. > > + if (((u32)output - CONFIG_PHYSICAL_START) & 0x3fffff) > + error("Destination address not 4M aligned"); > Ok. I am decompressing the kernel to 16MB and after reducing 1MB of CONFIG_PHYSICAL_START I am left with 15MB which is not 4M aligned hence I seems to be running into it. I changed it to if ((u32)output) & 0x3fffff) and kdump kernel booted fine. But this will run into issues if I load kernel at 1MB. I got a dump question. Why do I have to load the kernel at 4MB alignment? Existing kernel boots loads at 1MB, which is non 4MB aligned and it works fine? Thanks Vivek