On 03/02/2011 06:47 PM, Somebody in the thread at some point said:
Hi Jeremy -
Actually I didn't mean to enable EARLY_PRINTK in .config. Actually
I only used the android_omap3_defconfig, and I found I can not see the
terminal messages so I tried to enable EARLY_PRINTK to see if there're
any suspicious.
The last line I can see is:
Uncompressing Linux... done, booting the kernel.
Any clue on this for me?
To debug this you do want EARLY_PRINTK enabled in your .config, and add
this kernel commandline:
earlyprintk=1 earlycon=ttyO2,115200n81 loglevel=8
Without EARLY_PRINTK, nothing comes on the console until the console
device is initialized, until then all the log info is buffered in memory
and it's all dumped out at that point. So, if you blow an OOPS early in
boot, before the console stuff is initialized, you won't hear anything
about it.
With EARLY_PRINTK, every log message is printed to serial synchronously,
so you can hear about your problem if the problem produced any log
footprint, or at least get a clue about how far through the init process
you got before the black smoke comes ^^
-Andy
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
