Public bug reported:
The kernel built from the scripts at
https://code.launchpad.net/~beagleboard-kernel/+junk/2.6.35-devel
fails to mount the root directory from the mmc its booting off, although
it's detecting the mmc just fine and the ext3 support is enabled in the
kernel. This is happening on a revB7 board.
1.972015] Waiting for root device /dev/mmcblk0p2...
[ 2.192993] usb 2-1: new low speed USB device using musb_hdrc and address 2
[ 2.333587] mmc0: new high speed SDHC card at address 0007
[ 2.339630] mmcblk0: mmc0:0007 SD04G 3.73 GiB (ro)
[ 2.344787] mmcblk0: p1 p2 p3
[ 2.355194] usb 2-1: device v046d pc00e is not supported
[ 2.412048] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)
[ 2.419128] Please append a correct "root=" boot option; here are the
available partitions:
[ 2.427612] 1f00 512 mtdblock0 (driver?)
[ 2.432617] 1f01 1920 mtdblock1 (driver?)
[ 2.437683] 1f02 128 mtdblock2 (driver?)
[ 2.442687] 1f03 4096 mtdblock3 (driver?)
[ 2.447753] 1f04 255488 mtdblock4 (driver?)
[ 2.452819] b300 3911680 mmcblk0 driver: mmcblk
[ 2.458068] b301 40131 mmcblk0p1
[ 2.462432] b302 3365617 mmcblk0p2
[ 2.466796] b303 498015 mmcblk0p3
[ 2.471099] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(179,2)
[ 2.479675] [<c004a5d0>] (unwind_backtrace+0x0/0xf8) from [<c0550618>]
(panic+0x6c/0xf0)
[ 2.487854] [<c0550618>] (panic+0x6c/0xf0) from [<c0009194>]
(mount_block_root+0x188/0x230)
[ 2.496307] [<c0009194>] (mount_block_root+0x188/0x230) from [<c0009484>]
(prepare_namespace+0x140/0x1d4)
[ 2.506011] [<c0009484>] (prepare_namespace+0x140/0x1d4) from [<c00086a0>]
(kernel_init+0x13c/0x164)
[ 2.515258] [<c00086a0>] (kernel_init+0x13c/0x164) from [<c0045518>]
(kernel_thread_exit+0x0/0x8)
The very same setup with a kernel built from
https://code.launchpad.net/~beagleboard-kernel/+junk/2.6-stable
works just fine.
** Affects: linux-ti-omap (Ubuntu)
Importance: Undecided
Status: New
--
2.6.35-devel is unable to mount root on mmc
https://bugs.launchpad.net/bugs/607906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
