From: narkewoody@gmail.com (woody)
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel uncompression error
Date: Wed, 14 Nov 2012 22:23:55 +0800 [thread overview]
Message-ID: <k809hq$1q3$1@ger.gmane.org> (raw)
Hi, List
I just built a 3.2.x ARM kernel and tried to have it boot by a boot
loader (vivi) on my s3c2410a ARM board. The kernel was built with
default configuration s3c2410.
... But, the following error printed on the console:
---------------------
Uncompressing Linux...
uncompression error
-- System halted
---------------------
What kinds of reasons can most possibly lead the error? I searched on
the net and found some answers, but I cannot well judge them:
1. There is a D-Cache patch should be applied, but the message was
talking about 2.4.x kernel, so I guess if there really was a bug around
here, it should already been fixed. Right?
2. Probably the kernel image (here is a zImage) is too big, then the
uncompressed code was overwriting the original compressed part of the
image. This sounds a little relevant. My boot loader was loading the
kernel image to ram address 0x300008000, and my zImage is about 1.9M.
Do you think this is the reason?
Thanks in advance!
--
woody
I can't go back to yesterday - because I was a different person then.
next reply other threads:[~2012-11-14 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 14:23 woody [this message]
2012-11-14 17:34 ` Kernel uncompression error Russell King - ARM Linux
2012-11-14 23:40 ` Woody Wu
2012-11-15 5:56 ` woody
2012-11-15 9:32 ` Russell King - ARM Linux
2012-11-15 11:22 ` Arnaud Patard (Rtp)
2012-11-15 11:32 ` Vasily Khoruzhick
[not found] ` <CAAsE_ufdjZN31BXWTcq5XyRhx5YcoECRJVvARcNh8qT-AP1_jw@mail.gmail.com>
2012-11-15 9:33 ` Russell King - ARM Linux
2012-11-15 17:25 ` Woody Wu
2012-11-21 1:34 ` Woody Wu
2012-11-15 11:29 ` Vasily Khoruzhick
2012-11-15 11:31 ` Russell King - ARM Linux
2012-11-21 0:43 ` [PATCH] S3C24XX: Fix console baud rate guessing Domenico Andreoli
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='k809hq$1q3$1@ger.gmane.org' \
--to=narkewoody@gmail.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).