All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Felipe Balbi <balbi@ti.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	Tony Lindgren <tony@atomide.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux ARM Kernel Mailing List 
	<linux-arm-kernel@lists.infradead.org>,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: perf not capturing stack traces
Date: Fri, 23 Jan 2015 17:59:59 -0300	[thread overview]
Message-ID: <20150123205959.GD3073@kernel.org> (raw)
In-Reply-To: <20150123195128.GE26557@saruman.tx.rr.com>

Em Fri, Jan 23, 2015 at 01:51:28PM -0600, Felipe Balbi escreveu:
> I'm using v3.19-rc5 on an ARM Cortex A9 board. Unfortunately, perf is
> not able to capture any stack traces even though I CONFIG_STACKTRACE,
> CONFIG_FRAME_POINTER and CONFIG_ARM_UNWIND all enabled.
> 
> I wonder if anybody else is facing similar issues.

Did it work with a previous kernel?

- Arnaldo

WARNING: multiple messages have this Message-ID (diff)
From: acme@kernel.org (Arnaldo Carvalho de Melo)
To: linux-arm-kernel@lists.infradead.org
Subject: perf not capturing stack traces
Date: Fri, 23 Jan 2015 17:59:59 -0300	[thread overview]
Message-ID: <20150123205959.GD3073@kernel.org> (raw)
In-Reply-To: <20150123195128.GE26557@saruman.tx.rr.com>

Em Fri, Jan 23, 2015 at 01:51:28PM -0600, Felipe Balbi escreveu:
> I'm using v3.19-rc5 on an ARM Cortex A9 board. Unfortunately, perf is
> not able to capture any stack traces even though I CONFIG_STACKTRACE,
> CONFIG_FRAME_POINTER and CONFIG_ARM_UNWIND all enabled.
> 
> I wonder if anybody else is facing similar issues.

Did it work with a previous kernel?

- Arnaldo

  parent reply	other threads:[~2015-01-23 21:00 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 19:51 perf not capturing stack traces Felipe Balbi
2015-01-23 19:51 ` Felipe Balbi
2015-01-23 19:51 ` Felipe Balbi
2015-01-23 19:53 ` Felipe Balbi
2015-01-23 19:53   ` Felipe Balbi
2015-01-23 19:53   ` Felipe Balbi
2015-01-23 20:59 ` Arnaldo Carvalho de Melo [this message]
2015-01-23 20:59   ` Arnaldo Carvalho de Melo
2015-01-23 20:59   ` Arnaldo Carvalho de Melo
2015-01-23 22:37   ` Felipe Balbi
2015-01-23 22:37     ` Felipe Balbi
2015-01-23 22:37     ` Felipe Balbi
2015-01-24 15:12     ` Arnaldo Carvalho de Melo
2015-01-24 15:12       ` Arnaldo Carvalho de Melo
2015-01-24 15:12       ` Arnaldo Carvalho de Melo
2015-01-24 22:23       ` Felipe Balbi
2015-01-24 22:23         ` Felipe Balbi
2015-01-24 22:23         ` Felipe Balbi
2015-01-25 15:56         ` Russell King - ARM Linux
2015-01-25 15:56           ` Russell King - ARM Linux
2015-01-25 15:56           ` Russell King - ARM Linux
2015-01-26 10:27           ` Will Deacon
2015-01-26 10:27             ` Will Deacon
2015-01-26 10:27             ` Will Deacon
2015-01-26 12:12             ` Arnaldo Carvalho de Melo
2015-01-26 12:12               ` Arnaldo Carvalho de Melo
2015-01-26 12:12               ` Arnaldo Carvalho de Melo
2015-01-26 12:16               ` Will Deacon
2015-01-26 12:16                 ` Will Deacon
2015-01-26 12:16                 ` Will Deacon
2015-01-26 12:29                 ` Arnaldo Carvalho de Melo
2015-01-26 12:29                   ` Arnaldo Carvalho de Melo
2015-01-26 12:29                   ` Arnaldo Carvalho de Melo
2015-01-26 13:54               ` Russell King - ARM Linux
2015-01-26 13:54                 ` Russell King - ARM Linux
2015-01-26 13:54                 ` Russell King - ARM Linux
2015-01-26 14:33                 ` Arnaldo Carvalho de Melo
2015-01-26 14:33                   ` Arnaldo Carvalho de Melo
2015-01-26 14:33                   ` Arnaldo Carvalho de Melo
2015-01-26 13:51             ` Russell King - ARM Linux
2015-01-26 13:51               ` Russell King - ARM Linux
2015-01-26 13:51               ` Russell King - ARM Linux
2015-01-26 14:37               ` Arnaldo Carvalho de Melo
2015-01-26 14:37                 ` Arnaldo Carvalho de Melo
2015-01-26 14:37                 ` 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=20150123205959.GD3073@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=tony@atomide.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.