Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753305AbdIEVhq (ORCPT ); Tue, 5 Sep 2017 17:37:46 -0400 Received: from mail-pg0-f50.google.com ([74.125.83.50]:35536 "EHLO mail-pg0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752703AbdIEVho (ORCPT ); Tue, 5 Sep 2017 17:37:44 -0400 X-Google-Smtp-Source: ADKCNb6Td69j7YZO/zqNyg6KmH5IAAO1lY/+nJmYK6qsNHpGemi5wQiG6Tmd2sFL4jnmu7ND2r1HQw== Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: [GIT PULL] x86/mm changes for v4.14: PCID support, 5-level paging support, Secure Memory Encryption support From: Andy Lutomirski X-Mailer: iPhone Mail (14G60) In-Reply-To: Date: Tue, 5 Sep 2017 14:37:41 -0700 Cc: Ingo Molnar , Linux Kernel Mailing List , Thomas Gleixner , "H. Peter Anvin" , Peter Zijlstra , Andrew Morton , Andy Lutomirski , Borislav Petkov Message-Id: <50B32556-4ABD-424B-B01C-C314EEC33355@amacapital.net> References: <20170904093158.k6pg3ytcbotjlhv5@gmail.com> To: Linus Torvalds Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by nfs id v85LbqY7001121 Content-Length: 1349 Lines: 34 > On Sep 5, 2017, at 2:17 PM, Linus Torvalds wrote: > >> On Mon, Sep 4, 2017 at 2:31 AM, Ingo Molnar wrote: >> >> Please pull the latest ... git tree from: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ... > > Hmm. My laptop (XPS 13) doesn't resume any more. It suspends, but > doesn't come back from resume. > You could try booting with nopcid to rule out CR4 issues. I can also imagine SME's very clever CR3 masking causing a problem. Unfortunately, if it's a PCID problem involving wrong ordering of CR4 initialization, you might get lucky if you suspend with ASID 0 active, causing unfortunate bisection results. I will test on my XPS 13 after lunch. > I immediately assumed it was the power management pulls I just did, > but then I started bisecting, and now it's actually pointing into the > various x86 pulls I did yesterday instead. > > Now, I'm reasonably early in my bisection (so literally "somewhere > between the 'docs-next' and the 'x86-mm-for-linus' pull), and maybe > the problem isn't even entirely repeatable and my bisection has > already gone off the rails, but I thought I'd give at least an early > heads-up about this thing. > > I'll have more as it bisects deeper into the merge window, but it > might be a while. > > Linus