From owner-freebsd-scsi Sun Sep 17 10:39:37 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 78E2D37B50C for ; Sun, 17 Sep 2000 10:39:35 -0700 (PDT) Received: (from gibbs@localhost) by caspian.plutotech.com (8.9.3/8.9.1) id AAA14523; Sat, 16 Sep 2000 00:53:24 -0600 (MDT) (envelope-from gibbs) Date: Sat, 16 Sep 2000 00:53:24 -0600 (MDT) Message-Id: <200009160653.AAA14523@caspian.plutotech.com> From: "Justin T. Gibbs" To: "Kelsey Womack" Cc: scsi@FreeBSD.org Subject: Re: Adaptec 21960 X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <001801c01ee1$6bd8a950$020a0a0a@tjabring> User-Agent: tin/1.4.2-20000205 ("Possession") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <001801c01ee1$6bd8a950$020a0a0a@tjabring> you wrote: > > It's odd, I have a 4.1-stable server, in production, never had a prob... and > we have the 29160. However, our other 2 machines could never get > to -stable, and I have been told -stable fixes that. The company I used to > work for had about 5 servers with 29160's and the infamous Seagate drives > taht supposedly case this prob, and I was told to just disable write-back > caching in the scsi bios. I had it done, didnt work... I just thought I > would share this with you. > > -Kelsey The issue with the Seagate drives was that they would spontaineously drop off the bus. That doesn't sound like what others are reporting, but then again, its not clear exactly what a "freeze" means. Is the system completely unresponsive to anything including an attempt to drop into the debugger? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message