linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Steve Capper <steve.capper@linaro.org>,
	David Long <dave.long@linaro.org>
Cc: "Jon Medhurst (Tixy)" <tixy@linaro.org>,
	Russell King <linux@arm.linux.org.uk>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Sandeepa Prabhu <sandeepa.prabhu@linaro.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
	David Miller <davem@davemloft.net>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 0/5] ARM64: Add kernel probes(Kprobes) support
Date: Tue, 02 Dec 2014 15:00:51 -0500	[thread overview]
Message-ID: <547E1A73.6000805@redhat.com> (raw)
In-Reply-To: <547E129C.1090308@redhat.com>

On 12/02/2014 02:27 PM, William Cohen wrote:

> Hi Masami and Dave,
> 
> I have applied the suggested patch above to my local kernel. However, I have noticed systemtap testsuite consistently getting panics when running both before AND after applying that patch to the kernel.  Any thoughts on why "perf stat" would cause that? Below is an example output
> 
> -Will

This problem doesn't look like it is related to the kprobes support.  It can be triggered without running kprobes related code such as a "perf stat make" on a user-space build. It's failure looks similar to:

http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/265814.html

-Will
> 
> # perf stat make install
> 
> ...
> 
> Running ./systemtap/notest.exp ...
> Running ./systemtap.apps/java.exp ...
> [ 6734.986063] Bad mode in FIQ handler detected, code 0x56000000
> [ 6734.991788] CPU: 0 PID: 3968 Comm: stap Tainted: G            E  3.18.0-rc5kp3+ #3
> [ 6734.999317] Hardware name: APM X-Gene Mustang board (DT)
> [ 6735.004602] task: fffffe0016c25a00 ti: fffffe03d8aa8000 task.ti: fffffe03d8aa8000
> [ 6735.012052] PC is at 0x3ff7fc0d1fc
> [ 6735.015434] LR is at 0x3ff7fc31838
> [ 6735.018815] pc : [<000003ff7fc0d1fc>] lr : [<000003ff7fc31838>] pstate: 00000000
> [ 6735.026172] sp : fffffe03d8aabff0
> [ 6735.029467] x29: 000003fffe4f6460 x28: 000003ff7fb23640 
> [ 6735.034772] x27: 000003ff7fb23578 x26: 000000000059a420 
> [ 6735.040074] x25: 000000000000005f x24: 000003ff7fb3f000 
> [ 6735.045375] x23: 000000004178ee40 x22: 0000000000000006 
> [ 6735.050680] x21: 0000000000000001 x20: 0000000000008000 
> [ 6735.055980] x19: 000000004178ee40 x18: 000003fffe4f64a0 
> [ 6735.061282] x17: 000003ff7fc0d1fc x16: 000003ff7fd00008 
> [ 6735.066585] x15: 00000013cd9f3df0 x14: 0000000051c4a1f8 
> [ 6735.071886] x13: 0000000001519f64 x12: 000000000000000e 
> [ 6735.077187] x11: 646f6d2f62696c2f x10: 6174732f706d742f 
> [ 6735.082488] x9 : 312e332f73656c75 x8 : 0000000000000038 
> [ 6735.087790] x7 : 5f34366372617073 x6 : 000000000000007c 
> [ 6735.093094] x5 : 0000000000000000 x4 : 0000000000000001 
> [ 6735.098397] x3 : 0000000000000000 x2 : 0000000000000000 
> [ 6735.103697] x1 : 0000000000000001 x0 : 0000000000008030 
> [ 6735.108999] 
> [ 6735.110483] Bad mode in Synchronous Abort handler detected, code 0x8600000f
> [ 6735.117408] CPU: 0 PID: 3968 Comm: stap Tainted: G            E  3.18.0-rc5kp3+ #3
> [ 6735.124936] Hardware name: APM X-Gene Mustang board (DT)
> [ 6735.130220] task: fffffe0016c25a00 ti: fffffe03d8aa8000 task.ti: fffffe03d8aa8000
> [ 6735.137662] PC is at 0x3ff7fc31838
> [ 6735.141044] LR is at 0x3ff7fc31838
> [ 6735.144426] pc : [<000003ff7fc31838>] lr : [<000003ff7fc31838>] pstate: 600003c5
> [ 6735.151782] sp : fffffe03d8aabed0
> [ 6735.155077] x29: 000003fffe4f6460 x28: 000003ff7fb23640 
> [ 6735.160380] x27: 000003ff7fb23578 x26: 000000000059a420 
> [ 6735.165681] x25: 000000000000005f x24: 000003ff7fb3f000 
> [ 6735.170983] x23: 0000000000000000 x22: 000003ff7fc0d1fc 
> [ 6735.176285] x21: fffffe03d8aabff0 x20: 0000000000008000 
> [ 6735.181587] x19: 000000004178ee40 x18: 000003fffe4f64a0 
> [ 6735.186888] x17: 000003ff7fc0d1fc x16: 000003ff7fd00008 
> [ 6735.192189] x15: 00000013cd9f3df0 x14: 30303030203a6574 
> [ 6735.197490] x13: fffffe00008eda38 x12: cb88537fdc8cb000 
> [ 6735.202792] x11: fffffe03d8aabb70 x10: fffffe03d8aabb70 
> [ 6735.208094] x9 : 000000000000015f x8 : 0000000000000000 
> [ 6735.213395] x7 : 0000000000000200 x6 : fffffe0000095cd4 
> [ 6735.218698] x5 : fffffe0300030001 x4 : 0000000000000000 
> [ 6735.224001] x3 : fffffe03d8aabc80 x2 : 000000000000027e 
> [ 6735.229304] x1 : cb88537fdc8cb000 x0 : cb88537fdc8cb000 

