| To: | "Bruce Edge" <bedge@xxxxxxxxxxxxxxxxxx>, <lkcd-general@xxxxxxxxxxxxxxxxxxxxx>, <kdb@xxxxxxxxxxx> |
|---|---|
| Subject: | RE: [lkcd-general] This kernel supports KDB but LKCD was invoked directly, not via KDB.... |
| From: | "Jeff Haran" <jharan@xxxxxxxxxxx> |
| Date: | Mon, 15 Dec 2003 16:55:53 -0800 |
| Sender: | kdb-bounce@xxxxxxxxxxx |
| Thread-index: | AcPDYEiwaGq/CFtoSRyiw8QzWfsGPgAB379wAAFUm9AAAGmckA== |
| Thread-topic: | [lkcd-general] This kernel supports KDB but LKCD was invoked directly, not via KDB.... |
> -----Original Message----- > From: Bruce Edge [mailto:bedge@xxxxxxxxxxxxxxxxxx] > Sent: Monday, December 15, 2003 4:41 PM > To: lkcd-general@xxxxxxxxxxxxxxxxxxxxx; kdb@xxxxxxxxxxx > Subject: FW: [lkcd-general] This kernel supports KDB but LKCD was > invoked directly, not via KDB.... > ... > > I cannot try using a sysrq-c, as the console is a serial port. > FYI... Some kernels can be configured to interpret an RS-232 break condition as a sysrq key. I don't remember the name of the pertinent configuration variable. Then all you have to do is figure out how to make your terminal emulation program generate a break and you can generate sysrq-c thru a serial port. Jeff Haran Brocade Communications Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: FW: [lkcd-general] This kernel supports KDB but LKCD was invoked directly, not via KDB...., Keith Owens |
|---|---|
| Next by Date: | RE: FW: [lkcd-general] This kernel supports KDB but LKCD was invoked directly, not via KDB...., Bruce Edge |
| Previous by Thread: | Re: FW: [lkcd-general] This kernel supports KDB but LKCD was invoked directly, not via KDB...., Keith Owens |
| Next by Thread: | RE: FW: [lkcd-general] This kernel supports KDB but LKCD was invoked directly, not via KDB...., Bruce Edge |
| Indexes: | [Date] [Thread] [Top] [All Lists] |