Hi 

It looks with the bootloader param's passed to Kernel in the "ATAG_CMDLINE: 
3d 54410009 ': loglevel=8 console=ram " is configured with 'console=ram'. 

Try changing console to a valid serial port (tty). 

Anirudh

On Wednesday, June 5, 2013 2:41:43 PM UTC+5:30, Dilshad Alam wrote:
>
> Hi, 
> I am porting Linux kernel 3.9.0 to my device which is having android 4.1 & 
> kernel 3.0.3.
>
> With android kernel 3.0.3, it is booting properly. But after flashing my 
> build kernel 3.9.0, I am not seeing any initial kernel logs i.e 
> "Uncompressing Kernel.. Booting is done".
>
> We have verified machine ID & zreladdr etc. passed from bootloader and 
> configured in kernel are same. Please help me if someone knows how to solve 
> this problem.
> If any assistance provided in debugging arch/arm/bootp compressed folder, 
> It would be great help.
>
>
> --------------------------------------------------------------------------------------------------
>
> serial log with Linux 3.0.3
>
> -----------------------------
>
> ......ATAG_CORE: 5 54410001 0 0 0
>
> MEMCONFIG: 20e01323 20e01323
>
> ATAG_MEM: 4 54410002 10000000 40000000
>
> ATAG_MEM: 4 54410002 10000000 50000000
>
> ATAG_MEM: 4 54410002 10000000 60000000
>
> ATAG_MEM: 4 54410002 10000000 70000000
>
> ATAG_SERIAL: 4 54410006 175d762f 464119ec
>
> ATAG_REVISION: 3 54410007 c
>
> ATAG_CMDLINE: 3d 54410009 ': loglevel=8 console=ram sec_debug.enable=0 
> sec_debug.enable_user=0 c1_watchdog.sec_pet=5
>
> sec_log=0x200000@0x5ea00000 s3cfb.bootloaderfb=0x5ec00000 
> ld9040.get_lcdtype=0x0 consoleblank=0 lpj=3981312 vmalloc=144m 
> console=ttySAC2,115200'
>
> ATAG_NONE: 0 0
>
> Starting kernel at 0x40008000...
>
> Uncompressing Linux... done, booting the kernel.
>
> [ 0.000000] Initializing cgroup subsys cpu
>
> [ 0.000000] Linux version 3.0.31-1014481-eng 
> (*se.infra@SEP-112*<javascript:>) 
> (gcc version 4.4.3 (GCC) ) #3 SMP PREEMPT Fri Mar 1 06:19:36 KST 2013
>
> [ 0.000000] CPU: ARMv7 Processor [412fc091] revision 1 (ARMv7), cr=10c5387d
>
> [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction 
> cache
>
> [ 0.000000] Machine: SMDK4210 
>
> .................
>
> .................
>
>
> --------------------------------------------------------------------------------------------------
>
> serial log with Linux 3.9.0
>
> ---------------------------
>
> ATAG_CORE: 5 54410001 0 0 0
>
> MEMCONFIG: 20e01323 20e01323
>
> ATAG_MEM: 4 54410002 10000000 40000000
>
> ATAG_MEM: 4 54410002 10000000 50000000
>
> ATAG_MEM: 4 54410002 10000000 60000000
>
> ATAG_MEM: 4 54410002 10000000 70000000
>
> ATAG_SERIAL: 4 54410006 175d762f 464119ec
>
> ATAG_REVISION: 3 54410007 c
>
> ATAG_CMDLINE: 3d 54410009 ': loglevel=8 console=ram sec_debug.enable=0 
> sec_debug.enable_user=0 c1_watchdog.sec_pet=5
>
> sec_log=0x200000@0x5ea00000 s3cfb.bootloaderfb=0x5ec00000 
> ld9040.get_lcdtype=0x0 consoleblank=0 lpj=3981312 vmalloc=144m 
> console=ttySAC2,115200'
>
> ATAG_NONE: 0 0
>
> Starting kernel at 0x40008000... *(Last Bootloader logs)*
>
> *<<<<No log coming after this>>*
>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Thanks,
> Dilshad
>

-- 
-- 
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
--- 
You received this message because you are subscribed to the Google Groups 
"Android Linux Kernel Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-kernel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to