Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754679AbdDJP5f (ORCPT ); Mon, 10 Apr 2017 11:57:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42972 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754407AbdDJP5c (ORCPT ); Mon, 10 Apr 2017 11:57:32 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 0D2712E6042 Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=jmoyer@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 0D2712E6042 From: Jeff Moyer To: Baoquan He Cc: thgarnie@google.com, mingo@kernel.org, dan.j.williams@intel.com, linux-kernel@vger.kernel.org, linux-nvdimm@ml01.01.org Subject: Re: KASLR causes intermittent boot failures on some systems References: <20170408040837.GD4111@x1> X-PGP-KeyID: 1F78E1B4 X-PGP-CertKey: F6FE 280D 8293 F72C 65FD 5A58 1FF8 A7CA 1F78 E1B4 X-PCLoadLetter: What the f**k does that mean? Date: Mon, 10 Apr 2017 11:57:15 -0400 In-Reply-To: <20170408040837.GD4111@x1> (Baoquan He's message of "Sat, 8 Apr 2017 12:08:37 +0800") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Mon, 10 Apr 2017 15:57:17 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1008 Lines: 25 Baoquan He writes: > On 04/07/17 at 10:41am, Jeff Moyer wrote: >> Hi, >> >> commit 021182e52fe01 ("x86/mm: Enable KASLR for physical mapping memory >> regions") causes some of my systems with persistent memory (whether real >> or emulated) to fail to boot with a couple of different crash >> signatures. The first signature is a NMI watchdog lockup of all but 1 >> cpu, which causes much difficulty in extracting useful information from >> the console. The second variant is an invalid paging request, listed >> below. >> >> On some systems, I haven't hit this problem at all. Other systems >> experience a failed boot maybe 20-30% of the time. To reproduce it, >> configure some emulated pmem on your system. You can find directions >> for that here: https://nvdimm.wiki.kernel.org/ > > I got below problem when configure ndctl, didn't find a package named > libkmod: Sorry, you can skip the ndctl step altogether. This is emulated pmem, so the setting won't stick anyway. -Jeff