From: Scott Wood <scottwood@freescale.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Segher Boessenkool <segher@kernel.crashing.org>,
<linuxppc-dev@lists.ozlabs.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [BUG] Revert 0b05e2d671c4 'powerpc/32: cacheable_memcpy becomes memcpy'
Date: Mon, 21 Sep 2015 15:45:01 -0500 [thread overview]
Message-ID: <1442868301.19102.176.camel@freescale.com> (raw)
In-Reply-To: <1442819428.354.2.camel@ellerman.id.au>
On Mon, 2015-09-21 at 17:10 +1000, Michael Ellerman wrote:
> On Fri, 2015-09-18 at 16:45 +0200, Thomas Gleixner wrote:
> > On Fri, 18 Sep 2015, Segher Boessenkool wrote:
> >
> > > On Fri, Sep 18, 2015 at 08:01:57PM +1000, Michael Ellerman wrote:
> > > > Weird.
> > > >
> > > > Can you try:
> > > >
> > > > d690740f22f6 ("powerpc/powernv: Enable LEDS support")
> > > >
> > > > That is the commit before my merge of Scott's tree, which had all the
> > > > Freescale
> > > > & 32-bit stuff.
> > > >
> > > > If that works, it would isolate it to only about 30 commits from
> > > > Scott's tree.
> > >
> > > My theory is it is not a kernel problem at all; instead, uboot
> > > overwrites
> > > some little part of the kernel image.
> >
> > u-boot is just loading a cuImage which is a kernel with appended
> > device tree. So u-boot is out of the picture,
>
> Unless something is still DMA'ing after u-boot has handed over to the
> kernel.
> We had that happen on OF years ago.
>
> > still investigating (when time allows)
>
> Thanks. I assume no one at Freescale has been able to reproduce this?
I don't have an mpc52xx to test on. I can boot a p4080 with tracing enabled.
-Scott
next prev parent reply other threads:[~2015-09-21 20:45 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
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 [this message]
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=1442868301.19102.176.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rostedt@goodmis.org \
--cc=segher@kernel.crashing.org \
--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).