mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
To: "Mike Galbraith" <mikeg@wen-online.de>, <linux-kernel@vger.kernel.org>
Cc: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
Subject: Re: Problem with Ramdisk in linux-2.4.1
Date: Tue, 13 Feb 2001 11:16:43 -0800	[thread overview]
Message-ID: <009401c095f1$83b04c40$bba6b3d0@Toshiba> (raw)
In-Reply-To: <Pine.Linu.4.10.10102130916110.805-100000@mikeg.weiden.de> <005e01c095f0$6c1b6c00$bba6b3d0@Toshiba>

Dear Mike and others ,

Sometimes i also get :-

incomplete literal tree
OR
incomplete distance tree

along with

invalid compressed format (err=1)
OR
invalid compressed format (err=2)
OR
crc error

And it is very strange because for the same ramdisk , linux2.4.1 shows me
all the error messages .

I am using Ramdisk of 8 MB on compression it becomes around 1.4 MB.

Please help me.

Thanks ,

Best Regards,

 Jaswinder.
 --
 These are my opinions not 3Di.


----- Original Message -----
From: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
To: "Mike Galbraith" <mikeg@wen-online.de>; <linux-kernel@vger.kernel.org>
Cc: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
Sent: Tuesday, February 13, 2001 11:08 AM
Subject: Re: Problem with Ramdisk in linux-2.4.1


> Dear Mike and others ,
>
> I am using compressed ramdisk , i can not turn off cramfs .
>
> my error messages are very strange and irreregular .
>
> i am getting 3 different kind of error messages :-
>
> invalid compressed format (err=1)
> OR
> invalid compressed format (err=2)
> OR
> crc error
>
> I am using gzip 1.2.4 (18 Aug 93)
>
> But when i use same ramdisk with old kernel like 2.2.12 , it works fine .
>
> Please help me.
>
> Thanks ,
>
> Best Regards,
>
> Jaswinder.
> --
> These are my opinions not 3Di.
>
> ----- Original Message -----
> From: "Mike Galbraith" <mikeg@wen-online.de>
> To: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
> Sent: Tuesday, February 13, 2001 12:22 AM
> Subject: Re: Problem with Ramdisk in linux-2.4.1
>
>
> > On Mon, 12 Feb 2001, Jaswinder Singh wrote:
> >
> > > Dear linux-kernel mailing list,
> > >
> > > I am facing this problem in linux-2.4.1 :-
> > >
> > > RAMDISK driver initialized: 16 RAM disks of 8192K size
> > > 1024 blocksize
> > > RAMDISK: Compressed image found at block 0
> > >  incomplete distance tree
> > > invalid compressed format (err=1)Freeing initrd
> > > memory: 4096k freed
> > >
> > > Is any body seen this problem earlier , any hint .
> >
> > Hi,
> >
> > I think I might have seen this problem before.  If this isn't
> > a cramfs initrd, turn off cramfs and I think it'll work right.
> > I once had cramfs on by accident, and I found that my initrd
> > wouldn't load.
> >
> > -Mike
> >
>


  reply	other threads:[~2001-02-13 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.Linu.4.10.10102130916110.805-100000@mikeg.weiden.de>
2001-02-13 19:08 ` Jaswinder Singh
2001-02-13 19:16   ` Jaswinder Singh [this message]
2001-02-13 19:56   ` Mike Galbraith
2001-02-13 20:55     ` Jaswinder Singh
2001-02-14  5:21       ` Mike Galbraith
2001-02-12  8:19 Jaswinder Singh
2001-02-12 19:10 ` Jaswinder Singh

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='009401c095f1$83b04c40$bba6b3d0@Toshiba' \
    --to=jaswinder.singh@3disystems.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    /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®