"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.
