* [BUG] initrd >24MB corruption
@ 2002-08-26 8:34 Jeff Chua
2002-08-26 9:54 ` Alan Cox
0 siblings, 1 reply; 4+ messages in thread
From: Jeff Chua @ 2002-08-26 8:34 UTC (permalink / raw)
To: Linux Kernel
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?
Thanks,
Jeff
[ jchua@fedex.com ]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [BUG] initrd >24MB corruption
2002-08-26 8:34 [BUG] initrd >24MB corruption Jeff Chua
@ 2002-08-26 9:54 ` Alan Cox
2002-08-27 0:05 ` Jeff Chua
0 siblings, 1 reply; 4+ messages in thread
From: Alan Cox @ 2002-08-26 9:54 UTC (permalink / raw)
To: Jeff Chua; +Cc: Linux Kernel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [BUG] initrd >24MB corruption
2002-08-26 9:54 ` Alan Cox
@ 2002-08-27 0:05 ` Jeff Chua
2002-08-27 8:23 ` Russell King
0 siblings, 1 reply; 4+ messages in thread
From: Jeff Chua @ 2002-08-27 0:05 UTC (permalink / raw)
To: Alan Cox; +Cc: Linux Kernel
On 26 Aug 2002, Alan Cox wrote:
> > RAMDISK: Compressed image found at block 0 ... then stuck!
> Force a 1K block size when you make the fs
That was the default for mke2fs.
Tried compress instead of gzip. Same problem. I guess the compressed file
is too big for the kernel. The 8MB compressed (from 24MB) didn't work. 6MB
compressed from 18MB worked. The 24MB filesystem has just one extra junk
file in /tmp to fill up the filesystem to 90% and this caused the system
to hang.
I'm thinking it could be the ungzip function in the kernel that's causing
the problem.
Jeff.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [BUG] initrd >24MB corruption
2002-08-27 0:05 ` Jeff Chua
@ 2002-08-27 8:23 ` Russell King
0 siblings, 0 replies; 4+ messages in thread
From: Russell King @ 2002-08-27 8:23 UTC (permalink / raw)
To: Jeff Chua; +Cc: Linux Kernel
On Tue, Aug 27, 2002 at 08:05:14AM +0800, Jeff Chua wrote:
> On 26 Aug 2002, Alan Cox wrote:
> > > RAMDISK: Compressed image found at block 0 ... then stuck!
> > Force a 1K block size when you make the fs
>
> That was the default for mke2fs.
>
> Tried compress instead of gzip. Same problem. I guess the compressed file
> is too big for the kernel. The 8MB compressed (from 24MB) didn't work. 6MB
> compressed from 18MB worked. The 24MB filesystem has just one extra junk
> file in /tmp to fill up the filesystem to 90% and this caused the system
> to hang.
>
> I'm thinking it could be the ungzip function in the kernel that's causing
> the problem.
Out of curiosity, how much RAM do you have available?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-08-27 8:19 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-08-26 8:34 [BUG] initrd >24MB corruption Jeff Chua
2002-08-26 9:54 ` Alan Cox
2002-08-27 0:05 ` Jeff Chua
2002-08-27 8:23 ` Russell King
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®