Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754050AbbGCEks (ORCPT <rfc822;w@1wt.eu>);
	Fri, 3 Jul 2015 00:40:48 -0400
Received: from mail-ig0-f177.google.com ([209.85.213.177]:35142 "EHLO
	mail-ig0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751685AbbGCEkk (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 3 Jul 2015 00:40:40 -0400
From: Vince Weaver <vincent.weaver@maine.edu>
X-Google-Original-From: Vince Weaver <vince@vincent-weaver-1.umelst.maine.edu>
Date: Fri, 3 Jul 2015 00:46:48 -0400 (EDT)
To: Vince Weaver <vincent.weaver@maine.edu>
cc: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org,
        Ingo Molnar <mingo@redhat.com>,
        Arnaldo Carvalho de Melo <acme@kernel.org>,
        Stephane Eranian <eranian@gmail.com>
Subject: Re: perf: fuzzer, lots of warnings
In-Reply-To: <alpine.DEB.2.20.1507021356470.15205@vincent-weaver-1.umelst.maine.edu>
Message-ID: <alpine.DEB.2.20.1507030044320.16899@vincent-weaver-1.umelst.maine.edu>
References: <alpine.DEB.2.20.1507021134030.14637@vincent-weaver-1.umelst.maine.edu> <20150702164702.GA19282@twins.programming.kicks-ass.net> <alpine.DEB.2.20.1507021356470.15205@vincent-weaver-1.umelst.maine.edu>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1752
Lines: 39

On Thu, 2 Jul 2015, Vince Weaver wrote:

> On Thu, 2 Jul 2015, Peter Zijlstra wrote:
> 
> > On Thu, Jul 02, 2015 at 11:42:43AM -0400, Vince Weaver wrote:
> > > (#4)
> > > 
> > > [ 1638.702578] WARNING: CPU: 2 PID: 25543 at arch/x86/kernel/cpu/perf_event_intel_lbr.c:349 intel_pmu_lbr_disable+0xbc/0xd0()
> > > 
> > > 	WARN_ON_ONCE(cpuc->lbr_users < 0);
> > > 
> > > [ 1638.857921]  [<ffffffff8102e56c>] intel_pmu_lbr_disable+0xbc/0xd0
> > > [ 1638.864874]  [<ffffffff81031812>] intel_pmu_disable_event+0xc2/0x130
> > > [ 1638.872125]  [<ffffffff81030a49>] ? __intel_pmu_disable_all+0x49/0x70
> > > [ 1638.879455]  [<ffffffff81029175>] x86_pmu_stop+0x75/0xd0
> > > [ 1638.885560]  [<ffffffff81159f1a>] perf_ioctl+0x40a/0x470
> > > [ 1638.891650]  [<ffffffff811f199a>] do_vfs_ioctl+0x2ba/0x4a0
> > > [ 1638.897945]  [<ffffffff811dd9ac>] ? vfs_read+0x11c/0x130
> > > [ 1638.904069]  [<ffffffff811f27bd>] ? poll_select_set_timeout+0x4d/0x70
> > > [ 1638.911417]  [<ffffffff811f1bf9>] SyS_ioctl+0x79/0x90
> > > [ 1638.917295]  [<ffffffff816a64b2>] entry_SYSCALL_64_fastpath+0x16/0x7a
> > 
> > This might maybe help:
> > 
> > http://lkml.kernel.org/r/20150624144750.GJ18673@twins.programming.kicks-ass.net

I applied that patch and while the lbr_disable warning hasn't re-appeared 
I am still getting a lot of NMI dazed and confused messages.

Though that might be normal, I think I've always gotten NMI dazed and 
confused messages (although a bit more frequently on the core2 box than 
the haswell one).

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/