Re: 2.5.6-pre3 Kernel panic: VFS: Unable to mount root fs on 03:02

[Voluspa]

On Thu, 7 Mar 2002 03:42:32 -0500 (EST)
Alexander Viro <[e-mail]> 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
        ext2
        minix
        msdos
        vfat
        iso9660
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.

Regards,
Mats Johannesson
Sweden