[android-kernel] Re: get stuck in /init/main.c

2011-03-28 Thread tstanly
hi all, my original kernel command is: console=ttyO2,115200n8 rootdelay=1 init=/init root=/dev/mmcblk0p2 rw omapfb.vram="0:4M" and finally I add *androidboot* in the command become: androidboot.console=ttyO2,115200n8 console=ttyO2,115200n8 rootdelay=1 init=/init root=/dev/mmcblk0p2 rw omapfb.vram=

Re: [android-kernel] Re: get stuck in /init/main.c

2011-03-23 Thread Ravi Chemudugunta
what's your kernel command line? check that it includes a console= clause. -ravi -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel

[android-kernel] Re: get stuck in /init/main.c

2011-03-23 Thread Srikant
Mark means you've commented that part of the code. With that you may not get the console prompt. On Mar 23, 9:04 pm, tstanly wrote: > hi Srikant, > > thanks for your reply, > I tried to mark this code, and it pass to continue, > but stuck in executing /init, > so is it possible have side effect

[android-kernel] Re: get stuck in /init/main.c

2011-03-23 Thread tstanly
hi Srikant, thanks for your reply, I tried to mark this code, and it pass to continue, but stuck in executing /init, so is it possible have side effect that I mark this? my board is OMAP3630 thanks ! On 3月23日, 下午1時25分, Srikant wrote: > That means it is trying to open UART driver, you need to d

[android-kernel] Re: get stuck in /init/main.c

2011-03-22 Thread Srikant
That means it is trying to open UART driver, you need to debug the UART driver with putting some prints. The reason for the hang may be some feature/function of UART doesn't support. Which board are you using? On Mar 21, 12:33 pm, stanly wrote: > hi all, > > when my kernel booting, > it will be