From: "Thomas D." <whissi@whissi.de>
To: kexec@lists.infradead.org
Subject: kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y is set
Date: Sun, 17 Aug 2014 23:02:58 +0200 [thread overview]
Message-ID: <53F11882.3060803@whissi.de> (raw)
Hi,
looks like kexec doesn't support kernels where
CONFIG_RANDOMIZE_BASE=y
is set.
I already created a bug for Debian in June for this problem [1].
I am able to confirm the same problem with kexec 2.0.7 on Gentoo and
when building from source (943ba35f8143408d8ada9a24d0986663cc612df9).
Is this a known problem/limitation?
Is there anything I can help you with to get this fixed?
Thanks.
See also:
=========
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754288
-Thomas
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2014-08-17 21:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 21:02 Thomas D. [this message]
2014-08-18 14:57 ` kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y is set 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.
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=53F11882.3060803@whissi.de \
--to=whissi@whissi.de \
--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 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.