From owner-freebsd-scsi Wed Aug 23 22:49:27 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id BE60B37B43C for ; Wed, 23 Aug 2000 22:49:24 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id 789EC2B2BC; Thu, 24 Aug 2000 00:49:24 -0500 (CDT) Date: Wed, 23 Aug 2000 22:49:24 -0700 From: Paul Saab To: "Barrett G. Lyon" Cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec 3960D Ultra160 issues Message-ID: <20000823224924.A90931@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from blyon@theshell.com on Wed, Aug 23, 2000 at 10:39:58PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Turn off write caching. On recent 4.1 stable echo "WCE: 0" | camcontrol modepage da0 -m 8 -P 3 On older 4.1 stable EDITOR="/usr/bin/perl -i -pe 's/1/0/g if /^WCE/'" camcontrol \ modepage da0 -m 8 -P 3 Its a bug with U160 drives these days.. The otherway to fix it is to get an updated firmware from your drive manufacturer. paul Barrett G. Lyon (blyon@theshell.com) wrote: > > I would like to pre-apologize if I am posting this to the wrong list. I > am running FreeBSD 4.1-STABLE on x86 with this Adaptec 3960D Ultra160 SCSI > controller using an IBM DDYS-T09170N Ultra160 disk. The machine locks up > weekly on any heavy load. It was crashing when the vm system would get > stressed so we added more memory and now it is only crashing with the > filesystem is stressed (I think). > > One of the problems is that the Ultra160 disk (the IBM one) is not coming > up at 80 MHz only at 40 MHz: > > da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > > I'm not sure why that is happening because the SCSI adapter in the bios > detects it and shows it listed as operating at u160. I figured it could > be a driver issue so I updated from 4.0 to 4.1 and that seemed to not help > too much. > > Here is the debugger output from today's crash: > > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > dev = #da/0x20005, ino = 902, fs = /usr > panic: ffs_vfree: freeing free inode > Debugger("panic") > Stopped at Debugger+0x34: movb $0,in_Debugger.390 > db> next > Stopped at Debugger+0x3c: ret > db> next > > syncing disks... (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (on and on) > > > I'm not much of a BSD genius, any help would be very appreciated. > > -Barrett > > > > Barrett G. Lyon > Have fun: www.AlphaLinux.org > > [Q]: Hey, do they test this stuff before it's released? > [A]: Sure they do... "It compiles, it's ready!" > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message