From: David Ahern <dsahern@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
x86@kernel.org
Subject: Re: Hmm.. WARN_ON_ONCE(cpuc->enabled)
Date: Thu, 09 Feb 2012 17:13:05 -0700 [thread overview]
Message-ID: <4F346111.1040506@gmail.com> (raw)
In-Reply-To: <CA+55aFyXyfYd+_NJ8kLYz-bk7Qt0SLHu4t7RN1PCQptt75RGXQ@mail.gmail.com>
On 02/09/2012 04:46 PM, Linus Torvalds wrote:
> Ok, so I get the appended on my Core i5 when I did a "perf record -f
> -e cycles:pp make -j" on the kernel build.
>
> What's up, guys? I haven't tried that particular perf run in a while,
> so it might have been going on for quite some time.
Perhaps already fixed by
https://lkml.org/lkml/2012/2/4/42
It's not in your tree; but in tip/urgent.
David
>
> Linus
>
> ---
>
> WARNING: at arch/x86/kernel/cpu/perf_event_intel_ds.c:442
> intel_pmu_pebs_enable+0x89/0xa0()
> Hardware name: System Product Name
> Pid: 12994, comm: perf Not tainted 3.3.0-rc3-00001-g690d137f448d #34
> Call Trace:
> <IRQ> [<ffffffff8102f205>] warn_slowpath_common+0x75/0xb0
> [<ffffffff8105c1d4>] ? load_balance+0xc4/0x860
> [<ffffffff8102f305>] warn_slowpath_null+0x15/0x20
> [<ffffffff81013f59>] intel_pmu_pebs_enable+0x89/0xa0
> [<ffffffff81014614>] intel_pmu_enable_event+0xf4/0x190
> [<ffffffff81010f33>] x86_pmu_start+0x83/0x110
> [<ffffffff81098336>] perf_adjust_freq_unthr_context+0x106/0x170
> [<ffffffff810985a0>] perf_event_task_tick+0x200/0x2c0
> [<ffffffff8106a5d0>] ? tick_nohz_handler+0xf0/0xf0
> [<ffffffff81055856>] scheduler_tick+0xc6/0x100
> [<ffffffff8103b649>] update_process_times+0x69/0x80
> [<ffffffff8106a62f>] tick_sched_timer+0x5f/0xb0
> [<ffffffff8104dcd5>] __run_hrtimer.clone.31+0x55/0x110
> [<ffffffff8104e6ff>] hrtimer_interrupt+0xdf/0x210
> [<ffffffff8101c744>] smp_apic_timer_interrupt+0x64/0xa0
> [<ffffffff816a264b>] apic_timer_interrupt+0x6b/0x70
> <EOI> [<ffffffff8109d8df>] ? find_get_page+0x6f/0xc0
> [<ffffffff8128c114>] ? avtab_search_node+0x74/0x90
> [<ffffffff810a8b23>] ? mark_page_accessed+0x43/0x50
> [<ffffffff8129744d>] cond_compute_av+0x2d/0xd0
> [<ffffffff81293922>] context_struct_compute_av+0x1f2/0x420
> [<ffffffff8110834f>] ? __getblk+0x1f/0x280
> [<ffffffff81294265>] security_compute_av+0xf5/0x2c0
> [<ffffffff8127eeec>] avc_has_perm_noaudit+0xfc/0x3a0
> [<ffffffff811058ec>] ? ll_rw_block+0x2c/0xb0
> [<ffffffff8127f1d6>] avc_has_perm_flags+0x46/0xa0
> [<ffffffff81284801>] inode_has_perm.clone.39+0x21/0x30
> [<ffffffff8128525a>] selinux_inode_permission+0xaa/0x100
> [<ffffffff8127cc97>] security_inode_permission+0x17/0x20
> [<ffffffff810e4280>] inode_permission+0x40/0xd0
> [<ffffffff810e566f>] link_path_walk+0x6f/0x8f0
> [<ffffffff810e7807>] path_openat+0xb7/0x430
> [<ffffffff810e7bc4>] do_filp_open+0x44/0xa0
> [<ffffffff810b15ee>] ? kmemdup+0x3e/0x50
> [<ffffffff8128245a>] ? selinux_cred_prepare+0x1a/0x40
> [<ffffffff810df7dd>] open_exec+0x2d/0xf0
> [<ffffffff810e08d1>] do_execve_common.clone.36+0x1f1/0x430
> [<ffffffff810e0b26>] do_execve+0x16/0x20
> [<ffffffff8100aba5>] sys_execve+0x45/0x70
> [<ffffffff816a1fec>] stub_execve+0x6c/0xc0
> ---[ end trace 55816fcc72df1997 ]---
> ------------[ cut here ]------------
> WARNING: at arch/x86/kernel/cpu/perf_event_intel_lbr.c:75
> intel_pmu_lbr_enable+0x92/0xa0()
> Hardware name: System Product Name
> Pid: 12994, comm: perf Tainted: G W 3.3.0-rc3-00001-g690d137f448d #34
> Call Trace:
> <IRQ> [<ffffffff8102f205>] warn_slowpath_common+0x75/0xb0
> [<ffffffff8102f305>] warn_slowpath_null+0x15/0x20
> [<ffffffff81012e32>] intel_pmu_lbr_enable+0x92/0xa0
> [<ffffffff81013f38>] intel_pmu_pebs_enable+0x68/0xa0
> [<ffffffff81014614>] intel_pmu_enable_event+0xf4/0x190
> [<ffffffff81010f33>] x86_pmu_start+0x83/0x110
> [<ffffffff81098336>] perf_adjust_freq_unthr_context+0x106/0x170
> [<ffffffff810985a0>] perf_event_task_tick+0x200/0x2c0
> [<ffffffff8106a5d0>] ? tick_nohz_handler+0xf0/0xf0
> [<ffffffff81055856>] scheduler_tick+0xc6/0x100
> [<ffffffff8103b649>] update_process_times+0x69/0x80
> [<ffffffff8106a62f>] tick_sched_timer+0x5f/0xb0
> [<ffffffff8104dcd5>] __run_hrtimer.clone.31+0x55/0x110
> [<ffffffff8104e6ff>] hrtimer_interrupt+0xdf/0x210
> [<ffffffff8101c744>] smp_apic_timer_interrupt+0x64/0xa0
> [<ffffffff816a264b>] apic_timer_interrupt+0x6b/0x70
> <EOI> [<ffffffff8109d8df>] ? find_get_page+0x6f/0xc0
> [<ffffffff8128c114>] ? avtab_search_node+0x74/0x90
> [<ffffffff810a8b23>] ? mark_page_accessed+0x43/0x50
> [<ffffffff8129744d>] cond_compute_av+0x2d/0xd0
> [<ffffffff81293922>] context_struct_compute_av+0x1f2/0x420
> [<ffffffff8110834f>] ? __getblk+0x1f/0x280
> [<ffffffff81294265>] security_compute_av+0xf5/0x2c0
> [<ffffffff8127eeec>] avc_has_perm_noaudit+0xfc/0x3a0
> [<ffffffff811058ec>] ? ll_rw_block+0x2c/0xb0
> [<ffffffff8127f1d6>] avc_has_perm_flags+0x46/0xa0
> [<ffffffff81284801>] inode_has_perm.clone.39+0x21/0x30
> [<ffffffff8128525a>] selinux_inode_permission+0xaa/0x100
> [<ffffffff8127cc97>] security_inode_permission+0x17/0x20
> [<ffffffff810e4280>] inode_permission+0x40/0xd0
> [<ffffffff810e566f>] link_path_walk+0x6f/0x8f0
> [<ffffffff810e7807>] path_openat+0xb7/0x430
> [<ffffffff810e7bc4>] do_filp_open+0x44/0xa0
> [<ffffffff810b15ee>] ? kmemdup+0x3e/0x50
> [<ffffffff8128245a>] ? selinux_cred_prepare+0x1a/0x40
> [<ffffffff810df7dd>] open_exec+0x2d/0xf0
> [<ffffffff810e08d1>] do_execve_common.clone.36+0x1f1/0x430
> [<ffffffff810e0b26>] do_execve+0x16/0x20
> [<ffffffff8100aba5>] sys_execve+0x45/0x70
> [<ffffffff816a1fec>] stub_execve+0x6c/0xc0
> ---[ end trace 55816fcc72df1998 ]---
> --
> 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/
next prev parent reply other threads:[~2012-02-10 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 23:46 Hmm.. WARN_ON_ONCE(cpuc->enabled) Linus Torvalds
2012-02-10 0:13 ` David Ahern [this message]
2012-02-10 6:10 ` Ingo Molnar
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=4F346111.1040506@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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 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).