On 07/29/2015 08:45 AM, נעמה ממן wrote:
> Hello,
>
>
>
> cross compiled raspberry pi kernel using an Ubuntu virtual machine.
>
> Using this configurations:
>
>
>
> CONFIG_DEBUG_INFO=y
>
> CONFIG_MAGIC_SYSRQ=y
> CONFIG_FRAME_POINTER=y
> CONFIG_KGDB=y
> CONFIG_KGDB_SERIAL_CONSOLE=y
>
> CONFIG_KGDB_KDB=y
> CONFIG_KDB_KEYBOARD=y
>
> The pc is connected to RPI by UART.
>
> Want to debug the raspberry pi kernel with kdb&kgdb.
>
>
>
> using the minicom (in vm host) to send the break signal (alt+a ,f(send
> break) ,g(Go)) kdb&kgdb is working as expected
>
> when trying to use echo g > /proc/sysrq-trigger get the message :
>
> Entering kdb (current=0xc054ca80, pid 0) due to Keyboard Entry
>
> kdb>_
>
> kdb stuck and doesn’t response to keyboard, so i cant enter kgdb :/
>
> Do you have any suggestion why?

I have seem problems like this in the past and it is usually the case that the 
UART polling hooks are not written properly, or that the kernel is blocked on a 
lock, somewhere.  Considering that you made it to the KDB prompt with no 
critical printks, I would suspect the UART driver is probably the issue.

Jason.

------------------------------------------------------------------------------
_______________________________________________
Kgdb-bugreport mailing list
Kgdb-bugreport@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

Reply via email to