From owner-freebsd-scsi Sat Nov 9 22:28:25 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA18188 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 22:28:25 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA18181 for ; Sat, 9 Nov 1996 22:28:20 -0800 (PST) Received: by sovcom.kiae.su id AA20209 (5.65.kiae-1 ); Sun, 10 Nov 1996 09:24:57 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 10 Nov 96 09:24:57 +0300 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id JAA00321; Sun, 10 Nov 1996 09:17:09 +0300 (MSK) Message-Id: <199611100617.JAA00321@nagual.ru> Subject: Re: SCSI system becomes broken in -current? In-Reply-To: <199611100501.VAA13610@freefall.freebsd.org> from "Justin T. Gibbs" at "Nov 9, 96 09:01:20 pm" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sun, 10 Nov 1996 09:17:08 +0300 (MSK) Cc: scsi@freebsd.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >I turn tagged queue off about two hours ago and extensively test > >my drives under hard load. And still not have this bug, so it seems > >it _is_ tagged queue related. I have one good news, Tagged Queueing WORK after firmware upgrade!!! BTW, SCB Paging still not work for two devices and cause serious inode damages as before. It work for any of device alone. > I wasn't expecting you to run it yet, just pointing out that I had the 1060 > in mind when I added generic tagged queueing support to the SCSI system. > As for stability, the aic7xxx cards have been the only ones tested heavily > with the new code. 8-) If you can send me the inquiry data again for your > drive, I can probably combine that with the info in the Linux FAQ entry to > only penalize the drives with that version of the firmware. Before upgrade I have (ahc0:0:0): "CONNER CFP1060S 1.05GB 2135" type 0 fixed SCSI 2 and after upgrade I got (ahc0:0:0): "CONNER CFP1060S 1.05GB 213C" type 0 fixed SCSI 2 As you can notice, they change 2135->213C, so it seems any CONNER < 213C can be treated as "known rogue" with proper kernel warning about its upgrade. As I already say, it will be nice to put this firmware upgrade somewhere on FreeBSD ftp with proper link from the hardware FAQ to eliminate possible problems... -- Andrey A. Chernov http://www.nagual.ru/~ache/