Re: [microblaze-uclinux] EXT2 filesystem on RAMDISK

[John Williams <jwilliams@xxxxxxxxxxxxxx>]

Leonid wrote:

> I tried but that didn't help. However something changed. Previously
> kernel tried to load CRAMFS FS:
> 
> cramfs: wrong magic
> FAT: bogus logical sector size 0
> FAT: bogus logical sector size 0
> Kernel panic: VFS: Unable to mount root fs on 01:00
>      <0>Rebooting in 1 seconds..
> 
> Now it doesn't complain about bad magic:
> 
> Kernel panic: VFS: Unable to mount root fs on 01:00
>  <0>Rebooting in 1 seconds..

The kernel attempts to mount a root filesystem by passing the the device
descriptor identified as the ROOT_DEV to all filesystem types that have been
registered (ie compiled/linked in).  Each FS attempts to mount - if it succeeds,
then great, otherwise it gets passed to the next in the chain.  If no filesystem
"claims" the ROOT_DEV, then you get the VFS panic you are reporting.

> I suspect it's something in the do_mount logic which is wrong - the
> question is whether it's intrinsic uClinux bug or something that has
> been introduced by Petalogix or just my other definitions are wrong. 

If you have compiled ext2 support into your kernel (double check - there's no
error output here from ext2 subsystem so I'm dubious), then the problem is that
the rootfs image itself is either corrupt, or not where the kernel expects it.

Regards,

John

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/