From owner-freebsd-current  Sat Aug  9 15:16:01 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA17430
          for current-outgoing; Sat, 9 Aug 1997 15:16:01 -0700 (PDT)
Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA17409
          for <current@FreeBSD.ORG>; Sat, 9 Aug 1997 15:15:50 -0700 (PDT)
Received: (from uucp@localhost)
	by abby.skypoint.net (8.8.5/alexis 2.7)  with UUCP id RAA00301; Sat, 9 Aug 1997 17:15:47 -0500 (CDT)
Received: (from bruce@localhost)
	by zuhause.mn.org (8.8.6/8.8.5) id QAA14184;
	Sat, 9 Aug 1997 16:23:28 -0500 (CDT)
Date: Sat, 9 Aug 1997 16:23:28 -0500 (CDT)
Message-Id: <199708092123.QAA14184@zuhause.mn.org>
From: Bruce Albrecht <bruce@zuhause.mn.org>
To: Thomas Dean <tomdean@celebris.tddhome>
Cc: current@FreeBSD.ORG
Subject: Re: Trap 9 When Boot SMP
In-Reply-To: <199708080342.UAA00262@celebris.tddhome>
References: <199708080342.UAA00262@celebris.tddhome>
X-Mailer: VM 6.30 under 19.15p2 XEmacs Lucid
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Thomas Dean writes:
 > I have been trying to get SMP running on my machine,
 > a Digital Equipment Corp. Celebris XL 5133DP.
 > 
 > I get a trap 9 when I try to run an SMP kernel.  I tried -current
 > and 3.0-970618-SNAP,  with similar results.

I'm also getting this error on a Tyan ATX 1668 MB.  Strangely enough,
I got this error when I first tried the SMP snap kernel from Jan/Feb,
and went away for a week or so when SMP was integrated into -current,
and I've been unable to boot SMP since.  Steve Passe suggested that it
might be hardware, since I've also been having problems with my memory
getting parity error faults, but I sent it back to the company I
bought it from, and they replaced the memory (still getting parity
error faults, so I've got to do something about that again), and also
the motherboard because it was damaged during shipping (don't ask, it
took FedEx a month to deal with the claim).  It looks like it's dying
when sending the message saying the CPU is online, so I was thinking
of switching to the other console driver to see if it makes any
difference.  My machine runing SMP Windows/NT just fine.  I don't have
enough disk to try Linux SMP, though.