From: "Thomas D." <whissi@whissi.de>
To: Vivek Goyal <vgoyal@redhat.com>, WANG Chao <chaowang@redhat.com>
Cc: Kexec Mailing List <kexec@lists.infradead.org>,
Kees Cook <keescook@chromium.org>
Subject: Re: kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y is set
Date: Fri, 22 Aug 2014 14:47:39 +0200 [thread overview]
Message-ID: <53F73BEB.40001@whissi.de> (raw)
In-Reply-To: <20140822123811.GD5954@redhat.com>
On 2014-08-22 14:38, Vivek Goyal wrote:
> So may be this failure happens because new kernel stomps over page tables
> of old kernel. But if that theory is right, then we should be able to
> kexec using 32bit entry point of bzImage.
>
> Thomas, have you had any success with that?
When I execute kexec with "--entry-32bit" (I understand that you asked
me to try that) the new kernel will boot as expected.
I'll now try the kernel patch...
-Thomas
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-08-22 12:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 21:02 kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y is set Thomas D.
2014-08-18 14:57 ` Vivek Goyal
2014-08-19 9:07 ` WANG Chao
2014-08-20 14:33 ` Vivek Goyal
2014-08-21 15:57 ` Kees Cook
2014-08-21 18:10 ` Vivek Goyal
2014-08-21 19:02 ` Vivek Goyal
2014-08-21 19:27 ` Thomas D.
2014-08-22 18:18 ` Kexec failing in handle_relocations() (Was: Re: kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y is set) Vivek Goyal
2014-08-21 19:16 ` kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y is set Vivek Goyal
2014-08-22 3:19 ` WANG Chao
2014-08-22 11:59 ` Baoquan He
2014-08-22 12:30 ` Thomas D.
2014-08-22 12:40 ` Vivek Goyal
2014-08-22 13:23 ` Thomas D.
2014-08-22 13:16 ` Vivek Goyal
2014-08-22 14:44 ` Baoquan He
2014-08-22 12:38 ` Vivek Goyal
2014-08-22 12:47 ` Thomas D. [this message]
2014-08-22 12:53 ` Vivek Goyal
2014-08-22 14:59 ` Baoquan He
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=53F73BEB.40001@whissi.de \
--to=whissi@whissi.de \
--cc=chaowang@redhat.com \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.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 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.