Frederick Bruckman wrote:
> by hand. It had to be force loaded, with "-f", because there seems to
> be something wrong with the LKM versioning scheme: it complained that
> module is <some random word>, kernel is <some other random words>,

This means the LKM was compiled with different options than
kernel, and so the LKM is not compatible with running kernel.
Specifically, if the LKM isn't compiled with MULTIPROCESSOR,
it will crash kernel compiled with MULTIPROCESSOR.

You NEED to compile LKMs with exactly same options as kernel, such
as:

cd src/sys/lkm
make clean
DBG="-O2 -DMULTIPROCESSOR" make dependall
make install

FYI:
Do NOT use forced LKM load. It WILL make the kernel crash once the
LKM would do anything. I thought the message emitted by modload
with -f is discouraging enough. I guess I'd need to improve it
further :)

Jaromir

> when both should have been NetBSD-1.6ZC. I was able to run glxgears
> *really* *fast*. After I'd installed the second processor, the machine
> locked up before I could log in via xdm. Without the LKM, it's stable.
> Nevertheless, I intend to try again, and make a full report once
> things settle down. Erik, this is with a Matrox 550. I also have a
> Voodoo3 PCI card, and that module builds, too. Some of the other's
> didn't build at all with gcc-3.3.1. Erik's web page is still:
> 
>     http://www.canuck.com/~reide/netbsd/dri/
> 
> 
> Frederick
> 

-- 
Jaromir Dolecek <jdolecek@NetBSD.org>            http://www.NetBSD.cz/
-=- We should be mindful of the potential goal, but as the tantric    -=-
-=- Buddhist masters say, ``You may notice during meditation that you -=-
-=- sometimes levitate or glow.   Do not let this distract you.''     -=-