Date: Tue, 31 Aug 2010 14:58:30 +0200
From: Sam Ravnborg <sam@ravnborg.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Prabhu Chawandi <prabhu.chavandi@gmail.com>, linux-kernel@vger.kernel.org,
        listar@nl.linux.org
Subject: Re: increasing memory alloted for 'init' during kernel boot.
Message-ID: <20100831125830.GA14848@merkur.ravnborg.org>
References: <AANLkTimWnYqFSC=3kqzBVtZHwodCX=MnsViDGmJbUn_8@mail.gmail.com> <4C7CBBBC.3070503@gmail.com> <AANLkTiniKYm7krr1j48VbV7oNDA7YKXzTnuCZ9kOMnUs@mail.gmail.com> <4C7CFAEA.2040408@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C7CFAEA.2040408@gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1099
Lines: 32

On Tue, Aug 31, 2010 at 02:51:54PM +0200, Jiri Slaby wrote:
> On 08/31/2010 10:43 AM, Prabhu Chawandi wrote:
> > Hi ,
> > 
> > Thanks for the info...
> > 
> > Problem I am facing is, I have two bootloaders, when I boot from one
> > loader booting happens properly.
> > 
> > but when I try to load from other loader, kernel does not boot, it
> > crashes. When i saw the boot logs, I saw that I memory allocated to
> > 'init' section in case of crash is short by almost 5MB to the normal
> > boot log.
> > 
> > I am using mips processor.
> > 
> > Any idea, why this might be happening ?
> 
> The bad loader probably loads the image wrong (incorrect data or not
> whole image).

Shmulik just posted a patch that may be related.
See: "MIPS: Calculate VMLINUZ_LOAD_ADDRESS based on the length of vmlinux.bin"

Looks like a bug I have introduced btw :-(

	Sam
--
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/