> cpu1: starting
> cpu1: prelint0 10000<vector=0,delmode=0,masked,dest=0> 0<target=0>
> cpu1: prelint1 10000<vector=0,delmode=0,masked,dest=0> 0<target=0>
> cpu1: timer0 10000<vector=0,delmode=0,masked,dest=0> 0<target=0>
> cpu1: pcint0 10000<vector=0,delmode=0,masked,dest=0> 0<target=0>
> cpu1: lint0 10700<vector=0,delmode=7,masked,dest=0> 0<target=0>
> cpu1: lint1 400<vector=0,delmode=4,dest=0> 0<target=0>
> cpu1: err0 10000<vector=0,delmode=0,masked,dest=0> 0<target=0>
> cpu1: CPU 0 running

Looks to me like you have both CPU's going; if you look further back
in the dmesg, you'll see that cpu0 is at apic id 1, and cpu1 is at
apic id 0.

> (every other SMP dmesg I've seen posted has a "cpu1: CPU 1 running"
> message)

It seems to be fairly common for pentium-pro-era systems to come up on
CPU 1 rather than CPU 0; autoconf assigns device names based on the
order the devices were detected, rather than based on the underlying
hardware address..

> % /sbin/sysctl hw.ncpu
> hw.ncpu = 1

This sysctl isn't wired up to anything "real" yet.

> I tried getting top to run to show me what processes were running, but
> I get a "sysctl vm.uvmexp failed: Cannot allocate memory" message...i
> havent' really chased that down much.  Lack of sleep is catching up
> with me.

Someone resized "struct uvmexp" by adding a new counter to the middle,
which broke backwards-compat with the 1.5 version of "top"; you need
to rebuild top against the -current system headers.

					- Bill