At 12:48 PM -0500 12/30/01, you wrote:

:)The exception you are getting is 0x200, machine check at address 0x2eb4a0.
:)According to gdb, this is in the uvm_km_kmemalloc routine.  It is likely
:)trying to access some invalid physical memory location while probing for
:)devices.  You might try poking around in ddb to find the trapframe for the
:)stack address, i'm not sure why trace isn't working at that point, but
:)it may be that memory translation is off or something.

Any suggestions how to do that?  All I know how to do in ddb is get a stack
trace and reboot.

:)If you can figure out which devices it is trying to probe, take them
:)out of the kernel and see if you can get enough devices working in
:)order to boot.  Then debug from there.

OK, I'll give it a shot.

Thanks for the suggestions,
  -- MW