All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Kukard <nkukard@lbsd.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] kernel 2.6.33-rc4 OOPS's with large initramfs
Date: Sat, 20 Mar 2010 20:09:19 +0000	[thread overview]
Message-ID: <4BA52B6F.2060402@lbsd.net> (raw)
In-Reply-To: <4BA51A48.6010509@zytor.com>


>>>> 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.

The kernel now boots where it booted for my 64bit box.

The main problem though is the instant reboots for bzip2 and lzma
compressed initramfs images. The change for printf to /usr/bin/printf
both render the sane end result when run with the same commandline being
run in the makefile, so this isn't the issue.

-N

  reply	other threads:[~2010-03-20 20:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16 11:12 [BUG] kernel 2.6.33-rc4 OOPS's with large initramfs Nigel Kukard
2010-01-24 23:26 ` H. Peter Anvin
2010-03-20 18:12   ` Nigel Kukard
2010-03-20 18:56     ` H. Peter Anvin
2010-03-20 20:09       ` Nigel Kukard [this message]
2010-03-20 20:16         ` H. Peter Anvin
2010-03-20 20:22           ` Nigel Kukard
2010-03-20 21:37             ` H. Peter Anvin
2010-03-20 22:26               ` Nigel Kukard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BA52B6F.2060402@lbsd.net \
    --to=nkukard@lbsd.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.