From owner-freebsd-smp  Wed Dec  4 05:18:04 1996
Return-Path: owner-smp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id FAA29018
          for smp-outgoing; Wed, 4 Dec 1996 05:18:04 -0800 (PST)
Received: from spinner.DIALix.COM (root@spinner.DIALix.COM [192.203.228.67])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA28979
          for <smp@freebsd.org>; Wed, 4 Dec 1996 05:17:59 -0800 (PST)
Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1])
          by spinner.DIALix.COM (8.8.4/8.8.4) with ESMTP id VAA00740;
          Wed, 4 Dec 1996 21:16:39 +0800 (WST)
Message-Id: <199612041316.VAA00740@spinner.DIALix.COM>
To: Terje Normann Marthinussen <Terje.N.Marthinussen@cc.uit.no>
cc: smp@freebsd.org
Subject: Re: Crashing on activating other CPUs 
In-reply-to: Your message of "Wed, 04 Dec 1996 13:35:40 +0100."
             <199612041235.NAA00889@slibo.cc.uit.no> 
Date: Wed, 04 Dec 1996 21:16:39 +0800
From: Peter Wemm <peter@spinner.dialix.com>
Sender: owner-smp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Terje Normann Marthinussen wrote:
> >...and full dump messages run by before it freezes solid (and a reset is
> >necessary).  No variation on SMP_INVLTLB or APIC_IO seems to change the
> >above behavior.
> 
> Our 4 CPU Netserver works without SMP_INVLTLB and APIC_IO (the latter
> has never worked). With SMP_INVLTLB, I get something similar the
> moment I do "sysctl -w kern.smp_active=2".
> 
> SMP: AP CPU #1 LAUNCHED!!  Starting Scheduling...
> cpunumber = 0
> instruction pointer     = 0x8:0xf01b632d
                          ^^^^^^^^^^^^^^^^
> stack pointer           = 0x10:0xefbfffa4
> frame pointer           = 0x10:0xefbfd5e8
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, def32 1, gran 1
> processor eflags        = interrupt enabled, IOPL = 0
> current process         = 149 (sshd@386freebsd2)
> interrupt mask          = 
> panic (cpu#0): unknown/reserved trap
> boot() called on cpu#0
> 
> syncing disks... 5 5 2 done
> Automatic reboot in 15 seconds - press a key on the console to abort
> 
> 
> Terje Marthinussen
> terjem@cc.uit.no

Hmm, you have all 4 cpu's enabled?  Steve sounds like he's figured out
why the >2 cpu startup code (presently disabled) causes problems.  We
do not support >2 cpu's at the moment.  ("do not support" == "known to
not work" in this case).  We are close, but still not quite there.

Can you please try two things..

First, where is 0xf01b632d ?  Can you please do this:
# nm /kernel.whatever | sort | more
and search for the the 3 surrounding function names?

Second, can you please compile with "options DDB" and when it does this,
do a "trace" command and record the output.

Cheers,
-Peter