From: Frank D Lombardo <lombardo@mdivac•com>
To: Clint Thomas <cthomas@Soneticom•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Kernel crash on mem= argument
Date: Thu, 19 Apr 2007 18:23:43 -0400 [thread overview]
Message-ID: <4627EBEF.2090104@mdivac.com> (raw)
In-Reply-To: <3C02138692C13C4BB675FE7EA2409529328770@bluefin.Soneticom.local>
Clint Thomas wrote:
> My u-boot config does not currently have a CONFIG_PRAM variable defined.
> Is doing this as easy as dropping in a #define in my board config? Or do
> I need to address this in another part of the code? Up until now, I just
> assumed that if I passed mem=200M to the kernel, it would allocate as
> necessary, then I could use the remaining RAM as I saw fit, but since
> this is not working I need to deal with it appropriately.
>
> Clint
>
> -----Original Message-----
> From: Frank D Lombardo [mailto:lombardo@mdivac•com]
> Sent: Thursday, April 19, 2007 2:39 PM
> To: Clint Thomas
> Cc: linuxppc-embedded@ozlabs•org
> Subject: Re: Kernel crash on mem= argument
>
> Clint Thomas wrote:
>
Clint,
I believe whats happening is that u-boot is loading the initrd in the
region of RAM above 200M. Then you pass mem=200M to the kernel, and it
can't access the initrd. By adding the appropriate CONFIG_PRAM define
to your board config file, you let u-boot know not to use the memory
above 200M either. That way u-boot will load the initrd in memory that
is usable by the kernel.
Frank
prev parent reply other threads:[~2007-04-19 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 18:29 Kernel crash on mem= argument Clint Thomas
2007-04-19 18:39 ` Frank D Lombardo
2007-04-19 20:06 ` Clint Thomas
2007-04-19 22:23 ` Frank D Lombardo [this message]
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=4627EBEF.2090104@mdivac.com \
--to=lombardo@mdivac$(echo .)com \
--cc=cthomas@Soneticom$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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