Hi,

and thanks for the console output.  Two comments:

 o The "cpu<n>: processor failed to hatch" comes from an attempt at
   starting the secondary CPUs spinning; see cpu_boot_secondary() in
   sys/arch/alpha/alpha/cpu.c.  I do not have any definitive idea why
   this would happen -- sorry.  I think that as a first try I would
   try multiplying the time-out with 10, but that's probably not going
   anywhere useful.

   The kernel should already be waiting for 10 seconds for each CPU
   for it to spin up.  Does that match what you see on the console
   while it's doing that part of the autoconfiguration?

 o the kernel panic you get is in ltsleep(), and seems to indicate
   that a sleep is done outside of a process context, i.e. curlwp is
   NULL.  It would be interesting to see a stack backtrace to see
   where this happens.  I'm not sure if this is actually related to
   the machine running with multiple physical CPUs (but failed to
   initialize the secondary CPUs).
   =

Regards,

- H=E5vard