From: Pratyush Anand <panand@redhat.com>
To: Geoff Levand <geoff@infradead.org>
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: Mon, 30 Mar 2015 20:55:31 +0530 [thread overview]
Message-ID: <55196AEB.2040204@redhat.com> (raw)
In-Reply-To: <55195FE3.5090409@redhat.com>
Hi Geoff,
On Monday 30 March 2015 08:08 PM, Pratyush Anand wrote:
> diff --git a/kexec/arch/arm64/kexec-arm64.c
> b/kexec/arch/arm64/kexec-arm64.c
> index 8df66f5c8273..4365bb4087ad 100644
> --- a/kexec/arch/arm64/kexec-arm64.c
> +++ b/kexec/arch/arm64/kexec-arm64.c
> @@ -993,8 +993,8 @@ void machine_apply_elf_rel(struct mem_ehdr *ehdr,
> unsigned long r_type,
> # define R_AARCH64_CALL26 283
> #endif
>
> - uint32_t *location = (uint32_t *)ptr;
> - uint32_t data = *location;
> + uint64_t *location = (uint64_t *)ptr;
> + uint64_t data = *location;
> const char *type = NULL;
>
> switch(r_type) {
> @@ -1026,7 +1026,7 @@ void machine_apply_elf_rel(struct mem_ehdr *ehdr,
> unsigned long r_type,
> break;
> }
>
> - dbgprintf("%s: %s %x->%x\n", __func__, type, data, *location);
> + dbgprintf("%s: %s %lx->%lx\n", __func__, type, data, *location);
> }
Thanks for your help/pointer.
So, this was it. With above changes kexec reboot works fine with
purgatory too.
By the way, how much execution time expected for verify_sha256_digest? I
have not quantified, but it seems that it takes minutes to execute that.
~Pratyush
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-03-30 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 17:23 arm64 kexec hang Geoff Levand
2015-03-27 21:11 ` Pratyush Anand
2015-03-30 12:26 ` Pratyush Anand
2015-03-30 14:38 ` Pratyush Anand
2015-03-30 15:25 ` Pratyush Anand [this message]
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=55196AEB.2040204@redhat.com \
--to=panand@redhat.com \
--cc=geoff@infradead.org \
--cc=kexec@lists.infradead.org \
--cc=kmcmarti@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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).