All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Simon Horman <horms@verge.net.au>
Cc: Mariano Lopez <mariano.lopez@linux.intel.com>,
	Yinghai Lu <yinghai@kernel.org>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: commit 5edcbfd1368e break kexec on x86-64
Date: Mon, 04 May 2015 10:09:10 -0500	[thread overview]
Message-ID: <55478B96.4060706@linux.intel.com> (raw)
In-Reply-To: <20150501011556.GJ13754@verge.net.au>

Hi Simon,

Sorry about the problems that i caused, i was out from office.
I'm working in for a solution.

Best regards,
     alimon

On 30/04/15 20:15, Simon Horman wrote:
> On Thu, Apr 30, 2015 at 02:09:44PM +0900, Simon Horman wrote:
>> On Wed, Apr 29, 2015 at 03:36:17PM -0700, Yinghai Lu wrote:
>>> with
>>>
>>> commit 5edcbfd1368e84fce913ceeeca7b712c524dc20d
>>> Author: Aníbal Limón <anibal.limon@linux.intel.com>
>>> Date:   Thu Mar 26 16:19:58 2015 +0000
>>>
>>>      x86_64: Add support to build kexec-tools with x32 ABI
>>>
>>>
>>> after built kexec on opensuse 13.1 64bit, now when using kexec load
>>> kernel, I got
>>>
>>> overflow in relocation type R_X86_64_32 val 21dffc020
>>>
>>> revert that commit and the one after it, kexec is working again.
>> Thanks for bringing this to my attention.
>>
>> My current plan is to revert the above patch from the kexec tree
>> unless a fix is forthcoming by tomorrow.
> I have reverted the above commit.
>
> Aníbal and others, I am more than happy to consider a revised
> version of the above patch or another solution to the problem it
> aimed to solve.


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

  reply	other threads:[~2015-05-04 15:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 22:36 commit 5edcbfd1368e break kexec on x86-64 Yinghai Lu
2015-04-30  5:09 ` Simon Horman
2015-05-01  1:15   ` Simon Horman
2015-05-04 15:09     ` Aníbal Limón [this message]
2015-05-04 15:56       ` Aníbal Limón
2015-05-04 16:49         ` Yinghai Lu
2015-05-04 22:09           ` Aníbal Limón

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=55478B96.4060706@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=mariano.lopez@linux.intel.com \
    --cc=yinghai@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.