<snip>


  reply	other threads:[~2014-12-02 20:01 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18  6:32 [PATCH v3 0/5] ARM64: Add kernel probes(Kprobes) support David Long
2014-11-18  6:32 ` [PATCH v3 1/5] arm64: Kprobes with single stepping support David Long
2014-11-18 13:28   ` Jon Medhurst (Tixy)
2014-11-21  4:28     ` David Long
2014-11-18 14:38   ` William Cohen
2014-11-18 14:39   ` William Cohen
2014-11-18 14:56   ` Will Deacon
2014-11-19 11:21     ` Sandeepa Prabhu
2014-11-19 11:25       ` Will Deacon
2014-11-19 14:55         ` David Long
2014-11-20  5:10           ` Sandeepa Prabhu
2014-11-26  6:46           ` David Long
2014-11-26 10:09             ` Will Deacon
2014-12-22 10:10   ` Pratyush Anand
2014-11-18  6:32 ` [PATCH v3 2/5] arm64: Kprobes instruction simulation support David Long
2014-11-18 14:43   ` William Cohen
2014-11-18  6:32 ` [PATCH v3 3/5] arm64: Add kernel return probes support(kretprobes) David Long
2014-11-18 14:50   ` William Cohen
2014-11-18  6:32 ` [PATCH v3 4/5] kprobes: Add arm64 case in kprobe example module David Long
2014-11-18  6:32 ` [PATCH v3 5/5] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature David Long
2014-11-18 14:52   ` Will Deacon
2014-11-20  7:20     ` Masami Hiramatsu
2014-11-21  6:16     ` David Long
2014-11-20 15:02 ` [PATCH v3 0/5] ARM64: Add kernel probes(Kprobes) support Steve Capper
2014-11-26  8:33   ` Masami Hiramatsu
2014-11-26 10:03     ` Steve Capper
2014-11-26 17:46       ` David Long
2014-11-26 18:59         ` Steve Capper
2014-11-27  6:07           ` Masami Hiramatsu
2014-11-28 16:01             ` Steve Capper
2014-12-01  9:37               ` Masami Hiramatsu
2014-12-02 19:27                 ` William Cohen
2014-12-02 20:00                   ` William Cohen [this message]
2014-12-03  3:36                   ` Masami Hiramatsu
2014-12-03 14:54                 ` William Cohen
2014-12-03 22:54                   ` David Long
2014-12-04  0:02                     ` David Long
2014-12-04  1:16                     ` William Cohen
2014-12-04  2:48                       ` David Long
2014-12-04 10:21                         ` Steve Capper
2014-12-04 10:43                           ` Masami Hiramatsu
2014-12-04 11:29                             ` Steve Capper
2014-12-04 11:53                               ` Masami Hiramatsu
2014-12-09 13:33                                 ` Steve Capper
2014-12-09 14:27                                   ` David Long
2014-12-10 16:38                                     ` Steve Capper
2014-12-12 22:42                                       ` David Long
2014-12-12 23:10                                         ` Steve Capper
2014-12-15  5:58                                           ` Masami Hiramatsu
2014-12-15  6:29                                           ` David Long
2014-12-05  5:08                       ` William Cohen
2014-11-27  5:13       ` Masami Hiramatsu

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=547E1A73.6000805@redhat.com \
    --to=wcohen@redhat.com \
    --cc=ananth@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=catalin.marinas@arm.com \
    --cc=dave.long@linaro.org \
    --cc=davem@davemloft.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=sandeepa.prabhu@linaro.org \
    --cc=steve.capper@linaro.org \
    --cc=tixy@linaro.org \
    --cc=will.deacon@arm.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 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).