From: Michael Casadevall <michael.casadevall@canonical.com>
To: kexec@lists.infradead.org
Subject: kexec on ARM
Date: Mon, 19 Jan 2009 16:29:23 -0500 [thread overview]
Message-ID: <4974F0B3.2030501@canonical.com> (raw)
Hello all,
I've recently been working on trying to use kexec on ARM, but I've been
running into some trouble, which may or may not be user error. I'm
simply using kexec to load another kenel and execute it (for my
purposes, I'm not interested in crash kernel support). I have the host
kernel compiled in with kexec support, and I compiled kexec-tools for
ARM. I can load the second kernel with kexec -l, and see it get loaded,
but I just get a hang when I use kexec -e, I just get a hang. Looking at
the printk's, it seems execution leaves the main kernel, and gets into
the relocation stub before dying. On real hardware, it just hangs, but
on QEMU, I get the following dump on the console:
qemu: fatal: Trying to execute code outside RAM or ROM at 0xc0035460
R00=0f9b6000 R01=000005f8 R02=bf000c12 R03=ceddefc8
R04=0f9b6000 R05=cf9b6000 R06=fee1dead R07=00000000
R08=c002c008 R09=cedaa000 R10=00000000 R11=cedabe6c
R12=00092070 R13=cedabe58 R14=c0030ffc R15=c0035460
PSR=600000d3 -ZC- A svc32
Aborted (core dumped)
[1]+ Exit 134 ./start-arm
I'm hoping this is user error; does the second kernel require something
special such as relocation support? I'm fairly new to kexec so any help
that can be offered would be greatly appreciated.
Michael
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
reply other threads:[~2009-01-19 21:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4974F0B3.2030501@canonical.com \
--to=michael.casadevall@canonical.com \
--cc=kexec@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