From owner-freebsd-scsi Sun Mar 24 15:10:19 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (dhcp45-24.dis.org [216.240.45.24]) by hub.freebsd.org (Postfix) with ESMTP id B166237B405 for ; Sun, 24 Mar 2002 15:10:15 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g2ON9MO02559; Sun, 24 Mar 2002 15:09:22 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200203242309.g2ON9MO02559@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: F J Cc: freebsd-scsi@FreeBSD.org Subject: Re: SCSI write semantics In-reply-to: Your message of "Sat, 23 Mar 2002 10:54:30 PST." <20020323185430.80848.qmail@web20503.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sun, 24 Mar 2002 15:09:22 -0800 From: Michael Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Are the SCSI disk writes atomic or they're hardware > dependent? They are not atomic. > What I mean is that if you issue a > 32KB write and the power goes off at the same > time, is there any gauarantee that either the > disk blocks will be updated completely or > nothing will be written at all? No guarantees. > what about SCSI RAID > controllers? Controllers with battery-backed memory will typically attempt to complete= = writes that were outstanding when power is reapplied and the array = verified to match the pre-power-loss configuration. This is about the = only configuration that gives you any "guarantees" at all. > Another concern is that DMA may be in > progress while memory contents become unstable. Is > this possible? I wouldn't expect this to be a problem; by the time memory has become = unstable, the rest of the system will be dead (and I suspect that the = chipset would be suppressed as soon as soon as the rails go out of spec).= -- = To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to = the American public. - Theodore Roosevelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 25 14:32:15 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from ace.ulyssis.org (ace.ulyssis.student.kuleuven.ac.be [193.190.253.36]) by hub.freebsd.org (Postfix) with ESMTP id 976FC37B8B4 for ; Mon, 25 Mar 2002 14:30:21 -0800 (PST) Received: (from cernunos@localhost) by ace.ulyssis.org (8.9.3/8.9.1) id XAA03375 for freebsd-scsi@freebsd.org; Mon, 25 Mar 2002 23:29:51 +0100 Date: Mon, 25 Mar 2002 23:29:51 +0100 From: Stijn Opheide To: freebsd-scsi@freebsd.org Subject: SCSI controller doesn't work during install Message-ID: <20020325232951.C19245@ace.ulyssis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I'm trying to install FreeBSD 4.5 on a Celebris XL 5100 with 2 pentium 100 cpu's. I have a NCR53c810 SCSI-adapter and FreeBSD fails when initialising the adapter. I wrote the message down (there can be some typo's in it): sym0: <810> port 0exec00.0xecff mem 0xfedfbf00.0xfedfbfff irq11 at device 10 on pci0 sym0: NO NVRAM, ID7, Fast-10, SE, parity checking sym0: PCI DATA PARITY ERROR DETECTED - DISABLING MASTER DATA PARITY CHECKING. CACHE TEST FAILED: host wrote 1, chip read 2. sym0: CACHE INCORRECTLY CONFIGURED. device_probe_and_attach: sym0 attach returned 6 I already posted this problem on freebsd-newbies@freebsd.org, but it remains unsolved. The scsi-adapter works with redhat 6.1 and openBSD (but I want BSD and SMP :-)) best regards, Stijn. -- Stijn Opheide mail: stijn.opheide@kotnet.org -- cernunos@ulyssis.org web: http://bifrost.kotnet.org -- http://cernunos.studentenweb.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 25 14:37:51 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp011.mail.yahoo.com (smtp011.mail.yahoo.com [216.136.173.31]) by hub.freebsd.org (Postfix) with SMTP id CA5D237B4B0 for ; Mon, 25 Mar 2002 14:36:17 -0800 (PST) Received: from kc5vdj (AUTH plain) at mkc-65-30-96-67.kc.rr.com (HELO yahoo.com) (kc5vdj@65.30.96.67) by smtp.mail.vip.sc5.yahoo.com with SMTP; 25 Mar 2002 22:35:38 -0000 Message-ID: <3C9FA639.4040908@yahoo.com> Date: Mon, 25 Mar 2002 16:35:37 -0600 From: Jim Bryant Reply-To: kc5vdj@yahoo.com User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Julian Elischer Cc: scsi@freebsd.org Subject: Re: SCSI error messages. References: <3C9A8A03.A36B57B6@vicor-nb.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org One odd thing I noticed off the top of my head, is the size of da0 and da1. I am unaware of any half-terabyte disk drives being in current manufacture [but I could be wrong]... Are these arrays appearing as single drives? Julian Elischer wrote: > These were seen on a production machine.. > If anyone who knows the reason for these messages, > We's love an interpretation.... > > Julian > > > ------------------------------------------------------------------------ > [big snip] > > Mar 21 13:31:08 oos0c /kernel: da1 at ahc2 bus 0 target 1 lun 1 > Mar 21 13:31:08 oos0c /kernel: da1: Fixed Direct Access SCSI-3 device > Mar 21 13:31:08 oos0c /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged Queueing Enabled > Mar 21 13:31:08 oos0c /kernel: da1: 558463MB (1143732224 512 byte sectors: 255H 63S/T 5658C) > Mar 21 13:31:08 oos0c /kernel: da0 at ahc0 bus 0 target 1 lun 1 > Mar 21 13:31:08 oos0c /kernel: da0: Fixed Direct Access SCSI-3 device > Mar 21 13:31:08 oos0c /kernel: da0: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged Queueing Enabled > Mar 21 13:31:08 oos0c /kernel: da0: 558463MB (1143732224 512 byte sectors: 255H 63S/T 5658C) jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! ----------------------------------------------------- POWER TO THE PEOPLE! ----------------------------------------------------- "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 25 14:51:12 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by hub.freebsd.org (Postfix) with ESMTP id 53A3D37B404 for ; Mon, 25 Mar 2002 14:51:08 -0800 (PST) Received: from vicor-nb.com (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 223021B268; Mon, 25 Mar 2002 14:51:08 -0800 (PST) Message-ID: <3C9FA9DC.1D916539@vicor-nb.com> Date: Mon, 25 Mar 2002 14:51:08 -0800 From: Julian Elischer Organization: VICOR X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-STABLE i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: kc5vdj@yahoo.com Cc: scsi@freebsd.org Subject: Re: SCSI error messages. References: <3C9A8A03.A36B57B6@vicor-nb.com> <3C9FA639.4040908@yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Jim Bryant wrote: > > One odd thing I noticed off the top of my head, is the size of da0 and da1. > > I am unaware of any half-terabyte disk drives being in current manufacture [but I could be wrong]... Are these arrays appearing as > single drives? yes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 26 3:20:42 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id E56D337B416 for ; Tue, 26 Mar 2002 03:20:32 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id g2QBKEr02995; Tue, 26 Mar 2002 12:20:14 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g2QBGo6e095612; Tue, 26 Mar 2002 12:16:50 +0100 (CET)?g (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.2/8.12.2) with ESMTP id g2QBGonU017317; Tue, 26 Mar 2002 12:16:50 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.2/8.12.2/Submit) id g2QBGlXd017316; Tue, 26 Mar 2002 12:16:47 +0100 (CET) Date: Tue, 26 Mar 2002 12:16:46 +0100 From: Bernd Walter To: Julian Elischer Cc: Scott Long , scsi@FreeBSD.ORG Subject: Re: SCSI error messages. Message-ID: <20020326111645.GG14060@cicely8.cicely.de> References: <3C9A8A03.A36B57B6@vicor-nb.com> <1016761959.8445.19.camel@hollin.btc.adaptec.com> <3C9A90FE.30983DC@vicor-nb.com> <1016763240.8445.24.camel@hollin.btc.adaptec.com> <3C9A947D.CC00A837@vicor-nb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C9A947D.CC00A837@vicor-nb.com> User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Mar 21, 2002 at 06:18:37PM -0800, Julian Elischer wrote: > Scott Long wrote: > > > > > > > > Oops, you might be right, I mistook the pcib0 line. Still, check the > > BIOS to see if anything screwy is enabled. > > > > Scott > > Also I should add that the machine has been seen working for a while. > I just would like to know what the messages mean. Well the timeouts are because the drive went to sleep and did not return from a comand in a reasonable time. The result is a BDR (bus device reset) which tries to reset the drive. Finaly the drive responds not beeing ready. Sounds like a bad firmware on the drive. The timeout alone could be a bad cabeling too, but this should not result in dropping the device. You might work around the firmware bug by disabling tagged queueing and/or write cache. It could also be triggered by a problem with a physical drive. Nevertheless the error behavour is broken. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 26 14: 2: 7 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id 1F53A37B419 for ; Tue, 26 Mar 2002 14:02:03 -0800 (PST) Received: from [192.168.1.129] (212.129.10.222) by mail.libertysurf.net (5.1.053) id 3C9007EB002B3C10; Tue, 26 Mar 2002 23:02:53 +0100 Date: Tue, 26 Mar 2002 03:53:54 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: groudier@localhost.my.domain To: Stijn Opheide Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI controller doesn't work during install In-Reply-To: <20020325232951.C19245@ace.ulyssis.org> Message-ID: <20020326033613.Q1995-100000@localhost.my.domain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org It is the second failure of this kind I saw reported under FreeBSD 4.5. Note that everything works on my machine (Supermicro 370 DLE + 810A + 895 + 896 + 1033-66) under this O/S version. Btw, Il also have no Symbios driver problems under Linux. :) The driver has been full source-stable since at least 1 year and haven't had problems of this kind reported under FreeBSD 4.3 for example. What happens is that a physical address used by the chip to DMA from the PCI bus seems wrong. The failure happens during some simple checkings performed at initialisation. The driver gets such address values from the kernel BUS handling software. Could you give a try with FreeBSD 4.3 and/or 4.4 installation and see if it makes difference (as I wrote, these O/S versions have basically same sym driver version as 4.5). G=E9rard. On Mon, 25 Mar 2002, Stijn Opheide wrote: > Hi, > > I'm trying to install FreeBSD 4.5 on a Celebris XL 5100 with 2 pentium > 100 cpu's. I have a NCR53c810 SCSI-adapter and FreeBSD fails when > initialising the adapter. I wrote the message down (there can be some > typo's in it): > > sym0: <810> port 0exec00.0xecff mem 0xfedfbf00.0xfedfbfff irq11 at > device 10 on pci0 > sym0: NO NVRAM, ID7, Fast-10, SE, parity checking > sym0: PCI DATA PARITY ERROR DETECTED - DISABLING MASTER DATA PARITY > CHECKING. > CACHE TEST FAILED: host wrote 1, chip read 2. > sym0: CACHE INCORRECTLY CONFIGURED. > device_probe_and_attach: sym0 attach returned 6 > > I already posted this problem on freebsd-newbies@freebsd.org, but it > remains unsolved. > > The scsi-adapter works with redhat 6.1 and openBSD (but I want BSD and > SMP :-)) > > best regards, > > Stijn. > > -- > Stijn Opheide > mail: stijn.opheide@kotnet.org -- cernunos@ulyssis.org > web: http://bifrost.kotnet.org -- http://cernunos.studentenweb.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 27 19:24:37 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from ace.ulyssis.org (ace.ulyssis.student.kuleuven.ac.be [193.190.253.36]) by hub.freebsd.org (Postfix) with ESMTP id EB6CE37B417 for ; Wed, 27 Mar 2002 19:24:33 -0800 (PST) Received: (from cernunos@localhost) by ace.ulyssis.org (8.9.3/8.9.1) id EAA32640; Thu, 28 Mar 2002 04:24:32 +0100 Date: Thu, 28 Mar 2002 04:24:32 +0100 From: Stijn Opheide To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-scsi@freebsd.org Subject: Re: SCSI controller doesn't work during install Message-ID: <20020328042432.P19245@ace.ulyssis.org> References: <20020325232951.C19245@ace.ulyssis.org> <20020326033613.Q1995-100000@localhost.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <20020326033613.Q1995-100000@localhost.my.domain>; from groudier@free.fr on Tue, Mar 26, 2002 at 03:53:54AM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Mar 26, 2002 at 03:53:54AM +0100, Gérard Roudier wrote: > It is the second failure of this kind I saw reported under FreeBSD 4.5. > Note that everything works on my machine (Supermicro 370 DLE + 810A + 895 > + 896 + 1033-66) under this O/S version. > > Btw, Il also have no Symbios driver problems under Linux. :) > > The driver has been full source-stable since at least 1 year and haven't > had problems of this kind reported under FreeBSD 4.3 for example. > > What happens is that a physical address used by the chip to DMA from the > PCI bus seems wrong. The failure happens during some simple checkings > performed at initialisation. The driver gets such address values from the > kernel BUS handling software. > > Could you give a try with FreeBSD 4.3 and/or 4.4 installation and see if > it makes difference (as I wrote, these O/S versions have basically same > sym driver version as 4.5). It works with FreeBSD 4.3, not with 4.4... greetings, Stijn. -- Stijn Opheide mail: stijn.opheide@kotnet.org -- cernunos@ulyssis.org web: http://bifrost.kotnet.org -- http://cernunos.studentenweb.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 28 11:39:56 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.johnrshannon.com (mail.johnrshannon.com [208.141.183.125]) by hub.freebsd.org (Postfix) with ESMTP id 6337637B442 for ; Thu, 28 Mar 2002 11:39:33 -0800 (PST) Received: from pablo.johnrshannon.com (pablo.johnrshannon.com [192.168.1.3]) by mail.johnrshannon.com (Postfix) with ESMTP id 775B2E8B4 for ; Thu, 28 Mar 2002 12:39:30 -0700 (MST) Received: from pablo.johnrshannon.com (localhost [127.0.0.1]) by pablo.johnrshannon.com (8.12.2/8.11.6) with ESMTP id g2SJdUMb001126 for ; Thu, 28 Mar 2002 12:39:30 -0700 (MST) (envelope-from john@pablo.johnrshannon.com) Received: (from john@localhost) by pablo.johnrshannon.com (8.12.2/8.12.1/Submit) id g2SJdUAY001125 for freebsd-scsi@freebsd.org; Thu, 28 Mar 2002 12:39:30 -0700 (MST)?g (envelope-from john) Message-Id: <200203281939.g2SJdUAY001125@pablo.johnrshannon.com> Content-Type: text/plain; charset="iso-8859-1" From: "John R. Shannon" Reply-To: john@johnrshannon.com To: freebsd-scsi@freebsd.org Subject: sym Date: Thu, 28 Mar 2002 12:39:30 -0700 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org FreeBSD 4.5-release Tekram DC-390U3W What is occurring with the M_REJECT listed in the excerpt from dmesg below: sym0: <1010-33> port 0xc000-0xc0ff mem 0xefffa000-0xefffbfff,0xeffff800-0xeffffbff irq 11 at device 13.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: handling phase mismatch from SCRIPTS. sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym1: <1010-33> port 0xd000-0xd0ff mem 0xefffc000-0xefffdfff,0xeffffc00-0xefffffff irq 11 at device 13.1 on pci0 sym1: Symbios NVRAM, ID 7, Fast-80, SE, parity checking sym1: handling phase mismatch from SCRIPTS. sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. ... (noperiph:sym1:0:-1:-1): SCSI BUS reset detected. (probe21:sym1:0:6:0): M_REJECT received (7:8). (probe21:sym1:0:6:0): M_REJECT to send for: 1-6-4-c-0-3e-1-0. Mounting root from ufs:/dev/da0s1a da0 at sym1 bus 0 target 6 lun 0 da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8759MB (17938985 512 byte sectors: 255H 63S/T 1116C) da0: Fixed Direct Access SCSI-3 device da1 at sym1 bus 0 target 15 lun 0 da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 8714MB (17847486 512 byte sectors: 255H 63S/T 1110C) da1: Fixed Direct Access SCSI-4 device Thank You. -- John R. Shannon john@johnrshannon.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 28 12: 9:35 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mailbox.univie.ac.at (mailbox.univie.ac.at [131.130.1.27]) by hub.freebsd.org (Postfix) with ESMTP id 8BB6237B416 for ; Thu, 28 Mar 2002 12:09:27 -0800 (PST) Received: from korben (mailboxts3-46.univie.ac.at [131.130.99.46]) by mailbox.univie.ac.at (8.12.2/8.12.2) with ESMTP id g2SK9Cun963802 for ; Thu, 28 Mar 2002 21:09:18 +0100 Date: Thu, 28 Mar 2002 21:08:57 +0100 (=?ISO-8859-1?Q?Westeurop=E4ische_Normalzeit?=) From: Lukas Ertl To: freebsd-scsi@freebsd.org Subject: ciss driver and tagged queuing Message-ID: X-X-Sender: le@mailbox.univie.ac.at MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I hope this is the correct list to ask this: I have a brand new Compaq Proliant box here, which has a Smart Array 5302 controller (ciss driver). I did some performance testing on it (with bonnie++), but I wasn't quite satisfied, the throughput on the Smart Array is rather low. So I thought I have a look with camcontrol on it: [root@raidtest /home/le]# camcontrol negotiate da1 -T enable Current Parameters: (pass1:ciss1:0:0:0): disconnection is enabled camcontrol: XPT_SET_TRANS_SETTINGS CCB failed, status 0x6 [root@raidtest /home/le]# camcontrol negotiate da1 -v Current Parameters: (pass1:ciss1:0:0:0): disconnection is enabled ciss1: SIM/HBA version: 1 ciss1: supports tag queue messages ciss1: HBA engine count: 0 ciss1: maximum target: 15 ciss1: maximum LUN: 0 ciss1: highest path ID in subsystem: 0 ciss1: initiator ID: 15 ciss1: SIM vendor: FreeBSD ciss1: HBA vendor: msmith@freebsd.ociss ciss1: bus ID: 0 ciss1: base transfer speed: 135.168MB/sec I guess this means that the device is able to do tagged queueing, but the feature is currently turned off. So I tried to enable it and I get this error message: [root@raidtest /home/le]# camcontrol negotiate da1 -T enable Current Parameters: (pass1:ciss1:0:0:0): disconnection is enabled camcontrol: XPT_SET_TRANS_SETTINGS CCB failed, status 0x6 Can anyone tell me what this means? Is the driver lying to me about tagged queueing? Apart from that: the ciss driver is fairly new AFAIK, I didn't find a lot of references to it on the web. Would you recommend it for production use? Is there any testing going for userland tools (status control a.s.o.)? best regards, le --=20 Lukas Ertl eMail: l.ertl@univie.ac.at UNIX-Systemadministrator Tel.: (+43 1) 4277-14073 Zentraler Informatikdienst (ZID) Fax.: (+43 1) 4277-9140 der Universit=E4t Wien http://mailbox.univie.ac.at/~le/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 28 12:42:33 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 5F68737B41E for ; Thu, 28 Mar 2002 12:42:22 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g2SKg7Y22570; Thu, 28 Mar 2002 13:42:07 -0700 (MST) (envelope-from ken) Date: Thu, 28 Mar 2002 13:42:07 -0700 From: "Kenneth D. Merry" To: Lukas Ertl Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ciss driver and tagged queuing Message-ID: <20020328134207.A22421@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from l.ertl@univie.ac.at on Thu, Mar 28, 2002 at 09:08:57PM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Mar 28, 2002 at 21:08:57 +0100, Lukas Ertl wrote: > Hi, > > I hope this is the correct list to ask this: > > I have a brand new Compaq Proliant box here, which has a Smart Array 5302 > controller (ciss driver). I did some performance testing on it (with > bonnie++), but I wasn't quite satisfied, the throughput on the Smart Array > is rather low. So I thought I have a look with camcontrol on it: What were your performance numbers, anyway? > [root@raidtest /home/le]# camcontrol negotiate da1 -T enable > Current Parameters: > (pass1:ciss1:0:0:0): disconnection is enabled > camcontrol: XPT_SET_TRANS_SETTINGS CCB failed, status 0x6 > [root@raidtest /home/le]# camcontrol negotiate da1 -v > Current Parameters: > (pass1:ciss1:0:0:0): disconnection is enabled > ciss1: SIM/HBA version: 1 > ciss1: supports tag queue messages > ciss1: HBA engine count: 0 > ciss1: maximum target: 15 > ciss1: maximum LUN: 0 > ciss1: highest path ID in subsystem: 0 > ciss1: initiator ID: 15 > ciss1: SIM vendor: FreeBSD > ciss1: HBA vendor: msmith@freebsd.ociss > ciss1: bus ID: 0 > ciss1: base transfer speed: 135.168MB/sec Hmm, that value is a bit funny, although I suppose for a RAID board it's kinda hard to know exactly what to put there. > I guess this means that the device is able to do tagged queueing, but the > feature is currently turned off. So I tried to enable it and I get this > error message: > > [root@raidtest /home/le]# camcontrol negotiate da1 -T enable > Current Parameters: > (pass1:ciss1:0:0:0): disconnection is enabled > camcontrol: XPT_SET_TRANS_SETTINGS CCB failed, status 0x6 > > Can anyone tell me what this means? Is the driver lying to me about tagged > queueing? The driver doesn't support the XPT_SET_TRANS_SETTINGS CCB, but it does support the XPT_GET_TRAN_SETTINGS CCB. So you can get the transfer negotiation settings, but you can't set them. I would suggest using the 'tags' camcontrol command to see how many tag openings there are for the device, that might be more informative. > Apart from that: the ciss driver is fairly new AFAIK, I didn't find a lot > of references to it on the web. Would you recommend it for production use? > Is there any testing going for userland tools (status control a.s.o.)? Mike Smith would be the one to ask. I would also recommend looking into any caching parameters, etc., you may be able to set on the controller. That can have an effect on controller performance. I don't know anything about the ciss boards/driver, though, so I don't really know where you'd look to set that sort of thing. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 28 12:55:13 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from statler.a1plus.at (ns1.a1plus.at [193.154.168.2]) by hub.freebsd.org (Postfix) with ESMTP id 201D137B400 for ; Thu, 28 Mar 2002 12:55:08 -0800 (PST) Received: from dialup209.d1-Bhf1.Liez.AT.KPNQwest.net (dialup209.d1-Bhf1.Liez.AT.KPNQwest.net [193.81.58.209]) by statler.a1plus.at (8.11.1/8.11.1) with ESMTP id g2SKsxn17346; Thu, 28 Mar 2002 21:55:00 +0100 (MET) Date: Thu, 28 Mar 2002 21:54:50 +0100 (CET) From: Lukas Ertl X-X-Sender: le@korben.in.tern To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ciss driver and tagged queuing In-Reply-To: <20020328134207.A22421@panzer.kdm.org> Message-ID: <20020328214454.B214-100000@korben.in.tern> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 28 Mar 2002, Kenneth D. Merry wrote: > > I have a brand new Compaq Proliant box here, which has a Smart Array 53= 02 > > controller (ciss driver). I did some performance testing on it (with > > bonnie++), but I wasn't quite satisfied, the throughput on the Smart Ar= ray > > is rather low. So I thought I have a look with camcontrol on it: > > What were your performance numbers, anyway? If you are interested, you can find some figures at . I tested two Compaq Proliant boxes, one with a Smart Array Controller and a Smart Array, one with a Dual Channel Host Adapter (with Adaptec Chip) and a SCSI/IDE Raid Subsystem (speaks SCSI on the outside, has IDE disks inside). The SCSI/IDE Raid figures are often significantly higher. If you want to know more details, just mail me. > > camcontrol: XPT_SET_TRANS_SETTINGS CCB failed, status 0x6 > > The driver doesn't support the XPT_SET_TRANS_SETTINGS CCB, but it does > support the XPT_GET_TRAN_SETTINGS CCB. So you can get the transfer > negotiation settings, but you can't set them. Hm. > I would suggest using the 'tags' camcontrol command to see how many tag > openings there are for the device, that might be more informative. Ok: [root@raidtest /home/le]# camcontrol tags da1 -v (pass1:ciss1:0:0:0): dev_openings 1 (pass1:ciss1:0:0:0): dev_active 0 (pass1:ciss1:0:0:0): devq_openings 1 (pass1:ciss1:0:0:0): devq_queued 0 (pass1:ciss1:0:0:0): held 0 (pass1:ciss1:0:0:0): mintags 2 (pass1:ciss1:0:0:0): maxtags 255 > > Apart from that: the ciss driver is fairly new AFAIK, I didn't find a l= ot > > of references to it on the web. Would you recommend it for production u= se? > > Is there any testing going for userland tools (status control a.s.o.)? > > Mike Smith would be the one to ask. Is he on this list? Thanks for your quick answer. regards, le --=20 Lukas Ertl eMail: l.ertl@univie.ac.at UNIX-Systemadministrator Tel.: (+43 1) 4277-14073 Zentraler Informatikdienst (ZID) Fax.: (+43 1) 4277-9140 der Universit=E4t Wien http://mailbox.univie.ac.at/~le/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 28 14:26:59 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 3992137B404 for ; Thu, 28 Mar 2002 14:26:53 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g2SMQiJ23441; Thu, 28 Mar 2002 15:26:44 -0700 (MST) (envelope-from ken) Date: Thu, 28 Mar 2002 15:26:44 -0700 From: "Kenneth D. Merry" To: Lukas Ertl Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ciss driver and tagged queuing Message-ID: <20020328152644.A23074@panzer.kdm.org> References: <20020328134207.A22421@panzer.kdm.org> <20020328214454.B214-100000@korben.in.tern> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020328214454.B214-100000@korben.in.tern>; from l.ertl@univie.ac.at on Thu, Mar 28, 2002 at 09:54:50PM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Mar 28, 2002 at 21:54:50 +0100, Lukas Ertl wrote: > On Thu, 28 Mar 2002, Kenneth D. Merry wrote: > > > > I have a brand new Compaq Proliant box here, which has a Smart Array 5302 > > > controller (ciss driver). I did some performance testing on it (with > > > bonnie++), but I wasn't quite satisfied, the throughput on the Smart Array > > > is rather low. So I thought I have a look with camcontrol on it: > > > > What were your performance numbers, anyway? > > If you are interested, you can find some figures at > . I tested two Compaq > Proliant boxes, one with a Smart Array Controller and a Smart Array, one > with a Dual Channel Host Adapter (with Adaptec Chip) and a SCSI/IDE Raid > Subsystem (speaks SCSI on the outside, has IDE disks inside). The SCSI/IDE > Raid figures are often significantly higher. If you want to know more > details, just mail me. What RAID level are you using? There are significant differences (on the smart array controller at least) between the block read and write results. With the SCSI->IDE controller, oddly, the write results are faster than the read results. > > I would suggest using the 'tags' camcontrol command to see how many tag > > openings there are for the device, that might be more informative. > > Ok: > > [root@raidtest /home/le]# camcontrol tags da1 -v > (pass1:ciss1:0:0:0): dev_openings 1 > (pass1:ciss1:0:0:0): dev_active 0 > (pass1:ciss1:0:0:0): devq_openings 1 > (pass1:ciss1:0:0:0): devq_queued 0 > (pass1:ciss1:0:0:0): held 0 > (pass1:ciss1:0:0:0): mintags 2 > (pass1:ciss1:0:0:0): maxtags 255 Yeah, you can only have one tag outstanding to the array. So I would expect that performance might not be as good as if you could have multiple commands outstanding. What does dmesg say about the card? From looking at the driver, it looks like the "max outstanding commands" value that is printed out on boot will tell us how many outstanding transactions the card claims to support. > > > Apart from that: the ciss driver is fairly new AFAIK, I didn't find a lot > > > of references to it on the web. Would you recommend it for production use? > > > Is there any testing going for userland tools (status control a.s.o.)? > > > > Mike Smith would be the one to ask. > > Is he on this list? I think so. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 28 14:35:22 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from ns2.a1plus.at (ns2.a1plus.at [193.154.168.4]) by hub.freebsd.org (Postfix) with ESMTP id 966B837B417 for ; Thu, 28 Mar 2002 14:35:14 -0800 (PST) Received: from dialup209.d1-Bhf1.Liez.AT.KPNQwest.net (dialup209.d1-Bhf1.Liez.AT.KPNQwest.net [193.81.58.209]) by ns2.a1plus.at (8.12.2/8.12.2) with ESMTP id g2SMZAGQ004292; Thu, 28 Mar 2002 23:35:11 +0100 (MET) Date: Thu, 28 Mar 2002 23:35:01 +0100 (CET) From: Lukas Ertl X-X-Sender: le@korben.in.tern To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ciss driver and tagged queuing In-Reply-To: <20020328152644.A23074@panzer.kdm.org> Message-ID: <20020328232901.L214-100000@korben.in.tern> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 28 Mar 2002, Kenneth D. Merry wrote: > What RAID level are you using? There are significant differences (on the > smart array controller at least) between the block read and write results= =2E > With the SCSI->IDE controller, oddly, the write results are faster than t= he > read results. RAID5. I don't have a lot of experience with RAID, so I don't know if the number of disks have an influence on the result (12 80GB IDE disks in the SCSI/IDE array, 8 72GB disks in the Compaq array). > What does dmesg say about the card? From looking at the driver, it looks > like the "max outstanding commands" value that is printed out on boot wil= l > tell us how many outstanding transactions the card claims to support. Ok: ciss1: port 0x3000-0x30ff mem 0xf7e00000-0xf7efffff,0x f7fc0000-0xf7ffffff irq 3 at device 4.0 on pci7 ciss1: using 256 of 1024 available commands ciss1: 1 logical drive configured ciss1: firmware 1.76 ciss1: 2 SCSI channels ciss1: signature 'CISS' ciss1: valence 1 ciss1: supported I/O methods 0xe ciss1: active I/O method 0x3 ciss1: 4G page base 0x00000000 ciss1: interrupt coalesce delay 1000us ciss1: interrupt coalesce count 0 ciss1: max outstanding commands 1024 ciss1: bus types 0x2 ciss1: server name '' ciss1: heartbeat 0x20000022 ciss1: 1 logical drive ciss1: logical drive 0: RAID 5, 416768MB online regards, le --=20 Lukas Ertl eMail: l.ertl@univie.ac.at UNIX-Systemadministrator Tel.: (+43 1) 4277-14073 Zentraler Informatikdienst (ZID) Fax.: (+43 1) 4277-9140 der Universit=E4t Wien http://mailbox.univie.ac.at/~le/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 28 14:43:35 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id 19C6437B416 for ; Thu, 28 Mar 2002 14:43:28 -0800 (PST) Received: from [192.168.1.129] (212.129.44.153) by mail.libertysurf.net (5.1.053) id 3C9007EB00331B7D; Thu, 28 Mar 2002 23:44:43 +0100 Date: Fri, 29 Mar 2002 00:43:40 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: groudier@localhost.my.domain To: "John R. Shannon" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sym In-Reply-To: <200203281939.g2SJdUAY001125@pablo.johnrshannon.com> Message-ID: <20020328232957.P1809-100000@localhost.my.domain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 28 Mar 2002, John R. Shannon wrote: > FreeBSD 4.5-release > Tekram DC-390U3W > > What is occurring with the M_REJECT listed in the excerpt from dmesg belo= w: Some harmless noise, it seems. :) The messages seem related to a transfer negotiation that has been hard to be agreed by the driver and the ATLAS10K2 drive. I notice that the involved SCSI BUS (sym0) is Single Ended (20 MT/s ST max.). OTOH, the 2nd REJECT message, > (probe21:sym1:0:6:0): M_REJECT to send for: 1-6-4-c-0-3e-1-0. let me think that the driver wrongly initiated a negotiation for a DT data transfer (the 1010-33 only supports offset 31 in ST mode but supports offset 62=3D0x3e in DT mode). The driver does not check the actual BUS mode (SE versus LVD), but only relies on the user setup in HBA NVRAM for transfer negotiation initiation. (It should obviously check the BUS mode). As a result, setting a realistic value in the NVRAM for the transfer speed of your disk drive should very probably eliminate the negotiation noise (My guess is that your device is configured for 160 MB/s in the NVRAM that is far beyond the maximum possible for SE mode SCSI BUS - Max for SE Wide BUS is 40 MB/s ST). Btw, your ATLAS10K2 drive would perform better (faster and more reliably) on the LVD SCSI BUS. But may-be you had good reasons for putting it on a SE (Single Ended) SCSI BUS... Regards, G=E9rard. > sym0: <1010-33> port 0xc000-0xc0ff mem > 0xefffa000-0xefffbfff,0xeffff800-0xeffffbff irq 11 at device 13.0 on pci0 > sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking > sym0: handling phase mismatch from SCRIPTS. > sym0: open drain IRQ line driver, using on-chip SRAM > sym0: using LOAD/STORE-based firmware. > sym1: <1010-33> port 0xd000-0xd0ff mem > 0xefffc000-0xefffdfff,0xeffffc00-0xefffffff irq 11 at device 13.1 on pci0 > sym1: Symbios NVRAM, ID 7, Fast-80, SE, parity checking > sym1: handling phase mismatch from SCRIPTS. > sym1: open drain IRQ line driver, using on-chip SRAM > sym1: using LOAD/STORE-based firmware. > ... > > (noperiph:sym1:0:-1:-1): SCSI BUS reset detected. > (probe21:sym1:0:6:0): M_REJECT received (7:8). > (probe21:sym1:0:6:0): M_REJECT to send for: 1-6-4-c-0-3e-1-0. > Mounting root from ufs:/dev/da0s1a > da0 at sym1 bus 0 target 6 lun 0 > da0: 40.000MB/s transfers (20.000MHz, > offset 31, 16bit), Tagged Queueing Enabled > da0: 8759MB (17938985 512 byte sectors: 255H 63S/T 1116C) > da0: Fixed > Direct Access SCSI-3 device > da1 at sym1 bus 0 target 15 lun 0 > da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing > Enabled > da1: 8714MB (17847486 512 byte sectors: 255H 63S/T 1110C) > da1: Fixed Direct Access SCSI-4 device > > > Thank You. > > -- > > John R. Shannon > john@johnrshannon.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 28 15:37:59 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 238E837B41A for ; Thu, 28 Mar 2002 15:37:49 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g2SNbek24105; Thu, 28 Mar 2002 16:37:40 -0700 (MST) (envelope-from ken) Date: Thu, 28 Mar 2002 16:37:40 -0700 From: "Kenneth D. Merry" To: Lukas Ertl Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ciss driver and tagged queuing Message-ID: <20020328163740.A24032@panzer.kdm.org> References: <20020328152644.A23074@panzer.kdm.org> <20020328232901.L214-100000@korben.in.tern> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020328232901.L214-100000@korben.in.tern>; from l.ertl@univie.ac.at on Thu, Mar 28, 2002 at 11:35:01PM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Mar 28, 2002 at 23:35:01 +0100, Lukas Ertl wrote: > On Thu, 28 Mar 2002, Kenneth D. Merry wrote: > > > What RAID level are you using? There are significant differences (on the > > smart array controller at least) between the block read and write results. > > With the SCSI->IDE controller, oddly, the write results are faster than the > > read results. > > RAID5. I don't have a lot of experience with RAID, so I don't know if the > number of disks have an influence on the result (12 80GB IDE disks in the > SCSI/IDE array, 8 72GB disks in the Compaq array). That explains why the block read performance is faster than the write performance on the Smart Array controller. With RAID-5, you have to do parity calculation on writes, so they'll be somewhat slower, more so if the board doesn't have a hardware parity engine. That doesn't explain why writes are faster than reads on the other array. > > What does dmesg say about the card? From looking at the driver, it looks > > like the "max outstanding commands" value that is printed out on boot will > > tell us how many outstanding transactions the card claims to support. > > Ok: > > ciss1: port 0x3000-0x30ff mem > 0xf7e00000-0xf7efffff,0x > f7fc0000-0xf7ffffff irq 3 at device 4.0 on pci7 > ciss1: using 256 of 1024 available commands > ciss1: 1 logical drive configured > ciss1: firmware 1.76 > ciss1: 2 SCSI channels > ciss1: signature 'CISS' > ciss1: valence 1 > ciss1: supported I/O methods 0xe > ciss1: active I/O method 0x3 > ciss1: 4G page base 0x00000000 > ciss1: interrupt coalesce delay 1000us > ciss1: interrupt coalesce count 0 > ciss1: max outstanding commands 1024 > ciss1: bus types 0x2 > ciss1: server name '' > ciss1: heartbeat 0x20000022 > ciss1: 1 logical drive > ciss1: logical drive 0: RAID 5, 416768MB online Okay, it looks like you should be able to send at least 256 simultaneous commands. What does dmesg say about da1 (which I assume is the smart array device)? (might be faster to just send the full dmesg output) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 29 0:53:47 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mailbox.univie.ac.at (mailbox.univie.ac.at [131.130.1.27]) by hub.freebsd.org (Postfix) with ESMTP id 3355A37B41A for ; Fri, 29 Mar 2002 00:53:40 -0800 (PST) Received: from korben (mailboxts3-30.univie.ac.at [131.130.99.30]) by mailbox.univie.ac.at (8.12.2/8.12.2) with ESMTP id g2T8rEun143066; Fri, 29 Mar 2002 09:53:25 +0100 Date: Fri, 29 Mar 2002 09:53:02 +0100 (=?ISO-8859-1?Q?Westeurop=E4ische_Normalzeit?=) From: Lukas Ertl To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ciss driver and tagged queuing In-Reply-To: <20020328163740.A24032@panzer.kdm.org> Message-ID: X-X-Sender: le@mailbox.univie.ac.at MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 28 Mar 2002, Kenneth D. Merry wrote: > Okay, it looks like you should be able to send at least 256 simultaneous > commands. What does dmesg say about da1 (which I assume is the smart arr= ay > device)? (might be faster to just send the full dmesg output) Here you are: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-STABLE #0: Fri Mar 22 17:38:51 CET 2002 le@raidtest.univie.ac.at:/usr/obj/usr/src/sys/RAIDTEST Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1125772801 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1125.77-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x6b1 Stepping =3D 1 Features=3D0x383f9ff real memory =3D 1342160896 (1310704K bytes) avail memory =3D 1302265856 (1271744K bytes) pnpbios: Bad PnP BIOS data checksum Preloaded elf kernel "kernel" at 0xc02d2000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib1: on motherboard pci1: on pcib1 pcib0: on motherboard pci0: on pcib0 ciss0: port 0x2000-0x20ff mem 0xf5ef0000-0xf5ef3fff,0xf7 cc0000-0xf7cfffff irq 3 at device 1.0 on pci0 ciss0: using 256 of 1024 available commands ciss0: 1 logical drive configured ciss0: firmware 1.42 ciss0: 2 SCSI channels ciss0: signature 'CISS' ciss0: valence 1 ciss0: supported I/O methods 0xe ciss0: active I/O method 0x3 ciss0: 4G page base 0x00000000 ciss0: interrupt coalesce delay 1000us ciss0: interrupt coalesce count 16 ciss0: max outstanding commands 1024 ciss0: bus types 0x2 ciss0: server name '' ciss0: heartbeat 0x10000032 ciss0: 1 logical drive ciss0: logical drive 0: RAID 1, 16896MB online fxp0: port 0x2400-0x243f mem 0xf7b00000-0xf7bf ffff,0xf7cb0000-0xf7cb0fff irq 5 at device 2.0 on pci0 fxp0: Ethernet address 00:02:a5:f0:bd:02 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: port 0x2440-0x247f mem 0xf7900000-0xf79f ffff,0xf7af0000-0xf7af0fff irq 7 at device 4.0 on pci0 fxp1: Ethernet address 00:02:a5:f0:bd:01 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at 5.0 pci0: (vendor=3D0x0e11, dev=3D0xa0f0) at 6.0 irq 10 isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x2c00-0x2c0f at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 15.2 irq 11 pcib2: on motherboard pci2: on pcib2 pcib7: on motherboard pci7: on pcib7 ciss1: port 0x3000-0x30ff mem 0xf7e00000-0xf7efffff,0x f7fc0000-0xf7ffffff irq 3 at device 4.0 on pci7 ciss1: using 256 of 1024 available commands ciss1: 1 logical drive configured ciss1: firmware 1.76 ciss1: 2 SCSI channels ciss1: signature 'CISS' ciss1: valence 1 ciss1: supported I/O methods 0xe ciss1: active I/O method 0x3 ciss1: 4G page base 0x00000000 ciss1: interrupt coalesce delay 1000us ciss1: interrupt coalesce count 0 ciss1: max outstanding commands 1024 ciss1: bus types 0x2 ciss1: server name '' ciss1: heartbeat 0x20000022 ciss1: 1 logical drive ciss1: logical drive 0: RAID 5, 416768MB online pci7: (vendor=3D0x0e11, dev=3D0xa0f7) at 7.0 irq 15 eisa0: on motherboard mainboard0: on eisa0 slot 0 orm0: