From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 7 17:41:20 2005 Return-Path: X-Original-To: freebsd-scsi@FreeBSD.ORG 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 2D13D16A41F for ; Wed, 7 Sep 2005 17:41:20 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [70.88.158.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9E4A43D48 for ; Wed, 7 Sep 2005 17:41:19 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [70.88.158.93]) by sasami.jurai.net (8.13.1/8.13.1) with ESMTP id j87HfGnT038702; Wed, 7 Sep 2005 13:41:18 -0400 (EDT) (envelope-from mdodd@FreeBSD.ORG) Date: Wed, 7 Sep 2005 13:41:16 -0400 (EDT) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: "tonix (Antonio Nati)" In-Reply-To: <6.2.3.4.0.20050907164953.0548c070@pop.ufficiopostale.it> Message-ID: <20050907133856.C84118@sasami.jurai.net> References: <6.2.3.4.0.20050901172618.0532ecb0@pop.ufficiopostale.it> <20050906084747.A84118@sasami.jurai.net> <6.2.3.4.0.20050907153854.04c36bc8@pop.ufficiopostale.it> <6.2.3.4.0.20050907163520.05554a30@pop.ufficiopostale.it> <6.2.3.4.0.20050907164953.0548c070@pop.ufficiopostale.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (sasami.jurai.net [70.88.158.93]); Wed, 07 Sep 2005 13:41:19 -0400 (EDT) Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: camcontrol and IDAD0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2005 17:41:20 -0000 On Wed, 7 Sep 2005, tonix (Antonio Nati) wrote: > System is continuosly hanging. > > This is the screen shot of system hanging, with details on IDAD error. > > ida0: soft error > ida_command: out of QCBsida0: ida_timeout() qactive 256 > ida0: IDA_INTERRUPTS > ida0: R_CMD_FIFO: 00000000 > R_DONE_FIFO: 00000000 > R_INT_MASK: 00000000 > R_STATUS: 00000000 > R_INT_PENDING: 00000000 Ah, yes. I believe you've run into a firmware crash. Make sure your cards have the latest firmware running. I've seen cases where hot swapping drives causes the firmware to reset and lock up (based on the LED pattern of the diagnostic lights on my cards.) I added command timeout detection to the driver as a means of detecting this condition. I don't have any good leads on recovinging from it though as my test hardware failed and I haven't replaced it yet. -- 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00