From: colin.tuckley@arm.com (Colin Tuckley)
To: linux-arm-kernel@lists.infradead.org
Subject: Uncompressing broken with commit e7db7b4270
Date: Fri, 29 Jan 2010 16:12:08 -0000 [thread overview]
Message-ID: <000001caa0fd$cef2f740$9fca010a@Emea.Arm.com> (raw)
In-Reply-To: <1264698229.7064.93.camel@pc1117.cambridge.arm.com>
> -----Original Message-----
> From: linux-arm-kernel-bounces at lists.infradead.org
> Behalf Of Catalin Marinas
> 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.
My experiments appear to show that the problem appears as the kernel image
grows above 2MB
When size is 2084132 (1.9MB) it boots
If I add something to make it slightly bigger (like Control Group
Support)...
then size is 2103332 (2.005MB) and it fails to uncompress.
I'm building a RealView PBX kernel for A9 (v7).
Colin
--
Colin Tuckley - ARM Ltd.
110 Fulbourn Rd
Cambridge, CB1 9NJ
Tel: +44 1223 400536
next prev parent reply other threads:[~2010-01-29 16:12 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
2010-01-29 15:29 ` Albin Tonnerre
2010-01-29 15:16 ` Russell King - ARM Linux
2010-01-29 16:12 ` Colin Tuckley [this message]
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='000001caa0fd$cef2f740$9fca010a@Emea.Arm.com' \
--to=colin.tuckley@arm.com \
--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).