linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: David Ahern <dsahern@gmail.com>,
	Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] perf test 29 crashing
Date: Thu, 30 Jun 2016 17:10:16 +0200	[thread overview]
Message-ID: <20160630151016.GA4828@krava> (raw)
In-Reply-To: <20160629022006.GC1628@sejong>

On Wed, Jun 29, 2016 at 11:20:06AM +0900, Namhyung Kim wrote:

SNIP

> > 
> > If this helps break the tie:
> > 
> > dsa@kenny:~/kernel.git$ /tmp/perf/perf test 29
> > 29: Test cumulation of child hist entries                    : Ok
> > 
> > dsa@kenny:~/kernel.git$ /tmp/perf/perf --version
> > perf version 4.7.rc5.g02184c
> > 
> > But running on net-next kernel from a few days ago + 1 local patch:
> > dsa@kenny:~/kernel.git$ uname -r
> > 4.7.0-rc2-00862-g23854048c919
> > 
> > (I do get a few other failures)
> 
> Running latest acme/perf/core:
> 
>   $ perf test hist
>   15: Test matching and linking multiple hists                 : Ok
>   25: Test filtering hist entries                              : Ok
>   28: Test output sorting of hist entries                      : Ok
>   29: Test cumulation of child hist entries                    : Ok
>   $ perf --version
>   perf version 4.6.g6d9c67
> 

hum.. I still see it:
(latest acme's perf/core)

[jolsa@krava perf]$ ./perf --version
perf version 4.7.rc5.ga059d59
[jolsa@krava perf]$ ./perf test hist
15: Test matching and linking multiple hists                 : Ok
25: Test filtering hist entries                              : Ok
28: Test output sorting of hist entries                      : Ok
29: Test cumulation of child hist entries                    : FAILED!

[jolsa@krava perf]$ ./perf test 29 -v
29: Test cumulation of child hist entries                    :
--- start ---
test child forked, pid 11925
perf: Segmentation fault
Obtained 11 stack frames.
./perf(sighandler_dump_stack+0x41) [0x4f57f1]
/lib64/libc.so.6(+0x34a50) [0x7f5e22695a50]
./perf() [0x47b2cc]
./perf(test__hists_cumulate+0x10c) [0x47c79c]
./perf() [0x4698b6]
./perf(cmd_test+0x5be) [0x469eae]
./perf() [0x487561]
./perf(main+0x6f6) [0x424cb6]
/lib64/libc.so.6(__libc_start_main+0xf0) [0x7f5e22681700]
./perf(_start+0x29) [0x424da9]
[(nil)]
test child interrupted
---- end ----
Test cumulation of child hist entries: FAILED!


hate to be the only one with this.. now I need to dive in ;-)

jirka

  reply	other threads:[~2016-06-30 15:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 12:34 [BUG] perf test 29 crashing Jiri Olsa
2016-06-28 16:59 ` Arnaldo Carvalho de Melo
2016-06-28 17:52   ` David Ahern
2016-06-29  2:20     ` Namhyung Kim
2016-06-30 15:10       ` Jiri Olsa [this message]
2016-06-30 16:18         ` Jiri Olsa
2016-06-30 19:41           ` David Ahern
2016-07-01  7:02             ` Jiri Olsa
2016-06-30 19:56           ` 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=20160630151016.GA4828@krava \
    --to=jolsa@redhat.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@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).