In my attempt at porting kdb 1.5 to 2.2.16, I also ran into trouble
with "go" from kdb. Except in my case the system paniced and there
was some evidence of corruption. I now have prints on entry and
exit to kdb_setjmp() and kdb_longjmp() and the problem magically
disappeared. It is also suspicious that the static strings in the
prints seem to get corrupted. Don't know if this is related.
You might try to get into the debugger a second time, either with
Ctrl-A or a break point or trap keyed off of commands from a network
session. Then review the ps and see if you can identify the thread(s)
that is(are) stuck.
Alan
> Hi all,
> After kdb session is over. my keyboard gets locked, tough linux kept
> running, i am able to reboot the system via network.
> To come out of kdb i use go command. I am running 2.4test10 kernel with
> p3/I815 motherboard.
> Can anybody provide some help in restoring the keyboard without rebooting
> the system,
> thanks,
> Anil
> Note: Please CC the answer
>
