From: ecc@cmu.edu (Eric Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: kexec on kirkwood kernels?
Date: Wed, 26 Jan 2011 22:00:24 -0500 [thread overview]
Message-ID: <20110127030024.GF19307@localhost> (raw)
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.
--
Eric Cooper e c c @ c m u . e d u
next reply other threads:[~2011-01-27 3:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 3:00 Eric Cooper [this message]
2011-01-27 7:24 ` kexec on kirkwood kernels? Uwe Kleine-König
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=20110127030024.GF19307@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).