Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754035AbdIHKfT (ORCPT ); Fri, 8 Sep 2017 06:35:19 -0400 Received: from mail-wm0-f48.google.com ([74.125.82.48]:46333 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751548AbdIHKfS (ORCPT ); Fri, 8 Sep 2017 06:35:18 -0400 X-Google-Smtp-Source: ADKCNb69uQ4/kg6X3QIcDcp18H+WbQbzQHEPRJ+8WcmmLrLOVhv+EawqPCgsRV2GwCb2tmT5KS305w== Date: Fri, 8 Sep 2017 12:35:13 +0200 From: Ingo Molnar To: Markus Trippelsdorf Cc: Borislav Petkov , Thomas Gleixner , Peter Zijlstra , LKML , Ingo Molnar , Andy Lutomirski , Tom Lendacky Subject: Re: Current mainline git (24e700e291d52bd2) hangs when building e.g. perf Message-ID: <20170908103513.npjmb2kcjt2zljb2@gmail.com> References: <20170905085350.cgi7shvnillbikow@hirez.programming.kicks-ass.net> <20170905095547.GA286@x4> <20170906131504.GA282@x4> <20170907062845.GA280@x4> <20170908053534.GA276@x4> <20170908080536.ninspvplibd37fj2@pd.tnic> <20170908091614.nmdxjnukxowlsjja@pd.tnic> <20170908094815.GA278@x4> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170908094815.GA278@x4> 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: 1062 Lines: 31 * Markus Trippelsdorf wrote: > On 2017.09.08 at 11:16 +0200, Borislav Petkov wrote: > > On Fri, Sep 08, 2017 at 10:05:36AM +0200, Borislav Petkov wrote: > > > On Fri, Sep 08, 2017 at 08:26:44AM +0200, Thomas Gleixner wrote: > > > > On Fri, 8 Sep 2017, Markus Trippelsdorf wrote: > > > > > > > > CC+ Borislav. He might have access to such a beast > > > > > > Can I have /proc/cpuinfo and dmesg pls, in order to see whether I have > > > something similar? > > > > > > Private mail's fine too. > > > > So I don't have exactly your model - mine is model 2, stepping 3 but I see > > something strange too, in dmesg: > > I'm pretty sure the bug is in the merged 'x86-mm-for-linus' branch: > Either Andy's "PCID optimized TLB flushing" (would be my guess) or > 'encrypted memory' support by Tom Lendacky. > > (Bisecting is hard, because sometimes I can compile stuff for over 15 > minutes without hitting the bug. At other times the machine locks up > hard when starting X11 already.) Do you have the 72c0098d92ce fix? Thanks, Ingo