From owner-freebsd-current  Sat May 17 18:27:33 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA23602
          for current-outgoing; Sat, 17 May 1997 18:27:33 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA23596
          for <freebsd-current@FreeBSD.ORG>; Sat, 17 May 1997 18:27:30 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id SAA28184; Sat, 17 May 1997 18:28:00 -0700 (PDT)
To: Gilbert Bollinger <gbolling@seidata.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: FreeBSD 3.0 current continue reboots. 
In-reply-to: Your message of "Sat, 17 May 1997 16:46:33 CDT."
             <337E2739.CBA7CDEA@seidata.com> 
Date: Sat, 17 May 1997 18:28:00 -0700
Message-ID: <28181.863918880@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I have a FreeBSD 3.0 current box. With dual P6 200 512k chips. We do not
> have SMP turned on, but the system reboots 6 or more times a day. We
> have a Adaptec 2940 SCSI controller, MGA Millinnium video card, 3COM
> fastlink card. I think it's the SCSI drivers since they have been

I have a system right here with almost that exact same configuration,
modulo the 3COM controller (this one has an SMC NIC).  It's a running
just great with -current, and Justin's driver has certainly been
working well for at least several weeks now - this sounds like something
else.

					Jordan