From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: Linux Kernel boot up stops after message "Uncompressing Linux....done, booting the kernel"
Date: Thu, 24 May 2012 12:32:21 +0200 [thread overview]
Message-ID: <20120524103221.GA1889@glitch> (raw)
In-Reply-To: <CACZ0kf9yHJOAVEBx4e5dc_eCRT5dScrZHzbkx3_7P2QkzaHChQ@mail.gmail.com>
On Thu, May 24, 2012 at 10:52:46AM +0530, K K wrote:
> Hi,
Hi,
> We have a lpc-3180 based board and it is up and running fine with 2.6.10
> kernel version. We planned to port our board changes into 2.6.32 kernel
> version.
2.6.32, really?
> kernel build successfully. When we booting the board with the new 2.6.32
> kernel we are getting following messages and its stops.
Two cases:
1. earlyprintk is configured and enabled but points to the
wrong console and your platform hangs on it because it's not
initialized/ready. the correct console seems ok, the uncompressor
is able to use it. check debug-macro.S to be sure it uses the
correct address.
2. earlyprintk is not enabled (or configured) and your kernel is
not finding the console (any console= on the cmdline? driver
issue?) or dies before finding it. try enabling earlyprintk (and
check debug-macro.S as well).
cheers,
Domenico
ps: post also the kernel configuration
next prev parent reply other threads:[~2012-05-24 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACZ0kf88Ac8hne9RtLObi624okPw8Nkiv7++Uw8npPLW108mhw@mail.gmail.com>
2012-05-24 5:22 ` Linux Kernel boot up stops after message "Uncompressing Linux....done, booting the kernel" K K
2012-05-24 10:32 ` Domenico Andreoli [this message]
2012-05-24 10:56 ` Baruch Siach
2012-05-25 12:50 ` K K
2012-05-24 13:13 ` Arend van Spriel
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=20120524103221.GA1889@glitch \
--to=cavokz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.