From owner-freebsd-stable@FreeBSD.ORG Fri Jul 4 15:28:56 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 CC22D37B401 for ; Fri, 4 Jul 2003 15:28:56 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A13A44003 for ; Fri, 4 Jul 2003 15:28:56 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 58CC172FE3; Fri, 4 Jul 2003 15:28:56 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 55B8E72FDC; Fri, 4 Jul 2003 15:28:56 -0700 (PDT) Date: Fri, 4 Jul 2003 15:28:56 -0700 (PDT) From: Doug White To: Lefteris Tsintjelis In-Reply-To: <3F04D74A.6F5CEDE8@ene.asda.gr> Message-ID: <20030704152620.L68494@carver.gumbysoft.com> References: <20030703202912.98149A960@ene.asda.gr> <20030703154953.M60013@carver.gumbysoft.com> <3F04D74A.6F5CEDE8@ene.asda.gr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@FreeBSD.org Subject: Re: SCSI backup error 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: Fri, 04 Jul 2003 22:28:57 -0000 On Fri, 4 Jul 2003, Lefteris Tsintjelis wrote: > The only line is the following one. There is no other relevant error message > besides that one. Could it be a hardware problem or simply a long device > time out that triggers the dump? It is an old DAT that I use. Strange though > that happened right after the upgrade. > > Jul 3 22:53:16 ene /kernel: (sa0:ahc2:0:6:0): SCB 0x5 - timed out Yeah, your cabling or termination is off. Recheck and replace if necessary. SCSI cables are fickle to say the least. Upgrades with changes to the adaptec drivers tend to improve the timings and peformance at the expense of breaking marginal setups. Justin Gibbs would have to analyze the dump to confirm my analysis, but this type of problem is pretty common. Its a remote possibility that an updated driver also tickles a bug in your drive's firmware -- I've seen this with an AIT-2 drive. You might check with the drive manufacturer if there is an update. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org