Used to be you needed to build with CONFIG_ARCH_DISCONTIGMEM_ENABLE did you do this? Regards, Richard W. > -----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