From jharrell@ti.com Wed Feb 9 21:33:48 2000 Received: from gatekeep.ti.com (gatekeep.ti.com [192.94.94.61]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA07763; Wed, 9 Feb 2000 21:33:47 +0100 (MET) Received-Date: Wed, 9 Feb 2000 21:33:47 +0100 (MET) Received: from dlep7.itg.ti.com ([157.170.134.103]) by gatekeep.ti.com (8.9.3/8.9.3) with ESMTP id OAA08445; Wed, 9 Feb 2000 14:32:59 -0600 (CST) Received: from dlep7.itg.ti.com (localhost [127.0.0.1]) by dlep7.itg.ti.com (8.9.3/8.9.3) with ESMTP id OAA21227; Wed, 9 Feb 2000 14:32:54 -0600 (CST) Received: from dlep4.itg.ti.com (dlep4.itg.ti.com [157.170.188.63]) by dlep7.itg.ti.com (8.9.3/8.9.3) with ESMTP id OAA21216; Wed, 9 Feb 2000 14:32:53 -0600 (CST) Received: from ti.com (IDENT:jharrell@pcp97780pcs.sc.ti.com [158.218.100.100]) by dlep4.itg.ti.com (8.9.3/8.9.3) with ESMTP id OAA22208; Wed, 9 Feb 2000 14:32:57 -0600 (CST) Sender: jharrell@dsbmail.itg.ti.com Message-ID: <38A1CFAE.EFA429BA@ti.com> Date: Wed, 09 Feb 2000 13:35:58 -0700 From: Jeff Harrell X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: sgi-mips , linux-mips , linux-mips Subject: Question concerning memory initialization (4M->64M) Content-Type: multipart/alternative; boundary="------------0BB6A84381EA7F784BD03864" --------------0BB6A84381EA7F784BD03864 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------0BB6A84381EA7F784BD03864 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  
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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

  --------------0BB6A84381EA7F784BD03864--