From: "Greg Griffes" <ggg@ieee.org>
To: "Steven Blakeslee" <BlakesleeS@embeddedplanet.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: question concerning ram filestructure
Date: Tue, 9 Apr 2002 18:59:45 -0400 [thread overview]
Message-ID: <002901c1e01a$3e8d3e60$6401a8c0@attbi.com> (raw)
In-Reply-To: 001701c1e017$e74f7b60$6401a8c0@attbi.com
Steven,
I must retract my previous message. After closer scrutiny of your
log message, I realized that you are getting a crc error, I assume
during the decompression. I did not have that problem.
I wonder if it could be a difference in gzip that is used to compress
the ram disk on the host and the gunzip version built into your kernel.
Just speculating.
Greg
>
> >
> > RAMDISK: Compressed image found at block 0
> > crc errorFreeing initrd memory: 2201k freed
> > Kernel panic: VFS: Unable to mount root fs on 01:00
> > <0>Rebooting in 180 seconds..
> >
> > I've seen this before on different ports of linux but I have not been able
> > to figure it out. Does anyone have suggestions?
> > Steven Blakeslee
> >
>
> I just had the same symptom in my port this morning. In my case, the
> kernel was not picking up the initrd_start or initrd_size from the boot
> loader. It was a bug in my *_setup.c file. I tossed out the use of r4 and r5
> and switched to using parse_bootinfo in platform_init(). That fixed it.
>
> It could also be a problem in the boot loader.
>
> Greg Griffes
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-09 22:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 20:38 question concerning ram filestructure Steven Blakeslee
2002-04-09 22:43 ` Greg Griffes
2002-04-09 22:59 ` Greg Griffes [this message]
2002-04-10 8:50 ` Alex Zeffertt
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='002901c1e01a$3e8d3e60$6401a8c0@attbi.com' \
--to=ggg@ieee.org \
--cc=BlakesleeS@embeddedplanet.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).