linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "G. Guével" <gguevel@interfaceconcept.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: MMU problems on MPC860P
Date: Fri, 15 Sep 2000 18:40:09 +0200	[thread overview]
Message-ID: <000101c01f33$a5f58ca0$2901a8c0@none> (raw)


Hello,

I have a MBX MPC860 board and a montavista linux kernel 2.2.13 which works
very well.

I want to port this kernel on a MPC860P proprietary board called pLines.
I can execute my kernel init until the last execve command which launches
the sh command.
I can get my ip address from a bootp server and mount a network file system.

When the execve is run the following functions are called :
do_load_elf_binary - flush_old_exec - exec_mmap - new_page_tables -
SET_PAGE_DIR
This last function calls an asm instruction, ie "mtspr M_TWB 1DF00".
On the MBX board it is "mtspr M_TWB 1DE00".

This instruction sets the tablewalk level one base value.

If I comment this instruction, I can have the ash application which crashes
when calling other applications.
If I uncomment this instruction I have nothing.

If I add an infinitely printk loop after the mtspr, printk works during 2 to
3 s then cpu crashes.
But printk seems not to be sure while page manipulation.

Any help on this subject will be welcome.

Thanks to all
Sorry for my poor english language, je suis français.

Bye
Gerard Guevel


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

             reply	other threads:[~2000-09-15 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-15 16:40 G. Guével [this message]
2000-09-15 17:19 ` MMU problems on MPC860P Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2000-09-19 17:51 G. Guivel
2000-09-19 22:15 ` Dan Malek
2000-09-28 14:28 Girard Guivel

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='000101c01f33$a5f58ca0$2901a8c0@none' \
    --to=gguevel@interfaceconcept.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).