LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: happa@wmlab.csie.ncu.edu.tw
To: linuxppc-embedded@ozlabs.org
Subject: About MMU setting in MPC8245
Date: Thu, 12 Jan 2006 14:45:42 +0800(CST)	[thread overview]
Message-ID: <20060112064542.CB1581100F2@wmlab.csie.ncu.edu.tw> (raw)

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

Hi, Mark,
    Thanks for your information.
    
>Are you in PCI host mode?  If so, the first sentence of chapter 3--
>Address Maps of the 8245 manual states:

>	"The MPC8245 in PCI host mode supports an address mapping
>	configuration that is designated as address map B."

>Map B == CHRP mapping.

Yes, my CPU is in PCI host mode, and my address is use Map B.

I'm figure out my problem.

My kernel seems work fine until it calling run_init_process("/sbin/init").

run_init_process("/sbin/init")
   |
   v
..wait until the file got from NFS .....     
   |
   v 
 load_elf_binary()
   |
   v
 flush_old_exec()
   |
   v
 exec_mmap()
   |
   v
 activate_mm() ---> After this function is called any virtual memory operations
                    (access address out of my physical dram range), will let kernel jump into exception mode.
"Oops: kernel access of bad area, sig: 11 [#2]"


So I guess the problem is relative to mmu setting.
Would you give me any idea which part I need to check?

Thanks.

/Wen

             reply	other threads:[~2006-01-12  6:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12  6:45 happa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-11 10:26 About MMU setting in MPC8245 happa
2006-01-11 16:07 ` Mark A. Greer

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=20060112064542.CB1581100F2@wmlab.csie.ncu.edu.tw \
    --to=happa@wmlab.csie.ncu.edu.tw \
    --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