From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: WANG Chao <chaowang@redhat.com>
Cc: kexec@lists.infradead.org
Subject: Re: kexec/kdump fails to load in ELF symbol relocation on ppc64 arch
Date: Tue, 22 Jul 2014 15:54:29 +0200 [thread overview]
Message-ID: <53CE6D15.9060509@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140722104255.GF13924@dhcp-17-37.nay.redhat.com>
On 22/07/2014 12:42, WANG Chao wrote:
> Hi, Laurent
>
> With gcc -fexceptions, kexec/kdump fails to load:
>
> # kexec -p /boot/vmlinuz
> Warning: append= option is not passed. Using the first kernel root partition
> REL24 -157778404 out of range!
Hi Chao,
I think the root cause of the issue is due to an unresolved symbol in
the purgatory. The '_Unwind_Resume' symbol mentioned in the log is
generated by GCC which assumes it will find it somewhere when linking
with the according shared library.
The purgatory is not linked with any library and thus should not be
instrumented as the -fexecptions GCC's option does.
This should be similar to the fix I've done through the commit
7d33c8933ebf where the stack protection mechanism was introducing
unresolved symbols.
I'll look for a patch which is disabling the GCC -fexceptions option
when building the purgatory.
Laurent.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-07-22 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 10:42 kexec/kdump fails to load in ELF symbol relocation on ppc64 arch WANG Chao
2014-07-22 13:54 ` Laurent Dufour [this message]
2014-07-22 16:22 ` [PATCH] kexec/ppc64: disabling exception handling when building the purgatory Laurent Dufour
2014-07-23 0:02 ` Simon Horman
2014-07-23 0:02 ` Simon Horman
2014-07-24 6:15 ` WANG Chao
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=53CE6D15.9060509@linux.vnet.ibm.com \
--to=ldufour@linux.vnet.ibm.com \
--cc=chaowang@redhat.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