From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: Uncompressing broken with commit e7db7b4270
Date: Fri, 29 Jan 2010 16:14:02 +0100 [thread overview]
Message-ID: <20100129151402.GD27577@pengutronix.de> (raw)
In-Reply-To: <20100129150345.GA5876@laptop>
Hello,
On Fri, Jan 29, 2010 at 04:04:15PM +0100, Albin Tonnerre wrote:
> On Fri, 29 Jan 2010 15:46 +0100, Uwe Kleine-K?nig wrote :
> > On Thu, Jan 28, 2010 at 05:03:49PM +0000, Catalin Marinas wrote:
> > > Hi,
>
> > > For whatever reason, with commit e7db7b4270 (arm: add support for
> > > LZO-compressed kernels) if the kernel Image goes beyond a certain size
> > > it fails to uncompress. Reverting this commit solves the problem.
> > > Removing some random kernel features also solves the uncompressing as
> > > the kernel image gets smaller.
> > With the same commit zImage stopped printing dots during decompression.
>
> > Something that isn't mentioned in the commit log of e7db7b4270 is that
> > the decompressing routine for gzip is changed.
>
> > Before lib/inflate.c was included by arch/arm/boot/compressed/misc.c,
> > since e7db7b4270 it's lib/decompress_inflate.c.
>
> Indeed, that's why it stopped printing dots.
I'd like to have them back.
> > Maybe the new implementation needs more stack space? If so it might
> > help to increase the stack size. (This is defined in the last line of
> > arch/arm/boot/compressed/head.S. If you change the value be sure to
> > adapt the value just before the LC1 label in the same file, too.)
>
> If so, the decompressor would exit with an error message stating that it can't
> allocate enough memory, so I doubt this is the cause.
I havn't investigated but I wonder how a stack overflow would be
detected.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-01-29 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 17:03 Uncompressing broken with commit e7db7b4270 Catalin Marinas
2010-01-29 14:46 ` Uwe Kleine-König
2010-01-29 15:04 ` Albin Tonnerre
2010-01-29 15:14 ` Uwe Kleine-König [this message]
2010-01-29 15:29 ` Albin Tonnerre
2010-01-29 15:16 ` Russell King - ARM Linux
2010-01-29 16:12 ` Colin Tuckley
2010-01-29 21:13 ` Uwe Kleine-König
2010-02-02 9:01 ` Uwe Kleine-König
2010-02-02 9:07 ` Colin Tuckley
2010-02-02 9:55 ` Uwe Kleine-König
2010-02-02 10:19 ` Catalin Marinas
2010-02-03 9:41 ` Uwe Kleine-König
2010-02-19 14:21 ` Uwe Kleine-König
2010-02-19 15:27 ` Catalin Marinas
2010-02-01 22:56 ` Albin Tonnerre
2010-02-02 8:44 ` Uwe Kleine-König
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=20100129151402.GD27577@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).