linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: KEXEC on ARM cortex-a15
Date: Wed, 21 Nov 2012 10:22:44 +0000	[thread overview]
Message-ID: <20121121102244.GA11990@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CAJXQGfL4PRW9=MQO1XbogA40sHUzXorbFMe1WkiJ751Ej-h7=g@mail.gmail.com>

On Wed, Nov 21, 2012 at 08:21:21AM +0000, Naresh Bhat wrote:
> Hi Will,
> 
> I have disabled the SMP on host kernel.  But still I am facing the
> issue as below
> 
> bash-4.2# ls
> uImage  vexpress.dtb
> bash-4.2#
> bash-4.2# kexec -f uImage --dtb=vexpress.dtb --command-line="console=ttyS0"

Can you try using a zImage instead and also specifying the console as
ttyAMA0, as it looks like you're using a vexpress?

> Starting new kernel
> Bye!
> Uncompressing Linux...

This isn't really very helpful -- some more debugging on your part would be
appreciated to get an insight as to what's going wrong. You could either use
JTAG or put some early prints in the decompressor to work out where it goes
awry.

Useful things to know would be: the state of the CPU when the new kernel
image is entered (if you have JTAG, you could also look at the dtb in memory
to see that it looks sane) and also at which point in the decompressor it
goes wrong / takes an abort (usually it's when we enable the MMU).

Will

  reply	other threads:[~2012-11-21 10:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 14:27 KEXEC on ARM cortex-a15 Naresh Bhat
2012-11-19 14:44 ` Russell King - ARM Linux
2012-11-19 15:13   ` Will Deacon
2012-11-19 15:38     ` Naresh Bhat
2012-11-20 15:02       ` Naresh Bhat
2012-11-20 16:02         ` Will Deacon
2012-11-20 17:14           ` Naresh Bhat
2012-11-21  8:21           ` Naresh Bhat
2012-11-21 10:22             ` Will Deacon [this message]
2012-11-21 11:20               ` Naresh Bhat
2012-11-21 18:47               ` Naresh Bhat
2012-12-17 13:11               ` Naresh Bhat
2013-01-10 12:12               ` Naresh Bhat

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=20121121102244.GA11990@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --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).