From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephane Eranian <eranian@google.com>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: WARNING: at arch/x86/kernel/cpu/perf_event.c:989
Date: Thu, 2 Feb 2012 22:32:20 +0100 [thread overview]
Message-ID: <20120202213220.GB1642@x4> (raw)
In-Reply-To: <20120202211709.GA1642@x4>
On 2012.02.02 at 22:17 +0100, Markus Trippelsdorf wrote:
> The following warning is easily reproducible after todays
> 'perf-urgent-for-mingo' merge by just running "perf top":
>
> ------------[ cut here ]------------
> WARNING: at arch/x86/kernel/cpu/perf_event.c:989 x86_pmu_start+0xa5/0x100()
> Hardware name: System Product Name
> Pid: 0, comm: swapper/2 Not tainted 3.3.0-rc2-00068-g24b36da-dirty #22
> Call Trace:
> <IRQ> [<ffffffff81054ba0>] ? warn_slowpath_common+0x60/0xa0
> [<ffffffff8103e1a5>] ? x86_pmu_start+0xa5/0x100
> [<ffffffff8109f062>] ? perf_adjust_freq_unthr_context.part.82+0xe2/0x140
> [<ffffffff8109f260>] ? perf_event_task_tick+0x1a0/0x280
> [<ffffffff81078be3>] ? scheduler_tick+0xc3/0x140
> [<ffffffff810615b5>] ? update_process_times+0x55/0x80
> [<ffffffff8108904d>] ? tick_sched_timer+0x4d/0xa0
> [<ffffffff81072d1b>] ? __run_hrtimer.isra.32+0x3b/0xc0
> [<ffffffff810735e5>] ? hrtimer_interrupt+0xc5/0x1e0
> [<ffffffff81045de3>] ? smp_apic_timer_interrupt+0x63/0xa0
> [<ffffffff8147768b>] ? apic_timer_interrupt+0x6b/0x70
> <EOI> [<ffffffff81039100>] ? default_idle+0x20/0x40
> [<ffffffff81039172>] ? amd_e400_idle+0x52/0x100
> [<ffffffff81030156>] ? cpu_idle+0xb6/0xe0
> ---[ end trace 7dc3992f562261b6 ]---
Most likely caused by e050e3f0a71b :
perf: Fix broken interrupt rate throttling
CCing Stephane.
--
Markus
next prev parent reply other threads:[~2012-02-02 21:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 21:17 WARNING: at arch/x86/kernel/cpu/perf_event.c:989 Markus Trippelsdorf
2012-02-02 21:32 ` Markus Trippelsdorf [this message]
2012-02-02 22:22 ` Stephane Eranian
2012-02-04 13:51 ` Ingo Molnar
2012-02-04 18:09 ` Stephane Eranian
2012-02-06 9:54 ` Stephane Eranian
2012-02-06 10:12 ` Eric Dumazet
2012-02-06 10:40 ` Stephane Eranian
2012-02-06 11:11 ` Eric Dumazet
2012-02-06 14:13 ` Stephane Eranian
2012-02-06 14:29 ` Peter Zijlstra
2012-02-06 14:32 ` Stephane Eranian
2012-02-06 15:02 ` Peter Zijlstra
2012-02-06 14:38 ` Ingo Molnar
2012-02-06 14:41 ` Stephane Eranian
2012-02-06 15:47 ` Ingo Molnar
2012-02-06 20:44 ` Stephane Eranian
2012-02-06 20:58 ` Peter Zijlstra
2012-02-06 21:25 ` Stephane Eranian
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=20120202213220.GB1642@x4 \
--to=markus@trippelsdorf.de \
--cc=a.p.zijlstra@chello.nl \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.