[beagleboard] Kernel stops after changing debug port UART3 to UART1

I am working Omap3503 board, I took kernel source code from beagle board.org site and i changed debug port to from UART3 to UART1 for our board. after booting i am getting this result please let me know what will be the issue?

<6>cpuidle: using governor menu
cpuidle: using governor menu
<6>Waiting 1sec before mounting root device…
Waiting 1sec before mounting root device…
<4>mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: host does not support reading read-only switch. assuming write-enable.
<6>mmcblk0: mmc0:0007 SD02G 1955840KiB
mmcblk0: mmc0:0007 SD02G 1955840KiB
<6> mmcblk0: mmcblk0: p1 p1 p2 p2

<7>CEATA Card Not Found
<6>mmcblk1: mmc1:0001 MMC02G 1976320KiB
mmcblk1: mmc1:0001 MMC02G 1976320KiB
<6> mmcblk1: mmcblk1: p1 p1

List of all partitions:
List of all partitions:
1f00 512 mtdblock01f00 512 mtdblock0 (driver?)
(driver?)
1f01 1920 mtdblock11f01 1920 mtdblock1 (driver?)
(driver?)
1f02 128 mtdblock21f02 128 mtdblock2 (driver?)
(driver?)
1f03 5120 mtdblock31f03 5120 mtdblock3 (driver?)
(driver?)
1f04 254464 mtdblock41f04 254464 mtdblock4 (driver?)
(driver?)
b300 1955840 mmcblk0b300 1955840 mmcblk0 driver: mmcblk
driver: mmcblk
b301 401593 mmcblk0p1
b301 401593 mmcblk0p1
b302 1550272 mmcblk0p2
b302 1550272 mmcblk0p2
b308 1976320 mmcblk1b308 1976320 mmcblk1 driver: mmcblk
driver: mmcblk
b309 1976257 mmcblk1p1
b309 1976257 mmcblk1p1
No filesystem could mount root, tried: No filesystem could mount root, tried: ext2 ext2

<0>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1)

Where i have to set write protect GPIO pin.
i am using GPIO 62 for write protect pin.

–Sanjeev
|

It looks like the kernel simply isn’t finding a suitable root filesystem. Check the bootargs to see where its being pointed. You appear to have an mmcblk0p2 which is where most people put their rootfs. What are you using for the rootfs…?

The MMC read/write pin on the BeagleBoard Rev. C is (apparently) connected to GPIO29 but this shouldn’t matter as it ignores the MMC readonly state and assumes it can write. Linux can start to boot from a readonly rootfs just fine (its usually applications that fail) so that’s not the problem.

boot with ‘rootwait’ in your kernel cmdline

Op 25 jun 2009 om 16:58 heeft sanju More <sanjeev.m@inetfi.com> het volgende geschreven:\