mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: karsten wiese <annabellesgarden@yahoo.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]Uncompressing Linux... Out of memory: fixed by increased HEAP_SIZE
Date: Mon, 25 Oct 2004 21:43:27 +0200 (CEST)	[thread overview]
Message-ID: <20041025194327.88284.qmail@web12204.mail.yahoo.com> (raw)
In-Reply-To: <20041025143014.GA14992@elte.hu>

 --- Ingo Molnar <mingo@elte.hu> schrieb: 
> 
> > booting newest 2.6.9 experimental kernels, I frequently
> encountered 
> > "Uncompressing Linux... Out of memory --System halted"
> > In some mail archive I found the (obvious ;-) solution:
> Increase HEAP_SIZE.
> > 
> > Here in line 122 of arch/i386/boot/compressed/misc.c
> this
> > 	#define HEAP_SIZE             0x4000
> > instead of 
> > 	#define HEAP_SIZE             0x3000
> > made 2.6.9-mm1-RT-U10.3 boot again.
> 
> ah! Makes sense. Did you have LATENCY_TRACE enabled? That
> compiles the
> kernel with -pg which creates a fatter stackframe.
> 
Only the malloc() called by gunzip() called by
decompress_kernel() is influenced by this HEAP_SIZE.
gunzip()'s internal work data is stored in that heap.
This only is in effect before the kernel "really" boots,
no?
LATENCY_TRACE is indeed off, ...but can gunzip()'s heap
needs be easier answered by a fatter stackframe (at
decompression time!)?

Thanks,
Karsten


	

	
		
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

      reply	other threads:[~2004-10-25 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-25 14:28 Karsten Wiese
2004-10-25 14:30 ` Ingo Molnar
2004-10-25 19:43   ` karsten wiese [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041025194327.88284.qmail@web12204.mail.yahoo.com \
    --to=annabellesgarden@yahoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®