Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752957AbdIFUwl (ORCPT ); Wed, 6 Sep 2017 16:52:41 -0400 Received: from twin.jikos.cz ([89.185.236.188]:56419 "EHLO twin.jikos.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752801AbdIFUwj (ORCPT ); Wed, 6 Sep 2017 16:52:39 -0400 X-Greylist: delayed 362 seconds by postgrey-1.27 at vger.kernel.org; Wed, 06 Sep 2017 16:52:39 EDT Date: Wed, 6 Sep 2017 22:43:21 +0200 (CEST) From: Jiri Kosina X-X-Sender: jikos@twin.jikos.cz To: Linus Torvalds cc: Ingo Molnar , 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 In-Reply-To: Message-ID: References: <20170904093158.k6pg3ytcbotjlhv5@gmail.com> <20170905214046.ishenhbj7jrtoufc@gmail.com> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 973 Lines: 28 On Tue, 5 Sep 2017, Linus Torvalds wrote: > > And one of those 18 is commit 10af6235e0d3 ("x86/mm: Implement PCID > > based optimization: try to preserve old TLB entries using PCID"), > > which I guess is where the problem might actually start showing up if > > it is pcid. > > Yup, that's what it bisected down to in the end. > > And then rebooting once more into that kernel, but with "nopcid" on > the command line, and it all works. > > I'll go back to top-of-tree just to verify that 'nopcid' thing there > too, but it does seem pretty clear-cut. This is a "me too", observed on my Lenovo thinkpad x270 (so it's not specific to that XPS 13 system at all). The symptom I observe is that an attempt to resume from hibernation proceeds up to reading 100% of the hibernation image, and then reboot happens (IOW looks like triple fault). nopcid cures it, I haven't tried to revert 10af6235e0d3 yet, but looks like it's the same thing. -- Jiri Kosina SUSE Labs