From: "John Z. Bohach" <jzb2@aexorsyst.com>
To: linux-kernel@vger.kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: large initramfs causes h/w reset after decompressing
Date: Thu, 14 Jul 2011 15:32:59 -0700 [thread overview]
Message-ID: <201107141532.59383.jzb2@aexorsyst.com> (raw)
In-Reply-To: <4E1F5C20.8000008@zytor.com>
On Thursday 14 July 2011 02:14:08 pm H. Peter Anvin wrote:
> On 07/14/2011 09:06 AM, John Z. Bohach wrote:
> > I have a large initramfs cpio file, about 890 MB, which expands to
> > 2.7 GB, and am running on linux-2.6.36.1, in 64-bit mode with 8 GB
> > of physical RAM.
> >
> > Upon loading the initramfs, I see the message "Decompressing..."
> > for a few seconds, and then comes a reset.
> >
> > This question has come up before...is there some sort of max size.
> > that I am exceeding? With 8 GB of physical memory and 64-bit arch.
> > (AMD-II), certainly seems that there should be enough memory, no?
> >
> > Thanks...
>
> What bootloader are you using? There are some bootloaders which
> don't allocate the initramfs in a very good spot.
>
> -hpa
I've actually gotten the improbable to work, and am PXE booting via
syslinux and dhcp.
It all works fine with an initramfs of ~20 MB, but that's quite a diff.
from 2.7 GB of expanded /root (890 MB cpio.tar.gz file).
But excuse my ignorance, I don't see the relevance of your
question...the initramfs is part of the kernel itself...I simply load
the kernel bzImage (all 890 MB) and that's where its all at...this is
_not_ an initrd.
--john
next prev parent reply other threads:[~2011-07-14 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 16:06 John Z. Bohach
2011-07-14 21:14 ` H. Peter Anvin
2011-07-14 22:32 ` John Z. Bohach [this message]
2011-07-14 23:26 ` H. Peter Anvin
2011-07-14 23:35 ` John Z. Bohach
2011-07-15 0:15 ` H. Peter Anvin
2011-07-15 0:35 ` John Z. Bohach
2011-07-14 16:37 John Z. Bohach
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=201107141532.59383.jzb2@aexorsyst.com \
--to=jzb2@aexorsyst.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®