From: Voluspa <voluspa@bigfoot.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.6-pre3 Kernel panic: VFS: Unable to mount root fs on 03:02
Date: Thu, 7 Mar 2002 11:48:45 +0100 [thread overview]
Message-ID: <20020307114845.530abcfa.voluspa@bigfoot.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0203070329090.24127-100000@weyl.math.psu.edu>
In-Reply-To: <20020307085636.4feb2372.voluspa@bigfoot.com> <Pine.GSO.4.21.0203070329090.24127-100000@weyl.math.psu.edu>
On Thu, 7 Mar 2002 03:42:32 -0500 (EST)
Alexander Viro <viro@math.psu.edu> wrote:
> and what filesystems are compiled in? Actually, adding printk("%s\n", p);
> in the same place might give some hints...
Gave:
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
ext2
VFS: Cannot open root device "302" or 03:02
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 03:02
Since I've used "make oldconfig" and:
loke:loke:/usr/src/test$ diff my-2.5.6-pre2-.config my-2.5.6-pre3-.config
288d287
< CONFIG_IDE_TASK_IOCTL=y
291c290
< # IDE chipset support/bugfixes
---
> # IDE chipset support
301d299
< # CONFIG_BLK_DEV_IDEDMA_FORCED is not set
only show enforced differences, I could boot into 2.5.6-pre2 tonight (about 6 hours from now) and dump whatever info you need - if it is deemed necessary. Otherwise I'll just enjoy the -ac series until a -preX turns up that is bootable.
Regards,
Mats Johannesson
Sweden
next prev parent reply other threads:[~2002-03-07 10:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 6:21 Voluspa
2002-03-07 6:29 ` Alexander Viro
2002-03-07 7:56 ` Voluspa
2002-03-07 8:42 ` Alexander Viro
2002-03-07 9:21 ` Voluspa
2002-03-07 10:48 ` Voluspa [this message]
2002-03-07 11:09 ` Alexander Viro
2002-03-07 16:29 ` Voluspa
2002-03-07 16:57 ` Martin Dalecki
2002-03-07 12:37 ` Martin Dalecki
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=20020307114845.530abcfa.voluspa@bigfoot.com \
--to=voluspa@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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®