From owner-freebsd-isp Fri Nov 28 10:50:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA00628 for isp-outgoing; Fri, 28 Nov 1997 10:50:55 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA00623 for ; Fri, 28 Nov 1997 10:50:47 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id KAA18707; Fri, 28 Nov 1997 10:53:24 -0800 (PST) Message-Id: <199711281853.KAA18707@implode.root.com> To: Cliff Addy cc: Jeff Lynch , freebsd-isp@FreeBSD.ORG Subject: Re: Adaptec 2940 and FreeBSD 2.2.2-RELEASE In-reply-to: Your message of "Fri, 28 Nov 1997 11:08:35 EST." From: David Greenman Reply-To: dg@root.com Date: Fri, 28 Nov 1997 10:53:24 -0800 Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >On Fri, 28 Nov 1997, Jeff Lynch wrote: > >> The only problems I've had with 2940UWs on fbsd2.1.5-2.2.1 have occurred >> when we mix wide/narrow devices on the host adapter or attach a narrow >> (of course) external tape drive. Leaving the bus all wide or all narrow >> and all internal has never given us problems. > >The servers we have that keep blowing up have only a single internal DAT >on the narrow bus and a single internal UW HDD on the wide bus. It most >common for a tape error to lock up the machine, but they also lock up >with the same symptoms when no backups are being done. Hmmm...Do you have a narrow->wide converter than has termination for the upper (wide) data bits? I had a lot of problems here with using a narrow drive on a wide controller until Justin pointed out that the upper bits have to be terminated. I fixed the problem by putting a wide device at the end of the same cable that the narrow device was on (thus providing full wide termination). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project