From: Simon Baatz <gmbnomis@gmail.com>
To: "cloudy.linux" <cloudy.linux@gmail.com>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: PROBLEM: New 3.5.0-rcx kernel hang after uncompressing the kernel image on Orion ARM machine linkstation pro
Date: Mon, 18 Jun 2012 20:31:41 +0200 [thread overview]
Message-ID: <20120618183141.GA12544@schnuecks.de> (raw)
In-Reply-To: <4FDF113E.4080505@gmail.com>
On Mon, Jun 18, 2012 at 07:30:06PM +0800, cloudy.linux wrote:
...
> at 3.5-RCx. Both RC2 and RC3 ends the same, the system never boot.
> The serial console shows that the kernel hangs after "Uncompressing
> Linux ... done, booting the kernel" message. I tried to enable some
...
Did you apply the fix for the printk alignment issue?
https://lkml.org/lkml/2012/6/17/52
- Simon
next prev parent reply other threads:[~2012-06-18 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 11:30 PROBLEM: New 3.5.0-rcx kernel hang after uncompressing the kernel image on Orion ARM machine linkstation pro cloudy.linux
2012-06-18 18:31 ` Simon Baatz [this message]
2012-06-19 0:53 ` cloudy.linux
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=20120618183141.GA12544@schnuecks.de \
--to=gmbnomis@gmail.com \
--cc=cloudy.linux@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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