Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Sep 2005 13:41:16 -0400 (EDT)
From:      "Matthew N. Dodd" <mdodd@FreeBSD.ORG>
To:        "tonix (Antonio Nati)" <tonix@interazioni.it>
Cc:        freebsd-scsi@FreeBSD.ORG
Subject:   Re: camcontrol and IDAD0
Message-ID:  <20050907133856.C84118@sasami.jurai.net>
In-Reply-To: <6.2.3.4.0.20050907164953.0548c070@pop.ufficiopostale.it>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050907133856.C84118>