From: Erik Andersen <andersen@codepoet.org>
To: Jeff Chua <jchua@fedex.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] initrd >24MB corruption (fwd)
Date: Mon, 26 Aug 2002 20:56:16 -0600 [thread overview]
Message-ID: <20020827025616.GA6998@codepoet.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0208271038450.25059-100000@boston.corp.fedex.com>
On Tue Aug 27, 2002 at 10:49:13AM +0800, Jeff Chua wrote:
>
> Alan,
>
> Who else can help with this problem? I tried to write to Werner
> Almesberger <werner.almesberger@epfl.ch> (no such email) and Hans Lermen
> <lermen@fgan.de>, but no response from either.
>
> I'm suspecting that somehow part of initrd is being corrupted during boot
> up or may be ungzip is not working properly, because I can definitely
> gzip/ungzip on all versions of running Linux for the ram.gz filesystem I
> created. Again, the only difference between ram-18mb.gz (6MB) and
> ram-24mb.gz (8MB) is ram24.gz contains one extra file to fill up the
> filesystem to 90%.
>
> Same bzImage, same ramdisk_size=28000, just different initrd files.
> ram-18mb.gz boots, ram-24mb.gz hangs.
How much total ram does your system have?
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2002-08-27 2:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 2:49 [BUG] initrd >24MB corruption (fwd) Jeff Chua
2002-08-27 2:56 ` Erik Andersen [this message]
2002-08-27 8:55 ` Jeff Chua
2002-08-27 9:30 ` Russell King
2002-08-28 5:37 ` Jeff Chua
2002-08-28 5:59 ` Jeff Chua
2002-08-30 7:12 ` Jeff Chua
2002-09-14 3:02 ` Werner Almesberger
2002-09-14 3:35 ` Jeff Chua
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=20020827025616.GA6998@codepoet.org \
--to=andersen@codepoet.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jchua@fedex.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