Passing kdb=early or not does not make a difference. The control is not passed to kdb during the boot process. Anyway, after the system is completely up and running, I press the 'pause' key, kdb prints out a nice backtrace and its prompt, after that it does not accept any keyboard input.
Ronghua On Jan 13, 2008 6:10 PM, Onkar <[EMAIL PROTECTED]> wrote: > did you pass kdb=early to the boot option ? > > Onkar > > > > On Jan 14, 2008 2:00 AM, Ronghua Zhang <[EMAIL PROTECTED]> wrote: > > > > > > > > I applied kdb-4.4-2.6.20-common-6 and kdb-4.4-2.6.20-x86_64-3 patches > > against vanilla 2.6.20 kernel on a 64-bit machine. The patches applied > > cleanly. After I pressed the Pause key, the system did trap into kdb, > > but kdb didn't accept any keyboard input. Is it a known issue? The > > only thing special in my setup is that I ran the 64-bit kernel inside > > a VM? In case it's related to some config options, the config file is > > attached. Any help is appreciated! > > Thanks, > > Ronghua > > > > > > -- Binary/unsupported file stripped by Ecartis -- > > -- Type: application/octet-stream > > -- File: config > > > > > > --------------------------- > > 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.
