From owner-freebsd-questions Tue Aug 19 15:08:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA09120 for questions-outgoing; Tue, 19 Aug 1997 15:08:33 -0700 (PDT) Received: from rainey.blueneptune.com (root@rainey.blueneptune.com [207.104.147.238]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA09106; Tue, 19 Aug 1997 15:08:28 -0700 (PDT) From: michael@blueneptune.com Received: (from michael@localhost) by rainey.blueneptune.com (8.6.12/8.6.12) id PAA21215; Tue, 19 Aug 1997 15:13:22 -0700 Message-Id: <199708192213.PAA21215@rainey.blueneptune.com> Subject: Re: Is there still problems with Adaptec UW controllers (fwd) To: dan@dpcsys.com (Dan Busarow) Date: Tue, 19 Aug 1997 15:13:22 -0700 (PDT) Cc: mheath@netspace.net.au, freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG In-Reply-To: from "Dan Busarow" at Aug 19, 97 10:11:48 am Reply-To: michael@blueneptune.com X-Mailer: ELM [version 2.4 PL24 ME8b] Content-Type: text Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Here are some more details about our particular case of having problems with FreeBSD and (apparently) the Adaptec UW controller: Hardware configuration: CPU: AMD K6 CPU Motherboard: ASUS XP55T2P4 ATX w/512K cache PCI Chipset: Intel's 430 HX Memory: 64 MB SCSI Controller: Adaptec 2940UW Disk: Seagate ST34371W The system was running the latest version of INN. There were numerous log messages indicating a SCSI bus timeout. Then the system would hang. This is apparently consistent with earlier reports of the problems with the Adaptec controllers. The problem was seen on 2.2.2-RELEASE, and on an early August engineering release. (I don't have the exact date available.) Backing off to FreeBSD 2.1.7 solved the problem --- the system has been up for over a week now, whereas before it was crashing after very little uptime. We no longer have the detailed log information, and obviously won't be able to get it with the system running 2.1.7. [Yeah, I know, we should have saved the logged info. Sorry about that.] -- Michael Bryan michael@blueneptune.com