From owner-freebsd-smp  Thu Oct 30 16:41:21 1997
Return-Path: <owner-freebsd-smp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA24882
          for smp-outgoing; Thu, 30 Oct 1997 16:41:21 -0800 (PST)
          (envelope-from owner-freebsd-smp)
Received: from celebris.tddhome (sil-wa2-10.ix.netcom.com [206.214.137.42])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA24877
          for <freebsd-smp@FreeBSD.ORG>; Thu, 30 Oct 1997 16:41:18 -0800 (PST)
          (envelope-from tomdean@celebris.tddhome)
Received: (from tomdean@localhost)
	by celebris.tddhome (8.8.7/8.8.5) id QAA00662;
	Thu, 30 Oct 1997 16:41:05 -0800 (PST)
Date: Thu, 30 Oct 1997 16:41:05 -0800 (PST)
Message-Id: <199710310041.QAA00662@celebris.tddhome>
From: Thomas Dean <tomdean@ix.netcom.com>
To: joe@via.net
CC: freebsd-smp@freebsd.org
In-reply-to: <199710302326.PAA29117@monk.via.net> (message from Joe McGuckin
	on Thu, 30 Oct 1997 15:26:55 -0800)
Subject: Re: What's the state of SMP? Usable ?
Sender: owner-freebsd-smp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Great job by teh SMP folks.

I have been running SMP without a problem on a DEC Celebris XL 5133DP.
I have not had a crash since I compiled the last kernel.  Before that,
I had several problems, but, -current is just that, a growing thing.
I would pick a working -current and be careful about updates.

If your application is critical, -current is not for that.

# uname -a

FreeBSD celebris 3.0-CURRENT FreeBSD 3.0-CURRENT #2: Mon Aug 25
13:27:44 PDT 1997 root@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386

The machine is not a server, but, it is stable!