From: Michael Neuling <mikey@neuling.org>
To: "Scott D. Davilla" <davilla@4pi.com>
Cc: kexec@lists.infradead.org
Subject: Re: initramfs failing, 7MB limit?
Date: Wed, 12 Mar 2008 13:36:35 +0100 [thread overview]
Message-ID: <17393.1205325395@neuling.org> (raw)
In-Reply-To: <p06230929c3fb22e35e94@[192.168.9.5]>
> This is OT but I'm seeing what seems like a 7MB limit on an initramfs
> under 2.6.24.3.
>
> I can boot an initramfs which also works under kexec that has a cpio
> size of 6480384 bytes. I have another (created the same way) that
> has more userland tools with a size of 7395328 bytes. That fails
> under both boot and kexec with the kernel not finding "/init" and
> panicking. "/init" is present and executable in the initramfs. This
> fails on the target hardware and two other standard PC hardware with
> 256M, 512M and 1G of RAM.
>
> I use the kernel scripts (scripts/gen_initramfs_list.sh and
> usr/gen_init_cpio ) to create the cpio based initramfs but it's not
> embedded in the kernel. It's a standalone initramfs that gets passed
> to the bootloader/kexec.
>
> It's my understanding that with an initramfs, one is just limited to
> available RAM and there are no set size limits.
>
> Anyone else see this behavior or am I doing something incredibly stupid.
We have booted with very large initramfs (greater than 100MB) on ppc64
and not had a problem.
You're probably having problems the initramfs overwriting some other
important information. What does the memory map look like? Where is
the initramfs located in memory and what is after it?
Mikey
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-03-12 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 17:56 initramfs failing, 7MB limit? Scott D. Davilla
2008-03-12 12:36 ` Michael Neuling [this message]
2008-03-12 14:08 ` Scott D. Davilla
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=17393.1205325395@neuling.org \
--to=mikey@neuling.org \
--cc=davilla@4pi.com \
--cc=kexec@lists.infradead.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