Re: [beagleboard] Kernel panic - not syncing: VFS: Unable to mount root fs

[omapbuddy omapreddy]

On 12/30/12, Brent <bren...@hotmail.com> wrote:
> I am in the process of getting the Chipsee 7" LCD with capacitive touch
> working with Angstrom. So far, I have copied the
> /arch/arm/omap2/board-am335xevm.c file and the /drivers/video/da8xx-fb.c
> file from Chipsee into my kernel sources. This has the LCD working as I
> can now see my splash screen, but I'm getting a Kernel Panic error when
> booting the kernel. I know that I need to merge the files from Chipsee and
>
> BeagleBon together, but for now I'm just trying to get the basics working.
>
> Does anyone know what would cause these errors?
> [ 0.445312] mtdoops: mtd device (mtddev=name/number) must be supplied
> [ 0.652893] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(179,2)
>
>
>
> ## Booting kernel from Legacy Image at 80007fc0 ...
> Image Name: Linux-3.2.21-13823-g7b09ccc-dirt
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 3055824 Bytes = 2.9 MiB
> Load Address: 80008000
> Entry Point: 80008000
> Verifying Checksum ... OK
> XIP Kernel Image ... OK
> OK
> Starting kernel ...
> Uncompressing Linux... done, booting the kernel.
> [ 0.150024] tps65910 1-002d: could not be detected
> [ 0.187683] Could not set LED4 to fully on
> [ 0.315856] _omap_mux_get_by_name: Could not find signal
> gpmc_ad8.lcd_data16
> [ 0.323272] _omap_mux_get_by_name: Could not find signal
> gpmc_ad9.lcd_data17
> [ 0.330627] _omap_mux_get_by_name: Could not find signal
> gpmc_ad10.lcd_data18
> [ 0.338104] _omap_mux_get_by_name: Could not find signal
> gpmc_ad11.lcd_data19
> [ 0.345550] _omap_mux_get_by_name: Could not find signal
> gpmc_ad12.lcd_data20
> [ 0.353027] _omap_mux_get_by_name: Could not find signal
> gpmc_ad13.lcd_data21
> [ 0.360473] _omap_mux_get_by_name: Could not find signal
> gpmc_ad14.lcd_data22
> [ 0.367919] _omap_mux_get_by_name: Could not find signal
> gpmc_ad15.lcd_data23
> [ 0.399078] _omap_mux_get_by_name: Could not find signal NULL
> [ 0.445312] mtdoops: mtd device (mtddev=name/number) must be supplied
> [ 0.652893] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(179,2)
> [ 0.661712] Backtrace:
> [ 0.664306] [<c001789c>] (dump_backtrace+0x0/0x10c) from [<c03f73ac>]
> (dump_stack+0x18/0x1c)
> [ 0.673126] r6:c0591854 r5:00000000 r4:c065cf48 r3:c061fd48
> [ 0.679077] [<c03f7394>] (dump_stack+0x0/0x1c) from [<c03f75dc>]
> (panic+0x64/0x188)
> [ 0.687072] [<c03f7578>] (panic+0x0/0x188) from [<c0565c58>]
> (mount_block_root+0x178/0x22c)
> [ 0.695800] r3:cf01f800 r2:00000000 r1:cf81df48 r0:c04cd540
> [ 0.701721] r7:00008001
> [ 0.704376] [<c0565ae0>] (mount_block_root+0x0/0x22c) from [<c0565ee8>]
> (mount_root+0xf0/0x110)
> [ 0.713470] [<c0565df8>] (mount_root+0x0/0x110) from [<c0566070>]
> (prepare_namespace+0x168/0x1c0)
> [ 0.722747] r7:00000013 r6:c003f2e8 r5:c0591865 r4:c065bfa0
> [ 0.728668] [<c0565f08>] (prepare_namespace+0x0/0x1c0) from [<c05658c0>]
>
> (kernel_init+0xfc/0x12c)
> [ 0.737945] r5:c05fbe1c r4:c05fbe1c
> [ 0.741668] [<c05657c4>] (kernel_init+0x0/0x12c) from [<c003f2e8>]
> (do_exit+0x0/0x62c)
> [ 0.749938] r5:c05657c4 r4:00000000
>
> --
> For more options, visit http://beagleboard.org/discuss
>
>
>




ur uImage is currupted.prepare it with the fresh kernel.

[Gopal]

I got the same error when interfacing with a custom hardware on I2C-2 lines. But when you "reset" the board kernel boots normally. Try that...