Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751497AbdIEJzx (ORCPT ); Tue, 5 Sep 2017 05:55:53 -0400 Received: from ud10.udmedia.de ([194.117.254.50]:43542 "EHLO mail.ud10.udmedia.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750775AbdIEJzu (ORCPT ); Tue, 5 Sep 2017 05:55:50 -0400 Date: Tue, 5 Sep 2017 11:55:47 +0200 From: Markus Trippelsdorf To: Peter Zijlstra Cc: linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar Subject: Re: Current mainline git (24e700e291d52bd2) hangs when building e.g. perf Message-ID: <20170905095547.GA286@x4> References: <20170905072738.GA277@x4> <20170905085350.cgi7shvnillbikow@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170905085350.cgi7shvnillbikow@hirez.programming.kicks-ass.net> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1127 Lines: 35 On 2017.09.05 at 10:53 +0200, Peter Zijlstra wrote: > On Tue, Sep 05, 2017 at 09:27:38AM +0200, Markus Trippelsdorf wrote: > > Current mainline git (24e700e291d52bd2) hangs when building software > > concurrently (for example perf). > > The issue is not 100% reproducible (sometimes building perf succeeds), > > so bisecting will not work. > > Sadly I cannot reproduce, I had: > > while :; do make clean; make; done > > running on tools/perf for a while, and now have: > > while :; do make O=defconfig-build clean; make O=defconfig-build -j80; done > > running, all smooth sailing, although there's the hope that the moment I > hit send on this email the box comes unstuck. > > > Magic SysRq key doesn't work and there is nothing in the logs. > > Enabling CONFIG_PROVE_LOCKING makes the issue go away. > > SysRq not working is suspicious.. and I take it the NMI watchdog also > isn't firing? Yes. > > Any ideas on how to debug this further? > > So you have a (real) serial line on that box? Sadly, no. But hopefully somebody else (with a proper kernel debugging setup) will reproduce the issue soon. -- Markus