From: Matt Porter <mporter@kernel.crashing.org>
To: Travis Sawyer <tsawyer+linuxppc@sandburst.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 440GX tlb problem?
Date: Fri, 11 Jun 2004 14:24:37 -0700 [thread overview]
Message-ID: <20040611142437.A1795@home.com> (raw)
In-Reply-To: <1086979205.29360.5.camel@pavement.sandburst.com>; from tsawyer+linuxppc@sandburst.com on Fri, Jun 11, 2004 at 02:40:05PM -0400
On Fri, Jun 11, 2004 at 02:40:05PM -0400, Travis Sawyer wrote:
>
> Greetings:
>
> I'm attempting to bring up a new board (our custom hw) and am blowing an
> Instruction TLB error in head_440.S where the original TLB for SDRAM
head_440.S indicates you are using a really old kernel.
> (u-boot and initial kernel space) is invalidated after we've switched to
> 0xc000_0000.
What do you mean? Your u-boot port has invalidated caches? are you
running out of 0xc0000000 before you get here? Which TLB entry are
you executing from?
> the instructions:
> 3:/* iccci r0,r0 rcblach 12/19/02 clear all caches again on 1/17/03
> I took out these changes
> dccci r0,r0 again clear all caches */
> cmpwi r23,62
> beq 4f
> li r6,0
> tlbwe r6,r23,PPC440_TLB_PAGEID
> sync
By the comments, it's an IBM supplied kernel. This isn't anything
in the kernel.org or linuxppc kernel trees.
> The exception hits when the sync is executed.
Maybe you are executing from TLB entry 62, that's one of the
undocumented limitations...you can entry head_44x.S running in
entry 62.
> Any ideas?
Can you try a current kernel tree? kernel.org 2.4 or 2.6. The IBM
kernel trees are old and buggy (_buggier_).
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-11 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 18:40 440GX tlb problem? Travis Sawyer
2004-06-11 21:24 ` Matt Porter [this message]
2004-06-14 2:12 ` LarrZheng
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=20040611142437.A1795@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tsawyer+linuxppc@sandburst.com \
/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).