From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Scott Wood <scottwood@freescale.com>,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [BUG] Revert 0b05e2d671c4 'powerpc/32: cacheable_memcpy becomes memcpy'
Date: Wed, 16 Sep 2015 22:18:54 -0500 [thread overview]
Message-ID: <20150917031854.GA31437@gate.crashing.org> (raw)
In-Reply-To: <1442458212.8456.2.camel@ellerman.id.au>
On Thu, Sep 17, 2015 at 12:50:12PM +1000, Michael Ellerman wrote:
> On Wed, 2015-09-16 at 21:54 -0400, Steven Rostedt wrote:
> > This could be a symptom and not the problem. What the above shows is
> > that ftrace tried to convert the mcount at change_protection but what
> > it expected was there wasn't. Unfortunately, it doesn't state exactly
> > what it wants (that would take a arch specific function to do that, and
> > this is in generic code). But what it found was "74 66 74 70", which I
> > have no idea what type of command that is.
>
> This is big endian, so I think that's:
>
> andis. r6,r3,29808
>
> Which is feasible.
It also says "tftp", which is intriguing if nothing else :-)
Segher
next prev parent reply other threads:[~2015-09-17 3:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 16:23 [BUG] Revert 0b05e2d671c4 'powerpc/32: cacheable_memcpy becomes memcpy' Thomas Gleixner
2015-09-16 16:29 ` Scott Wood
2015-09-16 20:01 ` Thomas Gleixner
2015-09-17 1:54 ` Steven Rostedt
2015-09-17 2:50 ` Michael Ellerman
2015-09-17 3:18 ` Segher Boessenkool [this message]
2015-09-17 9:47 ` David Laight
2015-09-17 14:01 ` Segher Boessenkool
2015-09-17 10:13 ` Thomas Gleixner
2015-09-17 13:29 ` Steven Rostedt
2015-09-17 14:38 ` Thomas Gleixner
2015-09-17 14:52 ` Steven Rostedt
2015-09-17 15:22 ` Thomas Gleixner
2015-09-17 15:38 ` Segher Boessenkool
2015-09-18 10:01 ` Michael Ellerman
2015-09-18 14:32 ` Segher Boessenkool
2015-09-18 14:45 ` Thomas Gleixner
2015-09-21 7:10 ` Michael Ellerman
2015-09-21 20:45 ` Scott Wood
2015-09-17 0:38 ` Michael Ellerman
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=20150917031854.GA31437@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rostedt@goodmis.org \
--cc=scottwood@freescale.com \
--cc=tglx@linutronix.de \
/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.