From owner-freebsd-scsi Sat Jul 8 2:44:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from dastor.albury.net.au (dastor.albury.NET.AU [203.15.244.203]) by hub.freebsd.org (Postfix) with ESMTP id 1790A37B8DA for ; Sat, 8 Jul 2000 02:44:28 -0700 (PDT) (envelope-from nicks@dastor.albury.net.au) Received: (from nicks@localhost) by dastor.albury.net.au (8.10.2/8.10.2) id e689iLm80662; Sat, 8 Jul 2000 19:44:21 +1000 (EST) Date: Sat, 8 Jul 2000 19:44:21 +1000 From: Nick Slager To: Alfred Perlstein Cc: scsi@FreeBSD.ORG Subject: Re: Invalidating pack weirdness Message-ID: <20000708194421.A80601@albury.net.au> References: <20000708010113.A25571@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000708010113.A25571@fw.wintelcom.net>; from bright@wintelcom.net on Sat, Jul 08, 2000 at 01:01:13AM -0700 X-Homer: Whoohooooooo! Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake Alfred Perlstein (bright@wintelcom.net): > Does anyone know if this is most likely coming from: > > 1) driver problem > 2) hardware misconfig > 3) hardware problem > #3. For me, this appeared to be caused by weird interactions between my Adaptec controller and Seagate disks. Disabling write caching in the BIOS appeared to fix it. Obviously, this is specific to my hardware; YMMV. Nick. -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message