From: Andreas Steinmetz <ast@domdv.de>
To: Nick Ivanter <nick@emcraft.ru>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.10-pre13: Panic mounting initrd
Date: Fri, 21 Sep 2001 17:39:03 +0200 (CEST) [thread overview]
Message-ID: <XFMail.20010921173903.ast@domdv.de> (raw)
In-Reply-To: <01092119193901.01004@iron.auriga.ru>
On 21-Sep-2001 Nick Ivanter wrote:
> Andreas,
>
> Looks like you somehow haven't compiled ext2fs support into your new kernel.
> Try to check that.
>
If things would be that easy...
Snippets from a slight modification to mount_root() in fs/super.c
for (fs_type = file_systems ; fs_type ; fs_type = fs_type->next) {
printk("VFS: Processing %s\n",fs_type->name);
if (!(fs_type->fs_flags & FS_REQUIRES_DEV))
continue;
if (!try_inc_mod_count(fs_type->owner))
continue;
printk("VFS: Trying %s\n",fs_type->name);
And now the results during boot (snippets again):
VFS: Processing bdev
VFS: Processing proc
VFS: Processing sockfs
VFS: Processing tmpfs
VFS: Processing pipefs
VFS: Processing ext2
VFS: Trying ext2
VFS: Processing msdos
VFS: Trying msdos
VFS: Processing vfat
VFS: Trying vfat
VFS: Processing iso9660
VFS: Trying iso9660
VFS: Processing nfs
VFS: Processing reiserfs
VFS: Trying reiserfs
Kernel Panic: ...
This clearly shows that there's definitely something going _very_ wrong.
Best bet is loading/decompression of initrd. As far as I'm following the list
there were initrd modifications discussed/done by Alexander Viro/Andrea
Arcangeli.
Andreas Steinmetz
D.O.M. Datenverarbeitung GmbH
next parent reply other threads:[~2001-09-21 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01092119193901.01004@iron.auriga.ru>
2001-09-21 15:39 ` Andreas Steinmetz [this message]
2001-09-21 15:52 ` 2.4.10-pre13: Panic mounting initrd Alexander Viro
2001-09-21 13:29 Andreas Steinmetz
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=XFMail.20010921173903.ast@domdv.de \
--to=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@emcraft.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.