public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: viro@parcelfarce.linux.theplanet.co.uk
To: Walt H <waltabbyh@comcast.net>
Cc: arekm@pld-linux.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: initrd and 2.6.0-test8
Date: Sat, 18 Oct 2003 18:52:36 +0100	[thread overview]
Message-ID: <20031018175236.GA7665@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3F916A0C.10800@comcast.net>

On Sat, Oct 18, 2003 at 09:27:56AM -0700, Walt H wrote:
> 
> > Hi,
> > 
> > Seems that something changed between test7 and test8 regarding initrd or romfs 
> > support. I'm using highly modularized 2.6.0 kernel which has all filesystems 
> > beside romfs compiled as modules (romfs is compiled inside of kernel).
> > 
> > Modules for my rootfs are loaded from initrd (which is image with romfs as 
> > filesystem) but starting from test8 kernel is not able to mount initrd 
> > filesystem - stops with typical message about not being able to mount rootfs.
> > 
> > cset test7 from 20031012_0407 is known to be ok so something was changed later
> 
> 
> I noticed this happened in 2.6.0-test6-mm4. Backing out this patch fixes
> it in the short-term.

Even better would be to report the bug ;-/

I can't reproduce it here.  2.6.0-test8 vanilla, so far (last 15 minutes)
tried with
	* compressed initrd image
	* plain ext2
and I'll try romfs as soon as I hunt down mkfs for that animal.  All
appears to be working...

What did it say before the "typical message"?  Specifically, were there
any lines starting with RAMDISK:?

.config would be also useful.

  reply	other threads:[~2003-10-18 17:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-18 16:27 initrd and 2.6.0-test8 Walt H
2003-10-18 17:52 ` viro [this message]
2003-10-18 18:22   ` viro
2003-10-18 18:33   ` Christophe Saout
2003-10-18 19:41     ` [PATCH] initrd with devfs enabled (Re: initrd and 2.6.0-test8) viro
2003-10-18 21:56       ` Arkadiusz Miskiewicz
2003-10-18 22:11         ` viro
2003-10-18 22:46           ` Arkadiusz Miskiewicz
2003-10-18 23:07       ` Valdis.Kletnieks
  -- strict thread matches above, loose matches on Subject: below --
2003-10-18 19:10 initrd and 2.6.0-test8 Svetoslav Slavtchev
2003-10-18 19:25 ` viro
2003-10-18 19:33   ` Svetoslav Slavtchev
2003-10-18 20:32   ` Witold Krecicki
2003-10-18 20:43     ` viro
2003-10-18 22:25   ` Svetoslav Slavtchev
2003-10-18 18:02 Witold Krecicki
2003-10-18 19:41 ` Valdis.Kletnieks
2003-10-18 19:57   ` viro
2003-10-18 13:05 Arkadiusz Miskiewicz

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=20031018175236.GA7665@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=arekm@pld-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=waltabbyh@comcast.net \
    /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