From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: kexec on kirkwood kernels?
Date: Thu, 27 Jan 2011 08:24:33 +0100 [thread overview]
Message-ID: <20110127072433.GI1147@pengutronix.de> (raw)
In-Reply-To: <20110127030024.GF19307@localhost>
Hallo,
On Wed, Jan 26, 2011 at 10:00:24PM -0500, Eric Cooper wrote:
> Has anyone successfully used kexec to boot one kirkwood kernel from
> another? I've been trying to do it on a Seagate DockStar, but
> all I see is this:
>
> # kexec -l --append="console=ttyS0,115200" zImage
> # kexec -e
> [ 35.553632] Starting new kernel
> Uncompressing Linux... done, booting the kernel.
>
> and then nothing. I've tried with both 2.6.35 and 2.6.38-rc1 kernels.
> I've tried modifying the kernel image to set the machine ID
> explicitly, but that makes no difference. I wonder if the boot
> parameters are being passed correctly, but I don't know how to check
> without any console output. I do have a JTAG setup, but so far I've
> only used it cookbook-fashion to re-flash the u-boot NAND partition.
> I'm hoping someone can help me avoid having to use gdb over JTAG to
> resolve this. Thanks.
Try enabling DEBUG_LL and EARLY_PRINTK in the kernel to boot and pass
earlyprintk
as kernel parameter.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-01-27 7: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 [this message]
2011-01-28 3:24 ` Eric Cooper
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=20110127072433.GI1147@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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.