From: Kumar Gala <kumar.gala@freescale.com>
To: "Rune Torgersen" <runet@innovsys.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Lots of memory on 826x
Date: Tue, 8 Mar 2005 12:06:48 -0600 [thread overview]
Message-ID: <bf7e05b898c09a2e140f8be26a975118@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B8592E8@ismail.innsys.innovsys.com>
I would start looking at what addresses are getting assigned for
VMALLOC vs any io_block_mapping() calls. I know I've had problems with
large amount of memory in systems if the virt addrs allocated in
io_block_mapping calls conflict with vmalloc addrs.
- kumar
On Mar 8, 2005, at 11:33 AM, Rune Torgersen wrote:
> Anybody know how to get more than 512MB (1-2GB) of RAM to work with
> 2.6.11 on a 8265?
>
> Weird stuff and crashes keep happening on kernel start (vmalloc out of
> memory, and a pci driver ups) when I tell the kernel I have more than
> 512MB of ram.
> The pci craches happens when I tell the kernel I have 740-760MB or
> more.
>
> Any idea of where to start to look for this?
>
> Rune Torgersen
> System Developer
> Innovative Systems LLC
> 1000 Innovative Drive
> Mitchell, SD 57301
> Ph: 605-995-6120
> www.innovsys.com
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
next prev parent reply other threads:[~2005-03-08 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 17:33 Lots of memory on 826x Rune Torgersen
2005-03-08 18:06 ` Kumar Gala [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-08 18:37 Rune Torgersen
2005-03-08 18:54 ` Mark Chambers
2005-03-08 20:32 ` Matt Porter
2005-03-08 21:16 Rune Torgersen
2005-03-08 23:13 ` Kumar Gala
2005-03-08 23:20 Rune Torgersen
2005-03-08 23:30 ` Matt Porter
2005-03-08 23:35 Rune Torgersen
2005-03-08 23:39 ` Matt Porter
2005-03-09 17:52 Rune Torgersen
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=bf7e05b898c09a2e140f8be26a975118@freescale.com \
--to=kumar.gala@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=runet@innovsys.com \
/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).