Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Geoff Levand <geoff@infradead.org>
To: Anurup M <anurup.m@huawei.com>
Cc: sanil.kumar@hisilicon.com, kexec@lists.infradead.org
Subject: Re: [PATCH 0/8] arm64 kexec kernel patches V6
Date: Wed, 19 Nov 2014 17:19:42 -0800	[thread overview]
Message-ID: <1416446382.23886.90.camel@smoke> (raw)
In-Reply-To: <546AE4BE.1020909@huawei.com>

On Tue, 2014-11-18 at 11:48 +0530, Anurup M wrote:
> 	I get a relocation error  when I try to load using latest kexec-tools from https://git.linaro.org/people/geoff.levand/kexec-tools.git.
> 
> ############## error log ###############
> machine_apply_elf_rel: CALL26 94000000->97ffff62
> sym: sha256_update info: 12 other: 00 shndx: 1 value: 5f58 size: 16c
> sym: sha256_update value: 81af7f58 addr: 81af81e4
> machine_apply_elf_rel: CALL26 94000000->97ffff5d
> sym:      .data info: 03 other: 00 shndx: 4 value: 0 size: 0
> sym: .data value: 81af8630 addr: 81af8550
> machine_apply_elf_rel: ABS64 0->81af8630
> Symbol: sha256_regions is in a bss section cannot set
> ##############
> 
> 	What should be the problem? 

It seems either your purgatory code was not built correctly,
or the kexec-tools relocator didn't do the correct thing.

Please post the output from your gcc with the --version option and
the command line used to compile purgatory/purgatory.c.

> I use foundation model and the kernel image from
> https://git.linaro.org/people/geoff.levand/linux-kexec.git branch: origin/kexec-v6
> and rootfs from Linaro (http://releases.linaro.org/14.09/openembedded/aarch64)
> 
> 	The above error is not seen when I use kexec-tools branch: origin/kdump.
> 
> 	Also wish to know how to verify the kdump feature.

As I mentioned before, these patches only add kexec re-boot support.  kdump
has not been ported to arm64 yet.

-Geoff




_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2014-11-20  1:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D2393EB95A9993478029A6FE6A290A9F8129D1FE@szxeml510-mbx.china.huawei.com>
2014-11-18  6:18 ` [PATCH 0/8] arm64 kexec kernel patches V6 Anurup M
2014-11-20  1:19   ` Geoff Levand [this message]
2014-11-20 22:57   ` Geoff Levand
2014-11-20 23:31     ` Geoff Levand
2014-12-02 13:39       ` Anurup m
2014-12-02 20:30         ` Geoff Levand
2014-11-14  1:22 Geoff Levand
2014-11-27  6:19 ` Dave Young
2014-11-28  6:56   ` Dave Young
2014-12-02 20:26     ` Geoff Levand
2014-12-02 20:22   ` 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=1416446382.23886.90.camel@smoke \
    --to=geoff@infradead.org \
    --cc=anurup.m@huawei.com \
    --cc=kexec@lists.infradead.org \
    --cc=sanil.kumar@hisilicon.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