From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>, vincent.weaver@maine.edu
Subject: x86_pmu_start WARN_ON.
Date: Thu, 30 Jan 2014 14:02:53 -0500 [thread overview]
Message-ID: <20140130190253.GA11819@redhat.com> (raw)
I gave Vince's perf_fuzzer a run, hoping to trigger a different perf bug
that I've been seeing. Instead I hit a different bug.
WARNING: CPU: 1 PID: 9277 at arch/x86/kernel/cpu/perf_event.c:1076 x86_pmu_start+0xd1/0x110()
CPU: 1 PID: 9277 Comm: perf_fuzzer Not tainted 3.13.0+ #101
0000000000000009 0000000047887442 ffff88024d043da8 ffffffffbd7387ba
0000000000000000 ffff88024d043de0 ffffffffbd06d28d ffff88024d04bba0
ffff880104c9ef60 0000000000000004 0000000000000002 ffff88024d04bddc
Call Trace:
<IRQ> [<ffffffffbd7387ba>] dump_stack+0x4e/0x7a
[<ffffffffbd06d28d>] warn_slowpath_common+0x7d/0xa0
[<ffffffffbd06d3ba>] warn_slowpath_null+0x1a/0x20
[<ffffffffbd018421>] x86_pmu_start+0xd1/0x110
[<ffffffffbd018b9f>] x86_pmu_enable+0x22f/0x320
[<ffffffffbd150bca>] perf_pmu_enable+0x2a/0x30
[<ffffffffbd152711>] perf_cpu_hrtimer_handler+0xe1/0x1f0
[<ffffffffbd097582>] __run_hrtimer+0x72/0x250
[<ffffffffbd152630>] ? perf_event_context_sched_in.isra.85+0xc0/0xc0
[<ffffffffbd097e97>] hrtimer_interrupt+0x107/0x260
[<ffffffffbd030744>] local_apic_timer_interrupt+0x34/0x60
[<ffffffffbd74deba>] smp_trace_apic_timer_interrupt+0x4a/0x125
[<ffffffffbd74cb2f>] trace_apic_timer_interrupt+0x6f/0x80
<EOI> [<ffffffffbd743e4d>] ? retint_swapgs+0xe/0x13
1076 if (WARN_ON_ONCE(!(event->hw.state & PERF_HES_STOPPED)))
1077 return;
It reproduces pretty quickly for me (within a minute or two of runtime).
Oddly the generated test case from the log file doesn't reproduce.
Dave
next reply other threads:[~2014-01-30 19:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 19:02 Dave Jones [this message]
2014-02-10 21:26 ` x86_pmu_start WARN_ON Vince Weaver
2014-02-11 13:29 ` Peter Zijlstra
2014-02-12 21:04 ` Vince Weaver
2014-02-13 14:11 ` Vince Weaver
2014-02-13 17:35 ` Vince Weaver
2014-02-13 22:13 ` Vince Weaver
2014-02-17 15:28 ` Peter Zijlstra
2014-02-18 18:30 ` Vince Weaver
2014-02-18 22:20 ` Vince Weaver
2014-02-19 10:19 ` Peter Zijlstra
2014-02-19 22:34 ` Vince Weaver
2014-02-20 10:08 ` Peter Zijlstra
2014-02-20 15:47 ` Andi Kleen
2014-02-20 15:54 ` Peter Zijlstra
2014-02-20 17:31 ` Andi Kleen
2014-02-20 18:15 ` Peter Zijlstra
2014-02-20 18:23 ` Andi Kleen
2014-02-20 19:04 ` Steven Rostedt
2014-02-20 16:26 ` Steven Rostedt
2014-02-20 17:00 ` Peter Zijlstra
2014-02-20 17:43 ` Steven Rostedt
2014-02-20 17:46 ` Steven Rostedt
2014-02-20 18:18 ` Peter Zijlstra
2014-02-20 18:03 ` Vince Weaver
2014-02-20 18:23 ` Peter Zijlstra
2014-02-20 18:54 ` Vince Weaver
2014-02-20 19:21 ` Vince Weaver
2014-02-20 19:46 ` Vince Weaver
2014-02-21 14:37 ` Vince Weaver
2014-02-21 15:03 ` Peter Zijlstra
2014-02-21 20:18 ` Vince Weaver
2014-02-24 11:28 ` Peter Zijlstra
2014-02-26 5:59 ` Vince Weaver
2014-02-27 13:32 ` [tip:perf/core] perf/x86: Fix event scheduling tip-bot for Peter Zijlstra
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=20140130190253.GA11819@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).