From: Jiri Olsa <jolsa@redhat.com>
To: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, namhyung@kernel.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: found 2 tests failed using "perf test" command
Date: Tue, 22 May 2018 15:47:57 +0200 [thread overview]
Message-ID: <20180522134757.GA10727@krava> (raw)
In-Reply-To: <CAG=yYwnNYY6YKD8wtnjQD-87N7ipSCnyXr8dzFGm4brE6-cgNw@mail.gmail.com>
On Sun, May 20, 2018 at 01:53:15AM +0530, Jeffrin Thalakkottoor wrote:
> hello,
>
>
> i found two tests failed while i did "sudo ./perf test"
>
> --------------------------------------------------------------------------->
> 24: Object code reading : FAILED!
> 64: probe libc's inet_pton & backtrace it with ping : FAILED!
> ---------------------------------------------------------------------------->
>
> some relevent shell session details from ./sudo perf test -vv 24
> -------------------------------------------------------------------------------------------------------->
> Objdump command is: objdump -z -d --start-address=0xffffffff8132dda7
> --stop-address=0xffffffff8132de27
> /lib/modules/4.17.0-rc5+/build/vmlinux
> Bytes read match those read by objdump
> Reading object code for memory address: 0xfffffe000005e01e
> thread__find_addr_map failed
> test child finished with -1
> ---- end ----
> Object code reading: FAILED!
> ---------------------------------------------------------------------------------------------------------->
>
> $sudo ./perf test -vv 64
> 64: probe libc's inet_pton & backtrace it with ping :
> --- start ---
> test child forked, pid 4751
> test child finished with -1
> ---- end ----
> probe libc's inet_pton & backtrace it with ping: FAILED!
there's been some recent discussion/changes in here, please follow:
https://marc.info/?t=152662842600002&r=1&w=2
jirka
prev parent reply other threads:[~2018-05-22 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 20:23 PROBLEM: found 2 tests failed using "perf test" command Jeffrin Thalakkottoor
2018-05-22 13:47 ` Jiri Olsa [this message]
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=20180522134757.GA10727@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jeffrin@rajagiritech.edu.in \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@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