On Fri, Apr 11, 2014 at 03:20:35PM +0300, Tomi Valkeinen wrote:
On 10/04/14 17:26, Russell King - ARM Linux wrote:
What's probably more relevant (which probably is a contributory factor to the allocation failure) is the command line arguments:
mem=512M vmalloc=1G
which I always supply to OMAP kernels - this forces almost all of the memory into highmem.
Is everything (well, at least display) supposed to work with that? If I try vmalloc=1G (on my config), I can't even boot with nfsroot on panda, as the USB seems to fail to initialize. And I see "cma: CMA: failed to reserve 48 MiB" at the very start of the kernel log.
Ah, I see. If I disable CMA from the kernel config, I am able to boot, although omapfb still fails to allocate the fb. However, I see a spam from oom-killer when the rootfs starts to boot.
What's the DMA-able memory when CMA is off? Is it the low mem? With vmalloc=1G, lowmem seems to be 32MB. I guess that's big enough in theory to be able to allocate a framebuffer, presuming it's not fragmented, and there's not much there, and, of course, depending on the resolution.
Yes it is supposed to boot, and does boot. Here's the results - last nights with the runtime get/put added:
http://www.arm.linux.org.uk/developer/build/result.php?type=boot&idx=173...
All the previous boot instances are here:
http://www.arm.linux.org.uk/developer/build/index.php?id=2009
and for those which just cover OMAP4:
http://www.arm.linux.org.uk/developer/build/index.php?id=2001
As ever, full details are there - configuration files, full build logs and full boot logs.