[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJcbSZEWB27HHtP6zVQA+qJJ7uvWqZz+Y-kYFE0aTM2-jj72iQ@mail.gmail.com>
Date: Mon, 24 Apr 2017 17:41:27 -0700
From: Thomas Garnier <thgarnie@...gle.com>
To: Baoquan He <bhe@...hat.com>
Cc: Dan Williams <dan.j.williams@...el.com>,
Jeff Moyer <jmoyer@...hat.com>, Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>
Subject: Re: KASLR causes intermittent boot failures on some systems
On Mon, Apr 24, 2017 at 4:07 PM, Baoquan He <bhe@...hat.com> wrote:
> Yeah, according to my debugging tracking, it goes as Dan said. And the
> is_ram is REGION_DISJOINT. And till arch_add_memory, the parameters
> passed to arch_add_memory are "arch_add_memory, align_start:0x10000000000, align_size:0x3000000000",
> seems it's going well.
Hum ok, I hope it was another path given it seems the page table is
correctly setup on this one.
Maybe looking at the PTEs with and without crash might help? (setting
this if statement to 1:
http://lxr.free-electrons.com/source/arch/x86/mm/init_64.c#L360)
Thanks Baoquan,
--
Thomas
Powered by blists - more mailing lists