On 6/24/2014 1:49 AM, Uwe Kleine-König wrote: > Hi Laura, > > On Mon, Jun 23, 2014 at 01:47:55PM -0700, Laura Abbott wrote: >> Thanks for the report. > Thanks for your reply to address it :-) > Are you already aware of the mail with Message-Id: > CAGa+x85H510fNGTXJHGYfQybRa2FGgg2NyCgJ8rmjJ6TE7GNbA@xxxxxxxxxxxxxx ? > Seems to be another fall-out but I think you were not on Cc. > >> On 6/23/2014 2:17 AM, Uwe Kleine-König wrote: >>> This patch is in 3.16-rc1 as 1c2f87c22566cd057bc8cde10c37ae9da1a1bb76 >>> now. >>> >>> Unfortunately it makes my efm32 machine unbootable. >>> >>> With earlyprintk enabled I get the following output: >>> >>> [ 0.000000] Booting Linux on physical CPU 0x0 >>> [ 0.000000] Linux version 3.15.0-rc1-00028-g1c2f87c22566-dirty (ukleinek@perseus) (gcc version 4.7.2 (OSELAS.Toolchain-2012.12.1) ) #280 PREEMPT Mon Jun 23 11:05:34 CEST 2014 >>> [ 0.000000] CPU: ARMv7-M [412fc231] revision 1 (ARMv7M), cr=00000000 >>> [ 0.000000] CPU: unknown data cache, unknown instruction cache >>> [ 0.000000] Machine model: Energy Micro Giant Gecko Development Kit >>> [ 0.000000] debug: ignoring loglevel setting. >>> [ 0.000000] bootconsole [earlycon0] enabled >>> [ 0.000000] On node 0 totalpages: 1024 >>> [ 0.000000] free_area_init_node: node 0, pgdat 880208f4, node_mem_map 00000000 >>> [ 0.000000] Normal zone: 3840 pages exceeds freesize 1024 >> >> This looks off. The number of pages for the memmap exceeds the available free >> size. Working backwards, I think the wrong bounds are being calculated in >> find_limits in arch/arm/mm/init.c . max_low is now calculated via the current >> limit but nommu never sets a limit unlike the mmu case. Can you try the >> following patch and see if it fixes the issue? If this doesn't work, can >> you share working bootup logs so I can do a bit more compare and contrast? >> >> Thanks, >> Laura >> >> ---8<---- >> From 9b19241d577caf91928e26e55413047d1be90feb Mon Sep 17 00:00:00 2001 >> From: Laura Abbott <lauraa@xxxxxxxxxxxxxx> >> Date: Mon, 23 Jun 2014 13:26:56 -0700 >> Subject: [PATCH] arm: Set memblock limit for nommu >> >> Commit 1c2f87c (ARM: 8025/1: Get rid of meminfo) changed find_limits >> to use memblock_get_current_limit for calculating the max_low pfn. >> nommu targets never actually set a limit on memblock though which >> means memblock_get_current_limit will just return the default >> value. Set the memblock_limit to be the end of DDR to make sure > s/DDR/RAM/ ? > >> bounds are calculated correctly. > This patch makes my machine boot. Full boot log appended below. > (Side note: I place my dtb in the SRAM at 0x10000000 but don't add this to > the available memory because it's only 128 KiB in size and so too small > to be worth to track. Not sure this is allowed?!) > > Thanks > Uwe > I put this in the patch tracker as 8086/1 Thanks, Laura -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
