From: "H. Peter Anvin" <hpa@zytor.com>
To: Nigel Kukard <nkukard@lbsd.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] kernel 2.6.33-rc4 OOPS's with large initramfs
Date: Sun, 24 Jan 2010 15:26:09 -0800 [thread overview]
Message-ID: <4B5CD711.7050204@zytor.com> (raw)
In-Reply-To: <4B519F14.7020104@lbsd.net>
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)?
Also, you're describing how to reproduce this with Qemu, but have you
tried with other bootloaders? Which version of Qemu (some versions of
the Qemu bootloaders had a lot of problems.)
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-01-24 23:26 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 [this message]
2010-03-20 18:12 ` Nigel Kukard
2010-03-20 18:56 ` H. Peter Anvin
2010-03-20 20:09 ` Nigel Kukard
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=4B5CD711.7050204@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nkukard@lbsd.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox