public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "cloudy.linux" <cloudy.linux@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: cloudy.linux@gmail.com
Subject: PROBLEM: New 3.5.0-rcx kernel hang after uncompressing the kernel image on Orion ARM machine linkstation pro
Date: Mon, 18 Jun 2012 19:30:06 +0800	[thread overview]
Message-ID: <4FDF113E.4080505@gmail.com> (raw)

I'm running vanilla kernel since 2.6.31 kernel on my linkstaiton pro V2 
box. And they worked very well up to 3.4.x series. But that ends 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 debug 
option in kernel config (CONFIG_BUG, CONFIG_DEBUG_KERNEL, 
CONFIG_EARLY_PRINTK, CONFIG_DEBUG_BUGVERBOSE and 
CONFIG_DEFAULT_MESSAGE_LOGLEVEL to 7) , but still got no further 
information after the above message. The RC might be just too early for 
a normal user like me (in fact I first tried linux-git), but I really 
want to make it boot then I can test the new TDMA/IDMA patch for mv_cesa 
on this orion machine since it seems that there isn't too much caring 
about this SOC anymore.
And I do made a single modification to the source, that's editing the 
mach-type of the linkstation pro to 526 locally so to avoid modifying 
the uImage file generated by the make process. And this always works.
Could someone please help me out? Thanks in advance.

Cloudy

             reply	other threads:[~2012-06-18 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 11:30 cloudy.linux [this message]
2012-06-18 18:31 ` PROBLEM: New 3.5.0-rcx kernel hang after uncompressing the kernel image on Orion ARM machine linkstation pro Simon Baatz
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=4FDF113E.4080505@gmail.com \
    --to=cloudy.linux@gmail.com \
    --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