From: Jeff Moyer <jmoyer@redhat.com>
To: Dave Young <dyoung@redhat.com>
Cc: thgarnie@google.com, mingo@kernel.org, bhe@redhat.com,
dan.j.williams@intel.com, linux-kernel@vger.kernel.org,
linux-nvdimm@ml01.01.org, kexec@lists.infradead.org
Subject: Re: KASLR causes intermittent boot failures on some systems
Date: Wed, 12 Apr 2017 08:52:36 -0400 [thread overview]
Message-ID: <x49tw5t6b57.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20170412084037.GA3894@dhcp-128-65.nay.redhat.com> (Dave Young's message of "Wed, 12 Apr 2017 16:40:37 +0800")
Dave Young <dyoung@redhat.com> writes:
> On 04/12/17 at 04:24pm, Dave Young wrote:
>> I did some tests about emulated pmem via memmap=, kdump kernel hangs or
>> just reboots early during compressing kernel, no clue how to handle it.
>> Since for kdump kernel kaslr is pointless a workaround is use "nokaslr"
>>
>> In Fedora or RHEL, just add "nokaslr" in KDUMP_COMMANDLINE_APPEND
>> in /etc/sysconfig/kdump
>>
>> Can you try if this works?
>
> Oops, your problem is normal boot instead of kdump so this is two
> different problems. Seems we have not met your bug yet..
Correct.
-Jeff
next prev parent reply other threads:[~2017-04-12 12:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 14:41 KASLR causes intermittent boot failures on some systems Jeff Moyer
2017-04-07 14:49 ` Thomas Garnier
2017-04-07 14:51 ` Jeff Moyer
2017-04-07 21:25 ` Kees Cook
2017-04-10 15:49 ` Jeff Moyer
2017-04-10 18:13 ` Kees Cook
2017-04-10 18:22 ` Jeff Moyer
2017-04-10 19:03 ` Kees Cook
2017-04-10 19:18 ` Jeff Moyer
2017-04-08 2:51 ` Baoquan He
2017-04-08 4:08 ` Baoquan He
2017-04-08 7:02 ` Dan Williams
2017-04-08 7:52 ` Baoquan He
2017-04-10 15:57 ` Jeff Moyer
2017-04-12 8:24 ` Dave Young
2017-04-12 8:27 ` Dave Young
2017-04-12 8:40 ` Dave Young
2017-04-12 12:52 ` Jeff Moyer [this message]
2017-04-19 13:36 ` Baoquan He
2017-04-19 14:27 ` Thomas Garnier
2017-04-19 14:34 ` Dan Williams
2017-04-19 14:56 ` Baoquan He
2017-04-19 14:56 ` Thomas Garnier
2017-04-19 14:55 ` Baoquan He
2017-04-20 13:26 ` Baoquan He
2017-04-24 20:37 ` Thomas Garnier
2017-04-24 20:52 ` Dan Williams
2017-04-24 23:07 ` Baoquan He
2017-04-24 23:18 ` Dan Williams
2017-04-24 23:56 ` Baoquan He
2017-04-25 0:41 ` Thomas Garnier
2017-04-25 1:18 ` Baoquan He
2017-05-01 11:32 ` 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=x49tw5t6b57.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=bhe@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=mingo@kernel.org \
--cc=thgarnie@google.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;
as well as URLs for NNTP newsgroup(s).