From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Chua <jchua@fedex.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] initrd >24MB corruption
Date: 26 Aug 2002 10:54:16 +0100 [thread overview]
Message-ID: <1030355656.16618.32.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0208261621190.2610-100000@boston.corp.fedex.com>
On Mon, 2002-08-26 at 09:34, Jeff Chua wrote:
>
> I posted a similar message last week. No response, but that was on
> Gcc3.2, but when I tried out on gcc2.95.3, it failed too.
>
> Symptons:
> create 28MB ramdisk, fill up to 18MB, system boots ok.
>
> create 28MB ramdisk, fill up to 24MB, system can't boot, fail at
>
> RAMDISK: Compressed image found at block 0 ... then stuck!
>
>
> What's the next step to debug this?
Force a 1K block size when you make the fs
next prev parent reply other threads:[~2002-08-26 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 8:34 Jeff Chua
2002-08-26 9:54 ` Alan Cox [this message]
2002-08-27 0:05 ` Jeff Chua
2002-08-27 8:23 ` Russell King
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=1030355656.16618.32.camel@irongate.swansea.linux.org.uk \
--to=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
all inboxes | Powered by JetHome®