Date: Fri, 09 Sep 2005 12:04:56 +0100 From: "tonix (Antonio Nati)" <tonix@interazioni.it> To: freebsd-scsi@FreeBSD.ORG Subject: Re: camcontrol and IDAD0 Message-ID: <6.2.3.4.0.20050909120032.053cc160@pop.ufficiopostale.it> In-Reply-To: <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> <20050907133856.C84118@sasami.jurai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 18.41 07/09/2005, Matthew N. Dodd wrote: >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. Finally, these controllers seems to be unusable in a production environment with FreeBSD. Are new drivers (like ciss) and related controllers (Smart Array 5300 and following) exempt from these errors? Tonino
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.2.3.4.0.20050909120032.053cc160>