linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: rostedt@goodmis.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [FTRACE] Enabling function_graph causes OOPS
Date: Sun, 13 Sep 2009 14:37:30 +1000	[thread overview]
Message-ID: <1252816650.8375.70.camel@pasglop> (raw)
In-Reply-To: <1252814877.26049.93.camel@gandalf.stny.rr.com>

On Sun, 2009-09-13 at 00:07 -0400, Steven Rostedt wrote:
>                        982: R_PPC64_ADDR16_HIGHEST
> ftrace_return_to_handler
>  984:   60 84 00 00     ori     r4,r4,0
>                         986: R_PPC64_ADDR16_HIGHER
> ftrace_return_to_handler
>  988:   78 84 07 c6     rldicr  r4,r4,32,31
>  98c:   64 84 00 00     oris    r4,r4,0
>                         98e: R_PPC64_ADDR16_HI
> ftrace_return_to_handler
>  990:   60 84 00 00     ori     r4,r4,0
>                         992: R_PPC64_ADDR16_LO
> ftrace_return_to_handler
>  994:   e8 44 00 08     ld      r2,8(r4)
>  998:   48 00 00 01     bl      998 <.mod_return_to_handler+0x30>
>                         998:
> R_PPC64_REL24      .ftrace_return_to_handler
>  99c:   60 00 00 00     nop
>  9a0:   7c 68 03 a6     mtlr    r3

.../...

> Something is totally messed up here.

Could it be that we don't handle R_PPC64_ADDR16_* relocs in
arch/powerpc/kernel/modules/module_64.c ?

Sachin, do you see a bunch of "Unknown ADD relocation" in your dmesg ?

Ben.

  reply	other threads:[~2009-09-13  4:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 10:26 [FTRACE] Enabling function_graph causes OOPS Sachin Sant
2009-07-14 22:45 ` Steven Rostedt
2009-08-03 10:40   ` Sachin Sant
2009-09-09  1:05     ` Steven Rostedt
2009-09-09  6:27       ` Sachin Sant
2009-09-09 19:42         ` Steven Rostedt
2009-09-10  5:32           ` Sachin Sant
2009-09-11  3:05             ` Steven Rostedt
2009-09-11  4:26               ` Sachin Sant
2009-09-11 18:05             ` Steven Rostedt
2009-09-13  4:07         ` Steven Rostedt
2009-09-13  4:37           ` Benjamin Herrenschmidt [this message]
2009-09-13 13:21             ` Steven Rostedt
2009-09-13 20:25               ` Benjamin Herrenschmidt
2009-09-14  8:00                 ` Benjamin Herrenschmidt
2009-10-05 13:25                   ` Steven Rostedt
2009-10-05 20:20                     ` Benjamin Herrenschmidt
2009-10-05 20:37                       ` Steven Rostedt
2009-10-07  8:56                         ` Sachin Sant
2009-10-07  9:10                           ` Benjamin Herrenschmidt
2009-10-08 14:51                             ` [PATCH] Ftrace : fix function_graph tracer OOPS Sachin Sant
2009-10-14  3:01                               ` Steven Rostedt
2009-10-14  6:13                                 ` Sachin Sant
2009-10-14  6:15                                   ` Benjamin Herrenschmidt
2009-10-14 12:12                                     ` Steven Rostedt

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=1252816650.8375.70.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rostedt@goodmis.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).