From: Jeff Harrell <jharrell@ti.com>
To: sgi-mips <linux@cthulhu.engr.sgi.com>,
linux-mips <linux-mips@fnet.fr>,
linux-mips <linux-mips@vger.rutgers.edu>
Subject: Question concerning memory initialization (4M->64M)
Date: Wed, 09 Feb 2000 13:35:58 -0700 [thread overview]
Message-ID: <38A1CFAE.EFA429BA@ti.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
I have run into an interesting problem and would like to run it past
this newsgroup
to see if anyone has any experience in these areas. I am running kernel
2.3.22 and
have upgraded my memory space from ~4M (0x400000) to ~64M (0x4000000).
I run the 4M
version of the kernel and have no problems but when I run the 64M
version, I run
into problems during the mem_init() portion of the code. Specifically
during the
free_page(tmp) call during the determination of totalram, codepages and
datapages.
It looks like it is failing during the call to remove_mem_queue() within
free_pages_ok().
I am seeing the next->prev and prev->next set to 0 causing a page
fault. Is there
anything that anyone is aware of that I would need to change (beyond
mips_memory_upper)
that would enable me to increase available memory to 64M. Any insights
would be greatly appreciated.
Thanks
Jeff
Additional information:
------------------
high memory: 0x83fff000 start memory: 0x80433000
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jeff Harrell Work: (801) 619-6104
Broadband Access group/TI
jharrell@ti.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[-- Attachment #2: Type: text/html, Size: 1537 bytes --]
next reply other threads:[~2000-02-09 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-09 20:35 Jeff Harrell [this message]
2000-02-10 16:15 ` Question concerning memory initialization (4M->64M) Ralf Baechle
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=38A1CFAE.EFA429BA@ti.com \
--to=jharrell@ti.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@vger.rutgers.edu \
--cc=linux@cthulhu.engr.sgi.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