From: Alistair J Strachan <alistair@devzero.co.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test5-mm4
Date: Mon, 22 Sep 2003 13:17:42 +0100 [thread overview]
Message-ID: <200309221317.42273.alistair@devzero.co.uk> (raw)
In-Reply-To: <20030922013548.6e5a5dcf.akpm@osdl.org>
On Monday 22 September 2003 09:35, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test5/2
>.6.0-test5-mm4/
>
>
> . A series of patches from Al Viro which introduce 32-bit dev_t support
>
> . Various new fixes
>
>
Hi Andrew,
-mm4 won't mount my ext3 root device whereas -mm3 will. Presumably this is
some byproduct of the dev_t patches.
VFS: Cannot open root device "302" or hda2.
Please append correct "root=" boot option.
Kernel Panic: VFS: Unable to mount root fs on hda2.
One possible explanation is that I have devfs compiled into my kernel. I do
not, however, have it automatically mounting on boot. It overlays /dev (which
is populated with original style device nodes) after INIT has loaded.
Perhaps there is some other procedure I must complete before I can use 32bit
dev_t?
[alistair] 01:15 PM [/usr/src/linux-2.6] egrep -e "DEVFS" -e "EXT3_FS" .config
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_DEVFS_FS=y
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
[alistair] 01:16 PM [/usr/src/linux-2.6] dmesg | grep p2
/dev/ide/host0/bus0/target0/lun0: p1 p2 p4
Cheers,
Alistair.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-09-22 12:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 8:35 2.6.0-test5-mm4 Andrew Morton
2003-09-22 12:09 ` 2.6.0-test5-mm4 Florian Schanda
2003-09-22 12:17 ` Alistair J Strachan [this message]
2003-09-22 13:48 ` 2.6.0-test5-mm4 viro
2003-09-22 14:29 ` 2.6.0-test5-mm4 Alistair J Strachan
2003-09-22 14:30 ` 2.6.0-test5-mm4 Florian Schanda
2003-09-22 14:36 ` 2.6.0-test5-mm4 Zilvinas Valinskas
2003-09-22 13:49 ` 2.6.0-test5-mm4 Alistair J Strachan
2003-09-22 13:54 ` 2.6.0-test5-mm4 Alistair J Strachan
2003-09-22 18:55 ` 2.6.0-test5-mm4 Andrew Morton
2003-09-22 21:27 ` 2.6.0-test5-mm4 Peter Osterlund
2003-09-22 21:45 ` 2.6.0-test5-mm4 Vojtech Pavlik
2003-09-25 0:13 ` 2.6.0-test5-mm4 Peter Osterlund
2003-09-25 12:43 ` 2.6.0-test5-mm4 Vojtech Pavlik
2003-09-22 21:44 ` 2.6.0-test5-mm4 Vojtech Pavlik
2003-09-24 9:18 ` 2.6.0-test5-mm4 boot crash Helge Hafting
2003-09-24 9:57 ` viro
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=200309221317.42273.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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