Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752311AbaBMRd3 (ORCPT ); Thu, 13 Feb 2014 12:33:29 -0500 Received: from mail-qc0-f171.google.com ([209.85.216.171]:38611 "EHLO mail-qc0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751414AbaBMRd2 (ORCPT ); Thu, 13 Feb 2014 12:33:28 -0500 Date: Thu, 13 Feb 2014 12:35:18 -0500 (EST) From: Vince Weaver To: Vince Weaver cc: Peter Zijlstra , Dave Jones , Linux Kernel , Ingo Molnar , Paul Mackerras Subject: Re: x86_pmu_start WARN_ON. In-Reply-To: Message-ID: References: <20140130190253.GA11819@redhat.com> <20140211132956.GY9987@twins.programming.kicks-ass.net> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) 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 On Thu, 13 Feb 2014, Vince Weaver wrote: > On Wed, 12 Feb 2014, Vince Weaver wrote: > > > > It is triggered in this case when you have: > > > > An event group of breakpoint, cycles, branches > > An event of instructions with precise=1 > > A tracepoint > > > > and then you close the tracepoint. > > and for what it's worth, it's the cycles event (type=0 config=0) that's > causing the WARN_ON. The plot thickens. The WARN_ON is not caused by the cycles event that we open, but it's caused by the NMI Watchdog cycles event. I'm not sure if that's useful info or not. Vince -- 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/