From: Segher Boessenkool <segher@kernel.crashing.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Scott Wood <scottwood@freescale.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [BUG] Revert 0b05e2d671c4 'powerpc/32: cacheable_memcpy becomes memcpy'
Date: Thu, 17 Sep 2015 10:38:10 -0500 [thread overview]
Message-ID: <20150917153806.GC2613@gate.crashing.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1509171630130.3951@nanos>
On Thu, Sep 17, 2015 at 04:38:52PM +0200, Thomas Gleixner wrote:
> [ 2.398263] Instruction dump:
> [ 2.401297] 01000000 00037000 00000000 00000000 f0000000 00000001 0a641e09 acde4823
> [ 2.409237] 000f0000 179a7b00 07de2900 03ef1480 <01f78a40> 0001c200 60000000 9421fff0
Those are not instructions (until the nop).
Starting three back from the failing instruction, those are
396000000 132000000 66000000 <33000000> 115200
so something has been scribbling what looks like clock frequencies
over your code. Judging from the register contents this has happened
some time before.
Some device trees have similar numbers, e.g. media5200.dts does.
Segher
next prev parent reply other threads:[~2015-09-17 19:11 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
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 [this message]
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=20150917153806.GC2613@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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 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).