Re: [BUG] kernel 2.6.33-rc4 OOPS's with large initramfs

[H. Peter Anvin]

On 03/20/2010 11:12 AM, Nigel Kukard wrote:
> On 01/24/10 23:26, H. Peter Anvin wrote:
>> On 01/16/2010 03:12 AM, Nigel Kukard wrote:
>>   
>>> Generating a initramfs with the following, one of about 30Mb, one of 77Mb.
>>> find . | cpio -o -H newc > ../initramfs.cpio
>>>
>>> Only difference is adding of more files to the 77Mb image.
>>>
>>> It makes no difference if its compiled into kernel or used as initrd.
>>> Compression types makes no difference either.
>>>
>>> Tested on 2.6.32.3->2.6.33-rc4 , all fail with the below.
>>>
>>> The 30Mb initramfs loads fine, the 77Mb image throws the following...
>>>
>>>     
>> What are the exact compressed and uncompressed files (or is that an
>> uncompressed initramfs)?
>>   
> 
> Ok ... I revisited this, sorry for the delay, all tests done on kernel
> 2.6.33.1
> 
> (initramfs uploaded, link below)
> 
> It is generated using two commands...
> find . | cpio -o --quiet -H newc -A -O ../initramfs.cpio
> 
> and the kernel modules are appended to this using...
> find . | cpio -o --quiet -H newc -A -O ../initramfs.cpio
> 
> The exact size is ..
> % ls -la initramfs.cpio
> -rw-r--r-- 1 nkukard nkukard 115944448 Mar 19 22:15 initramfs.cpio
> 

How much RAM are you giving your VM?  The default for Qemu is 128 MB,
and if you have a 110 MB initramfs it's hardly surprising that you get
an out of memory error.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/