linux-kernel - Re: increasing memory alloted for 'init' during kernel boot.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C7CFAEA.2040408@gmail.com>
Date:	Tue, 31 Aug 2010 14:51:54 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Prabhu Chawandi <prabhu.chavandi@...il.com>
CC:	linux-kernel@...r.kernel.org, listar@...linux.org
Subject: Re: increasing memory alloted for 'init' during kernel boot.

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).

regards,
-- 
js
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/