linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Dan Williams <dan.j.williams@gmail.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
	thgarnie@google.com, Ingo Molnar <mingo@kernel.org>
Subject: Re: KASLR causes intermittent boot failures on some systems
Date: Sat, 8 Apr 2017 15:52:43 +0800	[thread overview]
Message-ID: <20170408075243.GA26009@x1> (raw)
In-Reply-To: <CAA9_cmcB2Ctxya6yNj6535WashWArsEr2kf1b3bq82=Dsy5fmA@mail.gmail.com>

Hi Dan,

Thanks!

On 04/08/17 at 12:02am, Dan Williams wrote:
> > I got below problem when configure ndctl, didn't find a package named
> > libkmod:
> >
> > ~~~~~~~~~
> > configure: error: Package requirements (libkmod) were not met:
> >
> > No package 'libkmod' found
> 
> kmod-devel provides that dependency. Otherwise ndctl is included in
> Fedora or you can find EPEL 7 packages here:
> 
> https://copr.fedorainfracloud.org/coprs/djbw/ndctl/

I have installed kmod-devel, still the configure error occured. But it
worked for me with the epel repo you provided to install ndctl.

Seems it can't be reproduced on my beaker machine with 18G memory. I did
steps as Jeff said, and reboot more than 5 times, no crash seen.

Below is the abstracted part of boot log.



[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.11.0-rc5+ root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap console=ttyS0,115200n81 LANG=en_US.UTF-8 memmap=15G!4G crashkernel=384M
[    0.000000] x86/fpu: x87 FPU will use FXSAVE
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bf337fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bf338000-0x00000000bf3b8fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bf3b9000-0x00000000bf3b9fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000bf3ba000-0x00000000bf3ccfff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000bf3cd000-0x00000000bf3cdfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bf3ce000-0x00000000bf3defff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000bf3df000-0x00000000bf3e1fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bf3e2000-0x00000000bf446fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000bf447000-0x00000000bf451fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000bf452000-0x00000000bf45cfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bf45d000-0x00000000bf47afff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000bf47b000-0x00000000bf67dfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bf67e000-0x00000000bf7fffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000004bfffffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] e820: user-defined physical RAM map:
[    0.000000] user: [mem 0x0000000000000000-0x000000000009d7ff] usable
[    0.000000] user: [mem 0x000000000009d800-0x000000000009ffff] reserved
[    0.000000] user: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[    0.000000] user: [mem 0x0000000000100000-0x00000000bf337fff] usable
[    0.000000] user: [mem 0x00000000bf338000-0x00000000bf3b8fff] ACPI NVS
[    0.000000] user: [mem 0x00000000bf3b9000-0x00000000bf3b9fff] ACPI data
[    0.000000] user: [mem 0x00000000bf3ba000-0x00000000bf3ccfff] reserved
[    0.000000] user: [mem 0x00000000bf3cd000-0x00000000bf3cdfff] ACPI NVS
[    0.000000] user: [mem 0x00000000bf3ce000-0x00000000bf3defff] reserved
[    0.000000] user: [mem 0x00000000bf3df000-0x00000000bf3e1fff] ACPI NVS
[    0.000000] user: [mem 0x00000000bf3e2000-0x00000000bf446fff] reserved
[    0.000000] user: [mem 0x00000000bf447000-0x00000000bf451fff] ACPI data
[    0.000000] user: [mem 0x00000000bf452000-0x00000000bf45cfff] ACPI NVS
[    0.000000] user: [mem 0x00000000bf45d000-0x00000000bf47afff] reserved
[    0.000000] user: [mem 0x00000000bf47b000-0x00000000bf67dfff] ACPI NVS
[    0.000000] user: [mem 0x00000000bf67e000-0x00000000bf7fffff] usable
[    0.000000] user: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
[    0.000000] user: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    0.000000] user: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] user: [mem 0x0000000100000000-0x00000004bfffffff] persistent (type 12)
[    0.000000] SMBIOS 2.4 present.

  reply	other threads:[~2017-04-08  7: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 [this message]
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
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=20170408075243.GA26009@x1 \
    --to=bhe@redhat.com \
    --cc=dan.j.williams@gmail.com \
    --cc=jmoyer@redhat.com \
    --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).