Failed to enter KDB on terminal program via key sequence "Ctrl-A"
yukun.chen at intel.com
Tue Nov 2 18:14:36 PST 2004
I use SLES9 SP1. I have tried the method u mentioned but it still dose not work. I think it might be a bug of suse distribution and I will report them it.
Thanx a lot for your help:)
From: Keith Owens [mailto:kaos at sgi.com]
Sent: 2004Äê11ÔÂ2ÈÕ 19:28
To: Chen, Yukun
Cc: kdb at oss.sgi.com
Subject: Re: Failed to enter KDB on terminal program via key sequence "Ctrl-A"
On Tue, 2 Nov 2004 17:38:42 +0800,
"Chen, Yukun" <yukun.chen at intel.com> wrote:
> 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?
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
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
More information about the kdb