From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Apr 2011 20:48:07 +0200 (CEST) Received: from mail3.caviumnetworks.com ([12.108.191.235]:11018 "EHLO mail3.caviumnetworks.com" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S1491832Ab1DASsE (ORCPT ); Fri, 1 Apr 2011 20:48:04 +0200 Received: from caexch01.caveonetworks.com (Not Verified[192.168.16.9]) by mail3.caviumnetworks.com with MailMarshal (v6,7,2,8378) id ; Fri, 01 Apr 2011 11:48:59 -0700 Received: from caexch01.caveonetworks.com ([192.168.16.9]) by caexch01.caveonetworks.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 1 Apr 2011 11:48:02 -0700 Received: from dd1.caveonetworks.com ([12.108.191.236]) by caexch01.caveonetworks.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 1 Apr 2011 11:48:02 -0700 Message-ID: <4D961DE1.50807@caviumnetworks.com> Date: Fri, 01 Apr 2011 11:48:01 -0700 From: David Daney User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Thunderbird/3.0.10 MIME-Version: 1.0 To: Michael Sundius CC: Kevin Cernekee , Ralf Baechle , David VomLehn , Dave Hansen , Andy Whitcroft , Jon Fraser , linux-mips@linux-mips.org, linux-kernel@vger.kernel.org, stable@kernel.org Subject: Re: [PATCH v2] MIPS: Kernel crashes on boot with SPARSEMEM + HIGHMEM enabled References: <4D9603D8.2010709@caviumnetworks.com> <4D961C6A.9070808@cisco.com> In-Reply-To: <4D961C6A.9070808@cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 01 Apr 2011 18:48:02.0048 (UTC) FILETIME=[54073000:01CBF09D] Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 29677 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: ddaney@caviumnetworks.com Precedence: bulk X-list: linux-mips On 04/01/2011 11:41 AM, Michael Sundius wrote: > David Daney wrote: >> >> >> I think this may do the same thing as my patch: >> >> http://patchwork.linux-mips.org/patch/1988/ >> >> Although my patch had different motivations, and changes some other >> things around too. >> >> David Daney >> > I'm not really sure why your kernel or initrd would be in memory was not > within > the range that had been accounted for. are you saying its in high mem? > Well the memory initialization code has a bunch of weird rules built in that prevent some memory from being used. For example if the kernel resides in a different SPARSE page than the rest of memory bad things happen because memory_present() was not called on something that is later freed (when init memory is released). If I try to put an initrd at a high physical address, the memory below that is not usable. My three patches try to make some sense out of the whole thing. David Daney