linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Boerner, Brian" <bmb@pirus.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: MMU: address translation for 0x00001100 failed
Date: Mon, 24 Sep 2001 15:11:12 -0400	[thread overview]
Message-ID: <200109241907.OAA30214@lists.linuxppc.org> (raw)


I get the above message when attempting to step through the
time_init function on a walnut using the BDI2000.

I set a hard break at 0x0 at the bdi prompt and the continue.
ppcboot passes control to linux at 0x0 and the bdi stops the
execution. I then change the break type to soft but will try hard.
I can then connect via gdb and set a break at start_kernel.
Everything is working fine. I can see the start_kernel code and gdb
appears to be happy with respect to setting other breaks. Once it
stops in time_init and then branches off to ppc4xx_time_init I get
the following messages on my BDI console:
*** MMU: address translation for 0x00001100 failed
*** MMU: address translation for 0x00001100 failed
*** MMU: address translation for 0x00001100 failed
*** MMU: address translation for 0x00001100 failed

continuing from here pretty much hangs gdb in the emacs window
and I've taken some kind of exception because if you stop it
with the bdi console I can see I'm sitting in panic(). I'm
guessing but it's probably either a machine check or a program.

Has anyone seen this message before? If so, what was done to resolve
them? Thanks in advance for any assistance.

-bmb

Brian Boerner
Member of Technical Staff
Pirus Networks

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-09-24 19:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24 19:11 Boerner, Brian [this message]
2001-09-24 22:31 ` MMU: address translation for 0x00001100 failed Dan Malek

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=200109241907.OAA30214@lists.linuxppc.org \
    --to=bmb@pirus.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).