From: Geoff Levand <geoff@infradead.org>
To: Pratyush Anand <panand@redhat.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Takahiro Akashi <takahiro.akashi@linaro.org>,
kexec@lists.infradead.org, Vivek Goyal <vgoyal@redhat.com>,
Kyle McMartin <kmcmarti@redhat.com>
Subject: Re: arm64 kexec hang
Date: Fri, 27 Mar 2015 10:23:35 -0700 [thread overview]
Message-ID: <1427477015.27739.30.camel@infradead.org> (raw)
Hi Pratyush,
On Wed, 2015-03-25 at 15:55 +0530, Pratyush Anand wrote:
> So with following changes kexec load seems to complete without any
> error. However, kexec reboot does not work yet, Nothing after bye
> message :( (1st kernel booted with maxcpus=1)
'Bye!' doesn't mean much, other than the first kernel has
almost shutdown. I recommend for debugging you either define
ARM64_DEBUG_PORT for the kexec-tools build, or have a suitable
earlyprintk= on the kernel command line. See the read_sink()
routine in kexec-arm64.c.
Either of these will output something like this from the
purgatory code:
I'm in purgatory
purgatory: kernel_entry: 0000000080080000
purgatory: dtb: 0000000080760000
Another option is to add my 'debugging: early putc' patch,
build the kernel with ARM64_DEBUG_PORT defined for your
board. This will output 'stext' when the second
stage kernel is entered
The kexec --lite option will bypass purgatory and should just
show 'stext'.
-Geoff
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2015-03-27 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 17:23 Geoff Levand [this message]
2015-03-27 21:11 ` arm64 kexec hang Pratyush Anand
2015-03-30 12:26 ` Pratyush Anand
2015-03-30 14:38 ` Pratyush Anand
2015-03-30 15:25 ` Pratyush Anand
2015-03-30 16:40 ` Geoff Levand
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=1427477015.27739.30.camel@infradead.org \
--to=geoff@infradead.org \
--cc=kexec@lists.infradead.org \
--cc=kmcmarti@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=panand@redhat.com \
--cc=takahiro.akashi@linaro.org \
--cc=vgoyal@redhat.com \
/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).