From: rabin@rab.in (Rabin Vincent)
To: linux-arm-kernel@lists.infradead.org
Subject: 'perf test' failed on ARM
Date: Tue, 23 Nov 2010 22:08:18 +0530 [thread overview]
Message-ID: <20101123163106.GA25677@debian> (raw)
In-Reply-To: <AANLkTik4QDCD0rAZ=04Ph23ApZ822BBoOWEiPEp7GBNr@mail.gmail.com>
On Tue, Nov 23, 2010 at 04:07:39PM +0800, Ming Lei wrote:
> 'perf test' is failed on linux 2.6.37-rc2/rc3, follows log info:
>
> root at beagleboard:/mnt/omap/linux-2.6-omap/tools/perf# ./perf test -v 3
> 1: vmlinux symtab matches kallsyms:
> --- start ---
> dso__find_symbol_by_name ---- end ----
> vmlinux symtab matches kallsyms: FAILED!
>
> Any suggestions?
There seems to be a problem with the symbol handling code. Patch below.
With this patch the command executes further, but the test fails because
of other reasons:
1: vmlinux symtab matches kallsyms:
--- start ---
map_groups__set_modules_path_dir: cannot open /lib/modules/2.6.37-rc3-next-20101122+/kernel dir
Problems creating module maps, continuing anyway...
map_groups__set_modules_path_dir: cannot open /lib/modules/2.6.37-rc3-next-20101122+/kernel dir
Problems creating module maps, continuing anyway...
Looking at the vmlinux_path (6 entries long)
Using vmlinux for symbols
0xc011ab68: diff end addr for __kprobes_text_start v: 0xc012b87f k: 0xc011b353
0xc012b880: kallsyms_addresses not on kallsyms
0xc0138c90: kallsyms_num_syms not on kallsyms
0xc0138ca0: kallsyms_names not on kallsyms
0xc015c010: kallsyms_markers not on kallsyms
0xc015c0f0: kallsyms_token_table not on kallsyms
0xc015c490: kallsyms_token_index not on kallsyms
Maps only in vmlinux:
c0014c5c-ffffffff 0 [kernel].init
Maps in vmlinux with a different name in kallsyms:
Maps only in kallsyms:
---- end ----
vmlinux symtab matches kallsyms: FAILED!
next prev parent reply other threads:[~2010-11-23 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 8:07 'perf test' failed on ARM Ming Lei
2010-11-23 16:38 ` Rabin Vincent [this message]
2010-11-23 18:17 ` Arnaldo Carvalho de Melo
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=20101123163106.GA25677@debian \
--to=rabin@rab.in \
--cc=linux-arm-kernel@lists.infradead.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).