> -----Original Message----- > From: Woodruff, Richard > Sent: Saturday, August 08, 2009 2:49 AM > To: Syed Mohammed, Khasim; linux-arm-kernel@xxxxxxxxxxxxxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx > Subject: RE: Exception while handling MEM Hole on OMAP3 / ARM Cortex A8 > > Used to be you needed to build with CONFIG_ARCH_DISCONTIGMEM_ENABLE did you do this? > Hi Richard, This shows as deprecated, # Discontigmem is deprecated config ARCH_DISCONTIGMEM_ENABLE I tried this today, enabling this for ARCH_OMAP results in compilation error In file included from arch/arm/kernel/asm-offsets.c:14: include/linux/mm.h: In function 'virt_to_head_page': include/linux/mm.h:310: error: implicit declaration of function 'KVADDR_TO_NID' include/linux/mm.h:310: error: implicit declaration of function 'LOCAL_MAP_NR' This is because NODE_MEM_SIZE_BITS is not enabled, I didn't get a proper value just tried copying others with 24 and 26, - THIS Just didn't boot to prompt. Should we fix this up? -or leave it out as it is getting deprecated ? Thanks for the input. Regards, Khasim > > > -----Original Message----- > > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > > owner@xxxxxxxxxxxxxxx] On Behalf Of Syed Mohammed, Khasim > > Sent: Friday, August 07, 2009 3:17 PM > > To: linux-arm-kernel@xxxxxxxxxxxxxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx > > Subject: Exception while handling MEM Hole on OMAP3 / ARM Cortex A8 > > > > Hi all, > > > > On OMAP3 we are creating a space for DSP components to have shared buffers > > using the boot arguments. > > > > mem=88M@0x80000000 mem=128M@0x88000000 > > > > This creates a 40M hole for DSP components, the drivers dynamically do a > > request mem region and ioremap of pre-defined address space with in the 40M > > region. > > > > With the above setup, we see the system running for a while but then ends up > > with exception. > > > > "Unable to handle kernel paging request at virtual address c7381000" > > > > The address reported here is not in kernel space, and this doesn't result in a > > kernel panic. > > > > Other observation: > > - The same setup works fine with no hole or space created. The 40M space for > > DSP components will be allocated at the end (216M). > > - If we increase the mem hole region we can make the system fail with in less > > time. > > - Free returns expected memory map > > > > While I am still debugging the issue, I thought of posting this message to > > know if there are any known issues with ARM architecture in handling such non > > contiguous space / mem hole. > > > > I see some special boot parameters for other architectures like exactmap, we > > don't see similar stuff on ARM. Do we need to port any such support for ARM ? > > > > Kindly advice, > > > > Thanks. > > > > Regards, > > Khasim > > > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
