hi Ken -
Hm, I don't think -any- .config file is supplied via CVS, although KDB
is set to be on in linux/arch/i386/defconfig.
KDB is generally a good thing to have on in a CVS kernel, I think,
because CVS is not expected to be super-stable, and may offer many
The latest -released- XFS version (1.1) did not have kdb enabled,
Frankly, if you're taking a CVS kernel & running it in a production
environment, without understanding the implications of the options that
are enabled, you are bound to have problems. :)
FWIW, you can also control kdb via /proc/sys/kernel/kdb
On Wed, 2002-07-24 at 10:20, Ken D'Ambrosio wrote:
> One thing I've noticed -- and feel free, guys, to correct me if I'm wrong,
> since I'm *not* a kernel hacker -- is that "Built-in Kernel Debugger
> support" is enabled by default, at least for the CVS copy I have. The
> problem here, I believe, is that if the system has an OOPS, instead of
> logging it to syslog and going on its way, it dumps you into the debugger.
> While this doesn't crash your system, per-se, it *does* make it unavailable
> until someone manually types "go" at the debug prompt. This can create big
> problems in a production environment (alas, I proved this myself last week).
> I've since re-compiled all my kernels to -not- have the debugger included,
> and all proceeds smoothly. Perhaps the debugger should _NOT_ be enabled by
> default in the .config file included with XFS' Linux kernel tree?
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc. 651-683-3102