From: ecc@cmu.edu (Eric Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: kexec on kirkwood kernels?
Date: Thu, 27 Jan 2011 22:24:54 -0500 [thread overview]
Message-ID: <20110128032454.GG22555@localhost> (raw)
In-Reply-To: <20110127072433.GI1147@pengutronix.de>
On Thu, Jan 27, 2011 at 08:24:33AM +0100, Uwe Kleine-K?nig wrote:
> Try enabling DEBUG_LL and EARLY_PRINTK in the kernel to boot and pass
> earlyprintk
> as kernel parameter.
Thanks, that helped quite a bit. After inserting various print
statements, I found that the system is hanging in the readl call in
orion_pcie_dev_id. The call chain is:
start_kernel
time_init
kirkwood_timer_init
kirkwood_find_tclk
kirkwood_pcie_id
orion_pcie_dev_id
readl
The readl is attempting to access the address
KIRKWOOD_REGS_VIRT_BASE + 0x40000.
This same code gets executed successfully when the kernel is started
from u-boot; I'm not sure what's different in the post-kexec
environment. Any suggestions on what to try next would be
appreciated.
--
Eric Cooper e c c @ c m u . e d u
next prev parent reply other threads:[~2011-01-28 3:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 3:00 kexec on kirkwood kernels? Eric Cooper
2011-01-27 7:24 ` Uwe Kleine-König
2011-01-28 3:24 ` Eric Cooper [this message]
2011-01-29 5:47 ` Eric Miao
2011-01-29 22:48 ` Eric Cooper
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=20110128032454.GG22555@localhost \
--to=ecc@cmu.edu \
--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).