[lkml]   [2002]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.5.6-pre3 Kernel panic: VFS: Unable to mount root fs on 03:02
On Thu, 7 Mar 2002 03:42:32 -0500 (EST)
Alexander Viro <> wrote:

> > mount() -> -14
> > VFS: Cannot open root device "302" or 03:02
> Bloody hell... 14 is EFAULT. And that - from sys_mount() called by

Hey, you're talking to pure user land here (but I guess it's meant for the other kernel hackers :-)

> task that has KERNEL_DS as addr_limit. What options do you pass to kernel
> and what filesystems are compiled in?

No options at all, except what lilo provides:

loke:loke:/proc$ cat cmdline
BOOT_IMAGE=2.4-Linux-test ro root=302 ramdisk=0

(Exchange 2.4-Linux-test with 2.5-Linux-test)

File systems compiled in:

loke:loke:/proc$ cat filesystems
nodev rootfs
nodev bdev
nodev proc
nodev sockfs
nodev tmpfs
nodev pipefs
nodev binfmt_misc
nodev nfs

Not changed in 2.5 (preempt enabled there shouldn't make a difference)

> Actually, adding printk("%s\n", p);
> in the same place might give some hints...

I interpret that as printk("mount() -> %d\n", err); can be swapped with printk("%s\n", p); and I'll do that right away. Last compile, then I must rush to work.

Mats Johannesson
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.064 / U:1.892 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site