From owner-freebsd-stable Mon Feb 19 14:42:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 3F46C37B491 for ; Mon, 19 Feb 2001 14:42:39 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.1/8.11.1) with ESMTP id f1JMgDR28638; Mon, 19 Feb 2001 14:42:13 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.1/8.11.0) id f1JMgB704018; Mon, 19 Feb 2001 14:42:11 -0800 (PST) (envelope-from jdp) Date: Mon, 19 Feb 2001 14:42:11 -0800 (PST) Message-Id: <200102192242.f1JMgB704018@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Reply-To: stable@freebsd.org Cc: ehoward@ameritech.net Subject: Re: just keep on crashing... In-Reply-To: <20010214143910.A3906@ameritech.net> References: <20010214143910.A3906@ameritech.net> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20010214143910.A3906@ameritech.net>, Eric L. Howard wrote: > I'm attempting to get 4.2 up on a homebrew. > > ASUS P2B-DS mobo w/ onboard aic7xxx > 2 - Seagate ST39204LW U2 drives > Dual PIII 700Mhz > > I'm almost consistently running into problems when I go to do stuff like cvsup > or even installing some packages. Seems as if whenever I get into something > pushing the drives heavy and consistently for any sustained period the machines > crashes. > > Errors include > SCB 69: Immediate reset > and > Invalid pack [...] > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da0: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da1: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) I could be steering you in the wrong direction, but I believe these are the Seagate drives that had a firmware bug which could cause the kinds of symptoms you describe. The work-around is to disable write cache enable (WCE) on the drives using "camcontrol modepage -e ...". Sorry, I don't remember the precise incantation, and you can read the camcontrol man page as well as I can. :-) Try turning off WCE on these drives and see if it fixes the problem. It can't hurt. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message