LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Zhou Rui <vancasperz@yahoo.com.cn>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Why does one "stw" fail with address translation disabled in PPC405EP?
Date: Sun, 24 Aug 2008 08:49:23 +1000	[thread overview]
Message-ID: <1219531763.21386.202.camel@pasglop> (raw)
In-Reply-To: <1219479992.7565.17.camel@localhost>

On Sat, 2008-08-23 at 10:26 +0200, Zhou Rui wrote:
> My board only has 32MB DRAM. Do you mean 32MB is not enough for that?
> The same codes can run well in a PPC440EP (Yosemite Board) which owns
> 256MB DRAM. At the beginning of my work, I thought memory size may be
> the cause of failure. But I did not know how to demonstrate it. So if
> the limitation of 32MB DRAM leads to the failure, are there any methods
> for the codes to solve it?

Well, it looks like the kernel is trying to access memory beyond 32M,
which would mean that the problem is that your kernel port or your
bootloader somewhat thinks there is more memory than there really is.

You need to look there... whatever passes the amount of memory to
the kernel at boot needs to be fixed.

Ben.

  reply	other threads:[~2008-08-23 22:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22 18:27 Why does one "stw" fail with address translation disabled in PPC405EP? Zhou Rui
2008-08-22 18:42 ` Josh Boyer
2008-08-23  8:26   ` Zhou Rui
2008-08-23 22:49     ` Benjamin Herrenschmidt [this message]
2008-08-24 18:55     ` Wolfgang Denk
2008-08-25 19:16       ` Zhou Rui
2008-08-28 15:53         ` Zhou Rui
2008-08-31 11:50         ` [Evolves!] " Zhou Rui
2008-09-01  5:42           ` Benjamin Herrenschmidt
2008-09-01  7:22             ` Zhou Rui
2008-09-01  7:17               ` Benjamin Herrenschmidt
2008-09-01  8:19                 ` Zhou Rui
2008-08-23 21:18   ` Zhou Rui

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=1219531763.21386.202.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=vancasperz@yahoo.com.cn \
    /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