From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: 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
Date: Thu, 2 Jul 2015 18:47:02 +0200 [thread overview]
Message-ID: <20150702164702.GA19282@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1507021134030.14637@vincent-weaver-1.umelst.maine.edu>
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
next prev parent reply other threads:[~2015-07-02 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 15:42 perf: fuzzer, lots of warnings Vince Weaver
2015-07-02 16:47 ` Peter Zijlstra [this message]
2015-07-02 17:59 ` Vince Weaver
2015-07-02 18:30 ` Ingo Molnar
2015-07-03 4:48 ` Vince Weaver
2015-07-06 16:36 ` Vince Weaver
2015-07-02 19:48 ` Stephane Eranian
2015-07-03 4:46 ` Vince Weaver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150702164702.GA19282@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=eranian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=vincent.weaver@maine.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox