Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752996AbdIEVkv (ORCPT ); Tue, 5 Sep 2017 17:40:51 -0400 Received: from mail-wm0-f65.google.com ([74.125.82.65]:38627 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751413AbdIEVku (ORCPT ); Tue, 5 Sep 2017 17:40:50 -0400 X-Google-Smtp-Source: ADKCNb5vyUe8l3oe3hiVLTkLV67XrWHm6m8fHNiHEOEOYqomejIUn7Pn8qTsQ4aJ1h/nPiUv4lfZPA== Date: Tue, 5 Sep 2017 23:40:46 +0200 From: Ingo Molnar To: Linus Torvalds Cc: Linux Kernel Mailing List , Thomas Gleixner , "H. Peter Anvin" , Peter Zijlstra , Andrew Morton , Andy Lutomirski , Borislav Petkov Subject: Re: [GIT PULL] x86/mm changes for v4.14: PCID support, 5-level paging support, Secure Memory Encryption support Message-ID: <20170905214046.ishenhbj7jrtoufc@gmail.com> References: <20170904093158.k6pg3ytcbotjlhv5@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1507 Lines: 40 * 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. > > 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. Hm, just as background, there are no regression reports I'm aware of against any of these trees, plus most of the dangerous commits have been in linux-next for at least two weeks - the majority of them even longer. The last 2-4 commits of x86/mm are fresher. But it could be a regression in an older commit in x86/mm just as well, triggered by you for the first time :-/ Does your laptop CPU have PCID support by any chance? The CPU coming out of resume with PCID disabled and us not properly re-enabling it might be a possible failure mode. Thanks, Ingo