[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?

1871996 bytes read
## Booting kernel from Legacy Image at 80000000 …
Image Name: Linux-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1871932 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum … OK
Loading Kernel Image … OK

Starting kernel …

Uncompressing Linux… d
one, booting the kernel.
<5>Linux version (root@INETFI-LINUX-MC4) (gcc version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-51)) #2 Thu Jun 25 14:21:43 I
ST 2009
CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=00c5387f
Machine: OMAP3 Beagle board
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 32768
<7> DMA zone: 256 pages used for memmap
<7> DMA zone: 0 pages reserved
<7> DMA zone: 32512 pages, LIFO batch:7
<7> Normal zone: 0 pages used for memmap
<6>SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
CPU0: D VIPT write-through cache
CPU0: cache: 768 bytes, associativity 1, 8 byte lines, 64 sets
Built 1 zonelists. Total pages: 32512
<5>Kernel command line: console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p1 rootfstype=ext2 rw rootdelay=1 nohz=off
<6>GPMC revision 5.0
<6>IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
<6>Total of 96 interrupts on 1 active controller
<6>OMAP34xx GPIO hardware version 2.5
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
<6>Memory: 128MB 0MB = 128MB total
<5>Memory: 125696KB available (3528K code, 441K data, 132K init)
<7>Calibrating delay loop… 499.92 BogoMIPS (lpj=1949696)
Mount-cache hash table entries: 512
<6>CPU: Testing write buffer coherency: ok
<6>NET: Registered protocol family 16
<3>twl4030: I2C Client[3] is not initialized[515]
<3>twl4030: I2C Client[3] is not initialized[464]
<6>SmartReflex driver initialized
<6>OMAP DMA hardware revision 4.0
<6>OMAP Display hardware version 2.0
<6>i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
<6>i2c_omap i2c_omap.2: bus 2 rev3.12 at 100 kHz
<6>i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
<6>TWL4030: TRY attach Slave TWL4030-ID0 on Adapter OMAP I2C adapter [1]
<6>TWL4030: TRY attach Slave TWL4030-ID1 on Adapter OMAP I2C adapter [1]
<6>TWL4030: TRY attach Slave TWL4030-ID2 on Adapter OMAP I2C adapter [1]
<6>TWL4030: TRY attach Slave TWL4030-ID3 on Adapter OMAP I2C adapter [1]
<6>TWL4030 Power Companion Active
<6><6>TWL4030: Driver registration complete.
<6>TWL4030 GPIO Demux: IRQ Range 376 to 386, Initialization Success
<6>Initialized TWL4030 USB module<5>SCSI subsystem initialized
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>musb_hdrc: version 2.2a/db-0.5.2, pio, otg (peripheral+host), debug=0
<7>musb_hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine (X), bulk split (X), HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)
<7>musb_hdrc: MHDRC RTL version 1.400
<7>musb_hdrc: setup fifo_mode 4
<7>musb_hdrc: 29/31 max ep, 15424/16384 memory
<7>musb_hdrc: hw_ep 0shared, max 64
<7>musb_hdrc: hw_ep 1tx, max 512
<7>musb_hdrc: hw_ep 1rx, max 512
<7>musb_hdrc: hw_ep 2tx, max 512
<7>musb_hdrc: hw_ep 2rx, max 512
<7>musb_hdrc: hw_ep 3tx, max 512
<7>musb_hdrc: hw_ep 3rx, max 512
<7>musb_hdrc: hw_ep 4tx, max 512
<7>musb_hdrc: hw_ep 4rx, max 512
<7>musb_hdrc: hw_ep 5tx, max 512
<7>musb_hdrc: hw_ep 5rx, max 512
<7>musb_hdrc: hw_ep 6tx, max 512
<7>musb_hdrc: hw_ep 6rx, max 512
<7>musb_hdrc: hw_ep 7tx, max 512
<7>musb_hdrc: hw_ep 7rx, max 512
<7>musb_hdrc: hw_ep 8tx, max 512
<7>musb_hdrc: hw_ep 8rx, max 512
<7>musb_hdrc: hw_ep 9tx, max 512
<7>musb_hdrc: hw_ep 9rx, max 512
<7>musb_hdrc: hw_ep 10tx, max 512
<7>musb_hdrc: hw_ep 10rx, max 512
<7>musb_hdrc: hw_ep 11tx, max 512
<7>musb_hdrc: hw_ep 11rx, max 512
<7>musb_hdrc: hw_ep 12tx, max 512
<7>musb_hdrc: hw_ep 12rx, max 512
<7>musb_hdrc: hw_ep 13tx, max 512
<7>musb_hdrc: hw_ep 13rx, max 512
<7>musb_hdrc: hw_ep 14shared, max 1024
<7>musb_hdrc: hw_ep 15shared, max 1024
<6>musb_hdrc: USB OTG mode controller at c8800000 using PIO, IRQ 92
<6>Time: 32k_counter clocksource has been installed.
<6>Switched to high resolution mode on CPU 0
<6>NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
<6>TCP: Hash tables configured (established 4096 bind 4096)
<6>TCP reno registered
<3>Power Management for TI OMAP.
<6>cpuidle: using driver omap3_idle
<3>create_proc_entry succeeded
<3>create_proc_entry succeeded
<4>NetWinder Floating Point Emulator V0.97 (double precision)
<5>VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
<6>JFFS2 version 2.2. (NAND) �թ 2001-2006 Red Hat, Inc.
<6>io scheduler noop registered
<6>io scheduler anticipatory registered (default)
<6>io scheduler deadline registered
<6>io scheduler cfq registered
<7>omap2_disp_outLCD panel 1024x768
<4>timeout waiting for frame-done interrupt
<7>omap2_disp_outTV 640x480 interlaced
<6>omap24xxfb: Options “”
Console: switching to colour frame buffer device 128x48
<6>omap24xxfb: fb0 frame buffer device
<6>omap24xxfb: display mode 1024x768x16 hsync 22kHz vsync 28Hz<6>omap_rng omap_rng: OMAP Random Number Generator ver. 70
<6>OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
<6>Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
<6>serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
<��� |

It looks like your console is disappearing off to the video out… You could try changing the bootargs so that the console is ttyS0 rather than ttyS2…

I don’t know what is on your rootfs, but for a while I had my console output disappearing to the video out (which wasn’t attached to anything)… fsck can kick in causing boots to appear to hang for a while or if you are using an Angstrom demo image then the initial boot setup can take several minutes to configure packages…