From: David Ahern <dsahern@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Perf events warning..
Date: Tue, 15 May 2012 09:37:37 -0600 [thread overview]
Message-ID: <4FB27841.9040301@gmail.com> (raw)
In-Reply-To: <1337095700.27694.76.camel@twins>
On 5/15/12 9:28 AM, Peter Zijlstra wrote:
> On Tue, 2012-05-15 at 09:25 -0600, David Ahern wrote:
>>
>> Perhaps it is specific to processor generation?
>
> Your error is distinctly different from Linus' in that it came from
> within the arch code, Linus' was core code.
>
> Furthermore the error you send had:
>
> [ 31.528799] Hardware name: Bochs
>
> Which is some virt crap.. so I wouldn't trust the 'hardware' anyway.
:-) Right, KVM and the vPMU added in 3.3. That said, it is recognized as
a Nehalem and perf walks the Nehalem events path.
So if VM based WARNING is not to your liking, here's a baremetal version:
[ 84.388495] ------------[ cut here ]------------
[ 84.388554] WARNING: at
/opt/sw/ahern/kernels/kernel-2.6.git/arch/x86/kernel/cpu/perf_event.c:1054
x86_pmu_start+0xdc/0x110()
[ 84.388613] Hardware name: ProLiant DL380 G6
[ 84.388663] Modules linked in: nfs fscache bridge stp llc
ipt_MASQUERADE iptable_nat nf_nat xt_physdev nf_conntrack_ipv4
nf_defrag_ipv4 xt_state nf_conntrack xt_multiport nfsd lockd nfs_acl
auth_rpcgss sunrpc coretemp ipmi_si ipmi_msghandler bnx2 i7core_edac
edac_core hpilo hpwdt acpi_power_meter crc32c_intel microcode iTCO_wdt
iTCO_vendor_support vhost_net pcspkr macvtap macvlan tun virtio_net
kvm_intel kvm usb_storage hpsa radeon ttm drm_kms_helper drm
i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
[ 84.390624] Pid: 1806, comm: find Not tainted 3.4.0-rc7+ #1
[ 84.390671] Call Trace:
[ 84.390719] [<ffffffff810579df>] warn_slowpath_common+0x7f/0xc0
[ 84.390769] [<ffffffff81057a3a>] warn_slowpath_null+0x1a/0x20
[ 84.390831] [<ffffffff8102546c>] x86_pmu_start+0xdc/0x110
[ 84.390880] [<ffffffff81025b22>] x86_pmu_enable+0x212/0x270
[ 84.390996] [<ffffffff81116496>] perf_event_context_sched_in+0xe6/0x100
[ 84.391113] [<ffffffff811180b3>] perf_event_comm+0x103/0x2b0
[ 84.391232] [<ffffffff81186732>] set_task_comm+0x72/0xe0
[ 84.391361] [<ffffffff81186e0b>] setup_new_exec+0x8b/0x240
[ 84.391480] [<ffffffff811ceca7>] load_elf_binary+0x3e7/0x19a0
[ 84.391600] [<ffffffff81145ac2>] ? get_user_pages+0x52/0x60
[ 84.391716] [<ffffffff81184af8>] ? get_user_arg_ptr+0x38/0x80
[ 84.391833] [<ffffffff81184f9e>] search_binary_handler+0xee/0x340
[ 84.391963] [<ffffffff811ce8c0>] ? load_elf_library+0x230/0x230
[ 84.392080] [<ffffffff81186bef>] do_execve_common+0x36f/0x410
[ 84.392196] [<ffffffff81186cca>] do_execve+0x3a/0x40
[ 84.392328] [<ffffffff8101d4a7>] sys_execve+0x47/0x70
[ 84.392445] [<ffffffff816002ec>] stub_execve+0x6c/0xc0
[ 84.392558] ---[ end trace 78e50a201158fd5d ]---
Though this one is an HP server with the lovely:
[ 0.143910] Performance Events: PEBS fmt1+, 16-deep LBR, Nehalem
events, Broken BIOS detected, complain to your hardware vendor.
[ 0.144351] [Firmware Bug]: the BIOS has corrupted hw-PMU resources
(MSR 38d is 330)
[ 0.144627] Intel PMU driver.
[ 0.144777] CPU erratum AAJ80 worked around
David
next prev parent reply other threads:[~2012-05-15 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 15:43 Perf events warning Linus Torvalds
2012-05-14 22:20 ` Peter Zijlstra
2012-05-14 22:25 ` David Ahern
2012-05-14 22:25 ` Linus Torvalds
2012-05-15 10:49 ` Peter Zijlstra
2012-05-15 15:25 ` David Ahern
2012-05-15 15:28 ` Peter Zijlstra
2012-05-15 15:37 ` David Ahern [this message]
2012-05-16 1:38 ` Namhyung Kim
2012-05-21 6:06 ` Namhyung Kim
2012-05-15 15:46 ` Arnaldo Carvalho de Melo
2012-05-15 15:48 ` Linus Torvalds
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=4FB27841.9040301@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=torvalds@linux-foundation.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