From: Scott Wood <scottwood@freescale.com>
To: James Black <jblack547@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: muram in device tree for mpc8250 in arch/powerpc
Date: Fri, 21 Mar 2008 15:34:47 -0500 [thread overview]
Message-ID: <47E41BE7.9020109@freescale.com> (raw)
In-Reply-To: <b77025b40803211314g74a41aa9of01f7cf3560a2505@mail.gmail.com>
James Black wrote:
> I've compiled the kernel with gcc 4.0.0 and 4.2.2 both versions have
> the same problem. Should I try the 2.6.25 kernel since the 2.6.19
> works just fine.
It's worth a try. Also, since it seems to be a random corruption issue,
make sure that no DMA is left running by the firmware (try resetting the
CPM (though you'll have to turn off the early udbg output)), that you're
not trying to use more memory than you have, etc. Try dumping various
registers to see if anything significant is different compared to 2.6.19.
If none of that helps, then I'm out of ideas as far as debug-by-email
goes...
> I've stripped the kernel options down almost as far
> as I can go.
You turned off too much. :-)
Turn kallsyms back on, so you get symbols in crash dumps.
-Scott
next prev parent reply other threads:[~2008-03-21 20:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 17:06 muram in device tree for mpc8250 in arch/powerpc James Black
2008-03-19 17:40 ` Scott Wood
[not found] ` <b77025b40803191107x2f9a7884n9b7f062fcf45370@mail.gmail.com>
2008-03-20 18:02 ` James Black
2008-03-20 18:20 ` Scott Wood
2008-03-20 23:02 ` James Black
2008-03-21 16:18 ` Scott Wood
2008-03-21 20:14 ` James Black
2008-03-21 20:34 ` Scott Wood [this message]
2008-03-21 21:35 ` James Black
2008-03-24 16:52 ` Scott Wood
2008-03-24 21:45 ` James Black
2008-03-24 21:53 ` Scott Wood
2008-03-24 21:59 ` James Black
2008-03-24 22:05 ` Scott Wood
2008-03-24 22:09 ` James Black
2008-03-24 22:28 ` James Black
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=47E41BE7.9020109@freescale.com \
--to=scottwood@freescale.com \
--cc=jblack547@gmail.com \
--cc=linuxppc-embedded@ozlabs.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).