From owner-freebsd-stable@FreeBSD.ORG Wed Oct 22 15:39:40 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D133716A4B3 for ; Wed, 22 Oct 2003 15:39:40 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 429A643F3F for ; Wed, 22 Oct 2003 15:39:40 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 3207E72DA3; Wed, 22 Oct 2003 15:39:40 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 2FC0572DA2; Wed, 22 Oct 2003 15:39:40 -0700 (PDT) Date: Wed, 22 Oct 2003 15:39:40 -0700 (PDT) From: Doug White To: Scott Mitchell In-Reply-To: <20031022212556.GA48208@llama.fishballoon.org> Message-ID: <20031022153722.P71676@carver.gumbysoft.com> References: <20031022212556.GA48208@llama.fishballoon.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: aic7896 SCB timeout - is this a sign of impending doom? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Oct 2003 22:39:40 -0000 On Wed, 22 Oct 2003, Scott Mitchell wrote: > The attached messages appeared on one of my servers this afternoon. Its > primarily a CVS server but beyond that I can't say what it was doing or how > busy it was when this happened, as I didn't see the messages until later. > > Is this anything to worry about? AFAICT some command to da4 timed out > (maybe twice?) and the driver eventually reset the bus to get things going > again... this has never happened before, and the machine seems perfectly > fine now. As mentioned, SCSI timeouts can have multiple causes, most of them not good. The thing to watch for is which target the command timed out on. Command timeouts can come from: . Bad cabling or termination . Bad cabling or termination . Bad cabling or termination (it needs to be said three times) . Flakey/failing device If it continues to happen then you should take a look around. Temperature wouldn't be a bad thing to check anyway. > The machine is running 4.8 on an Intel L440GX+ server board. Good boards. I'm using them as my build farm right now. 600MHz procs aren't that fast anymore but its a solid machine. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org