Re: Asking for path to modules (was: How do I keep testing current-amd64 witout so much trouble?)

[Andrew Doran <ad%netbsd.org@localhost>]

On Fri, Dec 26, 2008 at 10:17:49AM -0500, Christos Zoulas wrote:

> I don't know. but I think that the simplest solution for LOCKDEBUG
> kernels is to avoid the issue by not allowing spinouts while we
> are sleeping for input, using a global variable. It is ugly, but I
> don't have a better idea right now.

I pointed out in a seperate forum that kernel_lock should no longer be
required in this path. Removing the KERNEL_LOCK() call in init_main.c
should solve the problem.

Thanks,
Andrew