it is <esc>KDB now instead of ctrl-a.
scott -----Original Message----- From: Hasan Rashid [mailto:[EMAIL PROTECTED] Sent: Thu 7/17/2008 4:26 PM To: 'Keith Owens' Cc: Scott Lurndal; 'Jay Lan'; [email protected] Subject: RE: kdb has no working console and has switched itself off Keith, I replaced the boot arguments to (uart) what you see now. Kernel command line: auto BOOT_IMAGE=kiCkaSs ro root=301 console=ttyS0,19200n8 console=uart,io,0x3f8,19200n8 reboot=hard hdb=noprobe hdc=noprobe hdd=noprobe ide_setup: hdb=noprobe ide_setup: hdc=noprobe ide_setup: hdd=noprobe Initializing CPU#0 Early serial console at I/O port 0x3f8 (options '19200n8') kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights Reserved kdb_cmd[0]: defcmd archkdb "" "First line arch debugging" kdb_cmd[7]: defcmd archkdbcpu "" "archkdb with only tasks on cpus" kdb_cmd[14]: defcmd archkdbshort "" "archkdb with less detailed backtrace" kdb_cmd[21]: defcmd archkdbcommon "" "Common arch debugging" Kdb gets initialized and setup with early console detection. Now when I press CTRL+A nothing happens. How do I invoke kdb prompt? TIA! Regards, Hasan R. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Keith Owens > Sent: Thursday, July 17, 2008 2:48 PM > To: Hasan Rashid > Cc: 'Scott Lurndal'; 'Jay Lan'; [email protected] > Subject: Re: kdb has no working console and has switched itself off > > "Hasan Rashid" (on Thu, 17 Jul 2008 13:34:30 -0700) wrote: > >Scott, > > > >I compiled my kernel with the following: > > > ># Hardware I/O ports > ># > >CONFIG_SERIO=y > >CONFIG_SERIO_SERPORT=y > > > ># > ># Character devices > ># > ># CONFIG_VT is not set > ># CONFIG_SERIAL_NONSTANDARD is not set > > > ># > ># Serial drivers > ># > >CONFIG_SERIAL_8250=y > >CONFIG_SERIAL_8250_CONSOLE=y > >CONFIG_SERIAL_8250_PCI=y > >CONFIG_SERIAL_8250_NR_UARTS=1 > >CONFIG_SERIAL_8250_RUNTIME_UARTS=1 > ># CONFIG_SERIAL_8250_EXTENDED is not set > > > ># Non-8250 serial port support > ># > >CONFIG_SERIAL_CORE=y > >CONFIG_SERIAL_CORE_CONSOLE=y > >CONFIG_UNIX98_PTYS=y > >CONFIG_LEGACY_PTYS=y > >CONFIG_LEGACY_PTY_COUNT=256 > > > >> -----Original Message----- > >> From: Scott Lurndal [mailto:[EMAIL PROTECTED] > >> Sent: Thursday, July 17, 2008 1:06 PM > >> To: Hasan Rashid > >> Cc: 'Jay Lan'; [email protected] > >> Subject: Re: kdb has no working console and has switched itself off > >> > >> On Thu, Jul 17, 2008 at 12:47:32PM -0700, Hasan Rashid wrote: > >> > This is only with the 2.6.22.19 kernel. I have a similar device (WRAP > >> board) > >> > with the same setup, just a serial port connected to my computer and > KDB > >> > works just fine on that. > >> > > >> > .... > >> > ..... > >> > kdb: Initialization failed - no console. kdb is disabled. > >> > kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All > Rights > >> > >> Did you build your 2.6.22.19 with CONFIG_SERIAL_CONSOLE, > >> CONFIG_SERIAL_8250_CONSOLE or CONFIG_SERIAL_CORE_CONSOLE? > > Your serial console is not being detected early enough (or not at all). > You might need boot parameters console=ttyS0[,options] or > console=uart,io,<addr>[,options] to ensure that the serial console is > detected before kdb starts. See linux/Documentation/kernel- > parameters.txt. > There was a change to the kernel about a year ago to avoid probing > non-existent serial hardware. That change avoided errors on some > hardware, but unfortunately required extra boot parameters for early > console bringup. > > --------------------------- > Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
