From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 17 10:01:42 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17BD016A544 for ; Wed, 17 Mar 2004 10:01:42 -0800 (PST) Received: from mail.webjockey.net (mail.webjockey.net [208.141.46.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id A681843D1D for ; Wed, 17 Mar 2004 10:01:41 -0800 (PST) (envelope-from gary@outloud.org) Received: from orion-i1q62b3yi.outloud.org (69-160-74-90.frdrmd.adelphia.net [69.160.74.90]) by mail.webjockey.net (8.12.10/8.12.8) with ESMTP id i2HI2Caj081064; Wed, 17 Mar 2004 13:02:12 -0500 (EST) (envelope-from gary@outloud.org) Message-Id: <6.0.3.0.2.20040317130041.01e48b48@208.141.46.3> X-Sender: ancient@208.141.46.3 X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Wed, 17 Mar 2004 13:01:45 -0500 To: "Aaron Wohl" From: Gary Stanley In-Reply-To: <1079523587.3785.182830953@webmail.messagingengine.com> References: <8ACA9163-6F29-11D8-8F17-003065A70D30@shire.net> <20040317093148.GN12602@math.jussieu.fr> <1079523587.3785.182830953@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec 2410SA starts doing this: aac0: COMMAND 0xc551a7e8TIMEOUTAFTER 147 SECONDS (Modified by Chad Leigh -- Shire.NetLLC) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2004 18:01:42 -0000 At 06:39 AM 3/17/2004, Aaron Wohl wrote: >We got command timeout with the aac driver off and on for about a year >with a 5400s and various freebsd versions. Ive been sending Scott the >info and he has tried various fixes. I switched one of the machines to >5.2.1 a couiple of weeks ago. It been ok so far. Buts sometimes it may >go a month or two then happen a lot so hard to say for sure yet. > >When it has happened to us power cycling and rebooting gets it unwedged >-- reset does not. I was having similar problems a long time ago, but it turned out it was a firmware issue with the drives. After I flashed all the drives (8 total) the problem went away. /ges