Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754836AbbGCKI3 (ORCPT ); Fri, 3 Jul 2015 06:08:29 -0400 Received: from casper.infradead.org ([85.118.1.10]:53618 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754875AbbGCKIV (ORCPT ); Fri, 3 Jul 2015 06:08:21 -0400 Date: Fri, 3 Jul 2015 12:08:09 +0200 From: Peter Zijlstra To: Vince Weaver Cc: linux-kernel@vger.kernel.org, Ingo Molnar , Arnaldo Carvalho de Melo , Stephane Eranian , kan.liang@intel.com Subject: Re: perf: fuzzer triggered CPU lockup Message-ID: <20150703100809.GF19282@twins.programming.kicks-ass.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 968 Lines: 20 On Thu, Jul 02, 2015 at 11:31:15PM -0400, Vince Weaver wrote: > On Thu, 2 Jul 2015, Vince Weaver wrote: > > > The fuzzer just turned this up. This is the first part; a huge amount of > > CPU lockup messages, rcu stalls, and spinlock lockup suspected messages > > followed beyond what I've posted here but eventually the machine recovered (?) > > > [20602.134103] [] ? intel_pmu_drain_pebs_nhm+0x176/0x2e0 > > after a reboot I am still getting these, in addition to the other > intel_pmu_drain_pebs_nhm related warning. Do I need to try to bisect this > down? I think I have a fairly good idea which patches to blame for that; there's been a rework of the pebs code there. Let me go have a look. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/