Re: Early kernel debugging

2011-03-27 Thread Benjamin Herrenschmidt
On Sun, 2011-03-27 at 20:00 +0200, Philipp Ittershagen wrote: > On 03/25/2011 09:50 AM, Guillaume Dargaud wrote: > > Hello all, > > what can you do when the kernel you try to run stops before printing > > anything on the console ? > > http://elinux.org/Kernel_Debugging_Tips#Debugging_early_boot_p

Re: Early kernel debugging

2011-03-27 Thread Philipp Ittershagen
On 03/25/2011 09:50 AM, Guillaume Dargaud wrote: > Hello all, > what can you do when the kernel you try to run stops before printing anything > on the console ? http://elinux.org/Kernel_Debugging_Tips#Debugging_early_boot_problems Basically it means connecting a debugger to the running kernel (u

Re: early kernel debugging

2009-04-03 Thread Feng Kan
Hi: Did you try the early kernel printk option in kernel hacking. It can give some very helpful information. Make sure the address for the physical uart address is passed in correctly. Feng Tirumala Reddy Marri wrote: I am not sure if I understand correctly. But Looks like you are not pass

RE: early kernel debugging

2009-04-03 Thread Tirumala Reddy Marri
I am not sure if I understand correctly. But Looks like you are not passing the device tree along with kernel image and RAMDISK(you may not need it if you are using NFS mount). You boot command should some what look like this "bootm kernel_addr ramdisk_addr devtree_addr" or "bootm kernel_addr - de