kdb
[Top] [All Lists]

Re: Failed to enter KDB on terminal program via key sequence "Ctrl-A"

To: "Chen, Yukun" <yukun.chen@xxxxxxxxx>
Subject: Re: Failed to enter KDB on terminal program via key sequence "Ctrl-A"
From: Keith Owens <kaos@xxxxxxx>
Date: Tue, 02 Nov 2004 22:28:08 +1100
Cc: kdb@xxxxxxxxxxx
In-reply-to: Your message of "Tue, 02 Nov 2004 17:38:42 +0800." <16A54BF5D6E14E4D916CE26C9AD3057574602C@pdsmsx402.ccr.corp.intel.com>
Sender: kdb-bounce@xxxxxxxxxxx
On Tue, 2 Nov 2004 17:38:42 +0800, 
"Chen, Yukun" <yukun.chen@xxxxxxxxx> wrote:
>Hi all
>       I failed to switch to kdb environment in terminal program
>(minicom in Linux or HyperTerminal in Windows) via "Ctrl-A". 
>       On host machine, I can enter kdb environment via "Pause" (which
>will cause the kdb screen appears on terminal machine, it is OK). But
>failed to do so on terminal machine via "Ctrl-A"(no responses).
>       My environment is Suse sles 9 , kernel 2.6.5.
>       Anybody has ever meet such issue?
>       Thanx.

As a general rule, you should direct questions about distribution
specific patches to the distribution, not to this list.  Mainly because
distributions make their own changes.  But I'm in a good mood so ...

Which version of SuSE SLES 9?  SLES9 base has kdb v4.3, and SuSE
changed the KDB serial entry sequence from control-A to startKDB, but
only for the powerpc build.  SLES9 SP1 has kdb v4.4, which uses
escape-KDB as the entry sequence.  There is a message early in boot
that says which version of kdb you are using.

Watch out for minicom, it uses control-A as its own sequence.  To send
control-A to the kernel over minicom, you have to press it twice.
Which is one of the reasons that the sequence changed from kdb v4.3 to
v4.4.

---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
<Prev in Thread] Current Thread [Next in Thread>