From owner-freebsd-scsi Sun Mar 31 3:10: 5 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 A535937B41B; Sun, 31 Mar 2002 03:09:57 -0800 (PST) Received: from korben (mailboxts3-50.univie.ac.at [131.130.99.50]) by mailbox.univie.ac.at (8.12.2/8.12.2) with ESMTP id g2VB97bS116210; Sun, 31 Mar 2002 13:09:31 +0200 Date: Sun, 31 Mar 2002 13:08:45 +0200 (=?ISO-8859-1?Q?Westeurop=E4ische_Sommerzeit?=) From: Lukas Ertl To: Michael Smith Cc: "Kenneth D. Merry" , Subject: Re: ciss driver and tagged queuing In-Reply-To: <200203292216.g2TMGWN01304@mass.dis.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 Fri, 29 Mar 2002, Michael Smith wrote: > > The problem is that the inquiry data doesn't indicate that the arrays > > support tagged queueing, so you only get one tag at a time. > > The arrays don't support tagged queueing, but they do support multiple > outstanding commands. So is there anything I can do to improve performance? Or do I just have bad luck for now? Somehow I started to like the hardware, it seemed pretty robust at first glance :-) 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 Sun Mar 31 3:21:10 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 2DA5337B416; Sun, 31 Mar 2002 03:21:07 -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 g2VBK2c05032; Sun, 31 Mar 2002 03:20:03 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200203311120.g2VBK2c05032@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Lukas Ertl Cc: Michael Smith , "Kenneth D. Merry" , freebsd-scsi@freebsd.org Subject: Re: ciss driver and tagged queuing In-reply-to: Your message of "Sun, 31 Mar 2002 13:08:45 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Mar 2002 03:20:02 -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 > On Fri, 29 Mar 2002, Michael Smith wrote: > > > > The problem is that the inquiry data doesn't indicate that the arrays > > > support tagged queueing, so you only get one tag at a time. > > > > The arrays don't support tagged queueing, but they do support multiple > > outstanding commands. > > So is there anything I can do to improve performance? Or do I just have > bad luck for now? Somehow I started to like the hardware, it seemed pretty > robust at first glance :-) I'll try to come up with a patch, or you can look at the mly driver's CVS log when I made the change Ken refers to. Now that I recall it, it was a no-brainer so making a similar change to ciss(4) should be simple. -- 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 Sun Mar 31 12:18:21 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 7C15437B421; Sun, 31 Mar 2002 12:18:10 -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 g2VBK2c05032; Sun, 31 Mar 2002 03:20:03 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200203311120.g2VBK2c05032@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Lukas Ertl Cc: Michael Smith , "Kenneth D. Merry" , freebsd-scsi@freebsd.org Subject: Re: ciss driver and tagged queuing In-reply-to: Your message of "Sun, 31 Mar 2002 13:08:45 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Mar 2002 03:20:02 -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 > On Fri, 29 Mar 2002, Michael Smith wrote: > > > > The problem is that the inquiry data doesn't indicate that the arrays > > > support tagged queueing, so you only get one tag at a time. > > > > The arrays don't support tagged queueing, but they do support multiple > > outstanding commands. > > So is there anything I can do to improve performance? Or do I just have > bad luck for now? Somehow I started to like the hardware, it seemed pretty > robust at first glance :-) I'll try to come up with a patch, or you can look at the mly driver's CVS log when I made the change Ken refers to. Now that I recall it, it was a no-brainer so making a similar change to ciss(4) should be simple. -- 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 Apr 1 13:29:41 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id CA12437B417; Mon, 1 Apr 2002 13:29:33 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g31LT4939657; Mon, 1 Apr 2002 14:29:04 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200204012129.g31LT4939657@aslan.scsiguy.com> To: Michael Smith Cc: "Kenneth D. Merry" , Lukas Ertl , freebsd-scsi@FreeBSD.ORG Subject: Re: ciss driver and tagged queuing In-Reply-To: Your message of "Fri, 29 Mar 2002 14:16:32 PST." <200203292216.g2TMGWN01304@mass.dis.org> Date: Mon, 01 Apr 2002 14:29:04 -0700 From: "Justin T. Gibbs" 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 >The arrays don't support tagged queueing, but they do support multiple >outstanding commands. So then the boards aren't really emulating SCSI disks. 8-) Tagged queing is the only way to support multiple outstanding commands in SCSI. >I don't want to have to handle tags; I just want CAM to keep giving me >commands until I ask it to stop. 8) Don't you know in advance the maximum number of commands you can handle concurrently per-array and per-controller? If you do, you can just tell CAM the numbers and it will do what you request. If the limits are squishy, you have to freeze your device and/or sim queues when you hit hit a limit or perhaps simulate a queue full response if you are going to emulate tagged queuing. >One other complication is that the limit on outstanding commands is >per-adapter not per-array, so the automatic tag-backoff that CAM does >won't work correctly under load. I'm confused by this comment. CAM has both per-SIM and per-device limits and will round-robin resources amongst devices that share those resources when there is contention. The tag backoff is *per-device* not per controller. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 1 14: 7:53 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 8551837B416 for ; Mon, 1 Apr 2002 14:07:48 -0800 (PST) Received: from [192.168.1.129] (212.129.41.25) by mail.libertysurf.net (5.1.070) id 3C7EF02B0063E8B6; Tue, 2 Apr 2002 00:07:37 +0200 Date: Tue, 2 Apr 2002 01:07:56 +0200 (CEST) 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: <20020328042432.P19245@ace.ulyssis.org> Message-ID: <20020402005656.I2142-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, Stijn Opheide wrote: > On Tue, Mar 26, 2002 at 03:53:54AM +0100, G=E9rard 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 + 8= 95 > > + 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 th= e > > PCI bus seems wrong. The failure happens during some simple checkings > > performed at initialisation. The driver gets such address values from t= he > > kernel BUS handling software. > > > > Could you give a try with FreeBSD 4.3 and/or 4.4 installation and see i= f > > 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... Interesting. Some driver changes happen between 4.3 and 4.4, but they should have close to no effect since they address CAM new transfer settings that aren't available in 4.x (thus #ifed out). I just wanted to keep the source in sync with the main CVS branch. The best thing to try would be 4.5 + sym from 4.3, IMO, [and/or 4.3 + sym from 4.5]. Regards, G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 2 4: 7:52 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 1E39C37B417 for ; Tue, 2 Apr 2002 04:07:46 -0800 (PST) Received: from pablo.johnrshannon.com (pablo.johnrshannon.com [192.168.1.3]) by mail.johnrshannon.com (Postfix) with ESMTP id 77C2DE888 for ; Tue, 2 Apr 2002 05:07:40 -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 g32C7eUr002170 for ; Tue, 2 Apr 2002 05:07:40 -0700 (MST) (envelope-from john@pablo.johnrshannon.com) Received: (from john@localhost) by pablo.johnrshannon.com (8.12.2/8.12.1/Submit) id g32C7eJn002169 for freebsd-scsi@FreeBSD.ORG; Tue, 2 Apr 2002 05:07:40 -0700 (MST)?g (envelope-from john) Message-Id: <200204021207.g32C7eJn002169@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: AHC - Adaptec 39160 Date: Tue, 2 Apr 2002 05:07:40 -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 ahc0: ahc1: da0: Fixed Direct Access SCSI-3 device da1: Fixed Direct Access SCSI-4 device Are there any know problems with Adaptec 7899G based controllers with two disk drives on the same channel? Log extract follows: Apr 1 17:51:08 aslsystem /kernel: ahc1:A:15: parity error detected in DT Data-in phase. SEQADDR(0x1a3) SCSIRATE(0x0) Apr 1 18:36:01 aslsystem /kernel: Unexpected non-DT Data Phase Apr 1 18:36:01 aslsystem /kernel: ahc1:A:15: parity error detected in DT Data-in phase. SEQADDR(0x1a3) SCSIRATE(0x0) Apr 2 03:00:19 aslsystem /kernel: Unexpected non-DT Data Phase Apr 2 03:00:19 aslsystem /kernel: ahc1:A:15: parity error detected in DT Data-in phase. SEQADDR(0x1a3) SCSIRATE(0x0) Apr 2 03:00:19 aslsystem /kernel: ahc1:Arror detected in DT Data-in phase. SEQADDR(0x1a3) SCSIRATE(0x0) Apr 2 03:00:20 aslsystem /kernel: Unexpected non-DT Data Phase Apr 2 03:00:20 aslsystem /kernel: ahc1:A:15: parity error detected in DT Data-in phase. SEQADDR(0x1a3) SCSIRATE(0x0) Apr 2 03:00:21 aslsystem /kernel: Unexpected non-DT Data Phase Apr 2 03:00:21 aslsystem /kernel: ahc1:A:15: parity error detected in DT Data-in phase. SEQADDR(0x1a3) SCSIRATE(0x0) Apr 2 03:00:22 aslsystem /kernel: (da1:ahc1:0:15:0): Queuing a BDR SCB Apr 2 03:00:22 aslsystem /kernel: (da1:ahc1:0:15:0): SCB 0x74 - timed out Apr 2 03:00:22 aslsystem /kernel: (da1:ahc1:0:15:0): no longer in timeout, status = 34b Apr 2 03:00:22 aslsystem /kernel: ACCUM = 0x80, SINDEX = 0x81, DINDEX = 0x65, ARG_2 = 0x0 Apr 2 03:00:22 aslsystem /kernel: Card NEXTQSCB = 87 Apr 2 03:00:22 aslsystem /kernel: DFCNTRL = 0x0, DFSTATUS = 0x88 Apr 2 03:00:22 aslsystem /kernel: Disconnected Queue entries: 10:84 Apr 2 03:00:22 aslsystem /kernel: Disconnected Queue entries: 10:84 26:116 Apr 2 03:00:22 aslsystem /kernel: HCNT = 0x0 Apr 2 03:00:22 aslsystem /kernel: Kernel Free SCB list: 55 67 44 2 82 31 97 110 96 19 51 105 129 85 32 6 11 86 119 108 42 59 36 62 1 29 49 102 57 60 38 43 95 28 112 33 104 115 58 40 73 5 54 98 37 78 91 89 123 15 23 80 70 81 125 12 68 8 120 121 66 100 48 13 72 109 77 114 16 71 53 103 26 74 34 111 128 88 3 10 127 83 61 45 9 47 126 75 14 106 122 7 76 93 20 52 124 35 99 50 117 107 79 39 27 21 94 4 46 90 41 56 0 113 92 22 30 69 139 63 64 138 137 136 135 134 133 132 131 130 Apr 2 03:00:22 aslsystem /kernel: Kernel NEXTQSCB = 118 Apr 2 03:00:22 aslsystem /kernel: LASTPHASE = 0xe0, SCSISIGI = 0x74, SXFRCTL0 = 0x88 -- 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 Tue Apr 2 8:14:39 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id D6F5D37B496 for ; Tue, 2 Apr 2002 08:14:24 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g32GDj948010; Tue, 2 Apr 2002 09:13:45 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200204021613.g32GDj948010@aslan.scsiguy.com> To: john@johnrshannon.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AHC - Adaptec 39160 In-Reply-To: Your message of "Tue, 02 Apr 2002 05:07:40 MST." <200204021207.g32C7eJn002169@pablo.johnrshannon.com> Date: Tue, 02 Apr 2002 09:13:45 -0700 From: "Justin T. Gibbs" 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 >ahc0: >ahc1: >da0: Fixed Direct Access SCSI-3 device >da1: Fixed Direct Access SCSI-4 device > >Are there any know problems with Adaptec 7899G based controllers with two >disk drives on the same channel? No. >Log extract follows: > > >Apr 1 17:51:08 aslsystem /kernel: ahc1:A:15: parity error detected in DT >Data-in phase. SEQADDR(0x1a3) SCSIRATE(0x0) >Apr 1 18:36:01 aslsystem /kernel: Unexpected non-DT Data Phase You have a very sick bus. Have you tried replacing the cable(s) and verifying your termination? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 3 2:32: 7 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from bosvwl02.infy.com (bosvwl02.infy.com [216.52.49.36]) by hub.freebsd.org (Postfix) with SMTP id 3935337B405 for ; Wed, 3 Apr 2002 02:32:04 -0800 (PST) Received: from 192.168.200.82 by bosvwl02.infy.com (InterScan E-Mail VirusWall NT); Wed, 03 Apr 2002 05:31:22 -0500 Received: from BLRKECIMR01.ad.infosys.com ([192.168.200.58]) by INDHUBBHS02.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.4905); Wed, 3 Apr 2002 16:00:25 +0530 Received: from kecmsg02.ad.infosys.com ([192.168.18.90]) by BLRKECIMR01.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.4905); Wed, 3 Apr 2002 16:00:25 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: SCSI Callback function not getting called Date: Wed, 3 Apr 2002 16:00:24 +0530 Message-ID: <755FA95DB839D211856B0008C7287D930856282A@kecmsg02.ad.infosys.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: AHC - Adaptec 39160 Thread-Index: AcHaYZzGDSYLMTggS/elfotVjXdukQAlcBtA From: "Yassar S" To: X-OriginalArrivalTime: 03 Apr 2002 10:30:25.0411 (UTC) FILETIME=[91192D30:01C1DAFA] 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 All, =20 What needs to be done for the callback function to get called=20 after a SCSI operation through the SIM layer functions? Is it not enough to provide the callback function pointer to the scsi driver calls like scsi_read_write. Thanks Yassar. =20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 3 7:54:34 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 4469737B417 for ; Wed, 3 Apr 2002 07:54:30 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g33FsK871164; Wed, 3 Apr 2002 08:54:20 -0700 (MST) (envelope-from ken) Date: Wed, 3 Apr 2002 08:54:19 -0700 From: "Kenneth D. Merry" To: Yassar S Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI Callback function not getting called Message-ID: <20020403085419.A71134@panzer.kdm.org> References: <755FA95DB839D211856B0008C7287D930856282A@kecmsg02.ad.infosys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <755FA95DB839D211856B0008C7287D930856282A@kecmsg02.ad.infosys.com>; from yassars@infy.com on Wed, Apr 03, 2002 at 04:00:24PM +0530 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 Wed, Apr 03, 2002 at 16:00:24 +0530, Yassar S wrote: > Hi All, > > What needs to be done for the callback function to get called > after a SCSI operation through the SIM layer functions? > > Is it not enough to provide the callback function pointer > to the scsi driver calls like scsi_read_write. If you're writing a driver, you need to call xpt_done() for the CCB once the transaction has completed. Look in src/sys/dev/aic7xxx/aic7xxx_freebsd.c for examples on how command queueing and completion works in SIMs. 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 Wed Apr 3 19:46: 7 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from bosvwl02.infy.com (bosvwl02.infy.com [216.52.49.36]) by hub.freebsd.org (Postfix) with SMTP id 76F7037B416 for ; Wed, 3 Apr 2002 19:46:04 -0800 (PST) Received: from 192.168.200.81 by bosvwl02.infy.com (InterScan E-Mail VirusWall NT); Wed, 03 Apr 2002 22:45:22 -0500 Received: from BLRKECIMR01.ad.infosys.com ([192.168.200.58]) by indhubbhs01.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.4905); Thu, 4 Apr 2002 09:15:26 +0530 Received: from kecmsg02.ad.infosys.com ([192.168.18.90]) by BLRKECIMR01.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.4905); Thu, 4 Apr 2002 09:15:26 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: SCSI Callback function not getting called Date: Thu, 4 Apr 2002 09:15:25 +0530 Message-ID: <755FA95DB839D211856B0008C7287D930F3286DC@kecmsg02.ad.infosys.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SCSI Callback function not getting called Thread-Index: AcHbJ99PsbNhXb9GRGWAen08gLsLqAAYxW4g From: "Yassar S" To: "Kenneth D. Merry" Cc: X-OriginalArrivalTime: 04 Apr 2002 03:45:26.0610 (UTC) FILETIME=[284C2320:01C1DB8B] 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 I'm not writing a driver. I'm writing an application which uses the SIM calls like scsi_read_write etc. -Yassar. -----Original Message----- From: Kenneth D. Merry [mailto:ken@kdm.org] Sent: Wednesday, April 03, 2002 9:24 PM To: Yassar S Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI Callback function not getting called On Wed, Apr 03, 2002 at 16:00:24 +0530, Yassar S wrote: > Hi All, > =20 > What needs to be done for the callback function to get called=20 > after a SCSI operation through the SIM layer functions? >=20 > Is it not enough to provide the callback function pointer > to the scsi driver calls like scsi_read_write. If you're writing a driver, you need to call xpt_done() for the CCB once the transaction has completed. Look in src/sys/dev/aic7xxx/aic7xxx_freebsd.c for examples on how = command queueing and completion works in SIMs. Ken --=20 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 Wed Apr 3 21:49:23 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 8EBEF37B400 for ; Wed, 3 Apr 2002 21:49:19 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g345n9576999; Wed, 3 Apr 2002 22:49:09 -0700 (MST) (envelope-from ken) Date: Wed, 3 Apr 2002 22:49:08 -0700 From: "Kenneth D. Merry" To: Yassar S Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI Callback function not getting called Message-ID: <20020403224908.A76900@panzer.kdm.org> References: <755FA95DB839D211856B0008C7287D930F3286DC@kecmsg02.ad.infosys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <755FA95DB839D211856B0008C7287D930F3286DC@kecmsg02.ad.infosys.com>; from yassars@infy.com on Thu, Apr 04, 2002 at 09:15:25AM +0530 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, Apr 04, 2002 at 09:15:25 +0530, Yassar S wrote: > I'm not writing a driver. I'm writing an application which uses > the SIM calls like scsi_read_write etc. Those aren't SIM calls. The SIM layer (SIM == System Interface Module) is the layer where the various SCSI and FC drivers live. Functions like scsi_read_write() fill CCBs, they don't actually execute any I/O. You probably want to look at the cam(3) man page, and in particular you'll want to look at the camcontrol(8) source, located in src/sbin/camcontrol. That's probably the best example of how to issue SCSI commands from userland. The short answer to your original question is: scsi_read_write() and the other commands like it just fill CCBs, they don't actually execute I/O. In addition, the callback function pointer is only used in the kernel, not in userland. In userland, CCBs are currently issued synchronously, so there is no need for a callback function anyway. 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 Apr 4 9:38:38 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by hub.freebsd.org (Postfix) with ESMTP id A445437B420; Thu, 4 Apr 2002 09:38:13 -0800 (PST) Received: from localhost.localdomain (earth.hub.org [64.49.215.11]) by localhost (Postfix) with ESMTP id 2FCD010350B; Thu, 4 Apr 2002 13:38:07 -0400 (AST) Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by earth.hub.org (Postfix) with ESMTP id CD574103506; Thu, 4 Apr 2002 13:38:06 -0400 (AST) Date: Thu, 4 Apr 2002 13:38:06 -0400 (AST) From: "Marc G. Fournier" To: freebsd-questions@freebsd.org Cc: freebsd-scsi@freebsd.org, Subject: IBM eSeries 440 Server(s) ... Message-ID: <20020404133537.W20291-100000@mail1.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 looking at picking up one of the above to replace one of our older machines ... plan on starting with just 2xXeon1400CPU and 4Gig of RAM, but moving up to the full 8+32 as budget allows for it ... has anyone played with one of these with FreeBSD? Has there been any work done on the onboard SCSI controller? SMP work well on these? any caveats against them? Thanks ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 4 13:32:11 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.mirapoint.com (mail.mirapoint.com [63.107.133.18]) by hub.freebsd.org (Postfix) with ESMTP id 85B2037B420 for ; Thu, 4 Apr 2002 13:32:04 -0800 (PST) Received: from mail.mirapoint.com (localhost.mirapoint.com [127.0.0.1]) by mail.mirapoint.com (Mirapoint Messaging Server MOS 3.1.1.31) with SMTP id APW11519 (AUTH cer); Thu, 4 Apr 2002 13:32:03 -0800 (PST) Message-Id: <200204042132.APW11519@mail.mirapoint.com> Received: from 192.168.10.83 by mail.mirapoint.com (Mirapoint Messaging Server MOS 3.1.1.31) with HTTPS/1.1; Thu, 4 Apr 2002 13:35:00 -0800 Date: Thu, 4 Apr 2002 13:35:00 -0800 From: Carl Reisinger Subject: Any ideas what the following ahc errors mean? To: freebsd-scsi@freebsd.org Reply-To: cer@mirapoint.com X-Mailer: Mirapoint Webmail Direct 3.1.1.31 MIME-Version: 1.0 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 I am running FreeBSD 4.1-stable. The motherboard is a Intel STL2 with a 1.4GHz processor. On-board is a Adaptec AIC 7899G chipset, the channel being used is channel A of that chipset. The SCSI bus has three devices a StorageTek L40 (robotics), Quantum DLT8000 and a Seagate Viper 200 (LTO). Bus length is about 10 feet. I have been writting massive amounts of data to both drives until I hit the physical EOM, but just writting and have not seen any problems (of course the filemarks do not get written and the close returns a ENXIO error, but this is to be expected). Until this test I just closed the devices and started again. Now I am writting 128 KB records (yes, this required a change to the driver) to the LTO until I reach logical EOM (the first time a ENOSPC gets returned). I then issue a MTREW with the following results: 2002 Apr 04 15:17:27 rd12 /kernel: ahc0:A:2: no active SCB for reconnecting targ et - issuing BUS DEVICE RESET 2002 Apr 04 15:17:27 rd12 /kernel: SAVED_SCSIID == 0x27, SAVED_LUN == 0x0, ARG_1 == 0xff ACCUM = 0x80 2002 Apr 04 15:17:27 rd12 /kernel: SEQ_FLAGS == 0x0, SCBPTR == 0x0, BTT == 0xff, SINDEX == 0x31 2002 Apr 04 15:17:27 rd12 /kernel: SCSIID == 0x0, SCB_SCSIID == 0x27, SCB_LUN == 0x0, SCB_TAG == 0xff, SCB_CONTROL == 0x40 2002 Apr 04 15:17:27 rd12 /kernel: SCSIBUSL == 0x0, SCSISIGI == 0xc6 2002 Apr 04 15:17:27 rd12 /kernel: SXFRCTL0 == 0x88 2002 Apr 04 15:17:27 rd12 /kernel: SEQCTL == 0x10 2002 Apr 04 15:17:27 rd12 /kernel: ahc0: Dumping Card State at SEQADDR 0x1a8 2002 Apr 04 15:17:27 rd12 /kernel: SCSISEQ = 0x12, SBLKCTL = 0xa, SSTAT0 0x2 2002 Apr 04 15:17:27 rd12 /kernel: SCB count = 20 2002 Apr 04 15:17:27 rd12 /kernel: Kernel NEXTQSCB = 14 2002 Apr 04 15:17:27 rd12 /kernel: Card NEXTQSCB = 14 2002 Apr 04 15:17:27 rd12 /kernel: QINFIFO entries: 2002 Apr 04 15:17:27 rd12 /kernel: Waiting Queue entries: 2002 Apr 04 15:17:27 rd12 /kernel: Disconnected Queue entries: 2002 Apr 04 15:17:27 rd12 /kernel: QOUTFIFO entries: 2002 Apr 04 15:17:27 rd12 /kernel: Sequencer Free SCB List: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 2002 Apr 04 15:17:27 rd12 /kernel: Pending list: 2002 Apr 04 15:17:27 rd12 /kernel: Kernel Free SCB list: 9 8 7 15 16 17 18 19 0 1 2 3 4 5 6 13 12 11 10 2002 Apr 04 15:17:27 rd12 /kernel: ahc0: Bus Device Reset on A:2. 0 SCBs aborted I have the EOTMODEL set to 1 filemark. Interesting note: it appears the tape is not being rewound. If I issue a read after the ioctl returns the drive issues a CONDITION CHECK with a sense key of 8 and asc/ascq of 0/5. Which is a BLANK CHECK (EOD encountered). Anyone have an idea? Carl Reisinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 4 15:51:11 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 60B0837B41B for ; Thu, 4 Apr 2002 15:51:06 -0800 (PST) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id g34Np5f81355 for ; Thu, 4 Apr 2002 15:51:05 -0800 (PST) (envelope-from mjacob@feral.com) Date: Thu, 4 Apr 2002 15:51:05 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: freebsd-scsi@freebsd.org Subject: a somewhat major QLogic Driver Change for Fibre Channel Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 A major change just went into the QLogic FC driver in how it evaluates fabric membership. In short, GA_NXT is no longer used. Instead, GID_FT builds a list of Port IDs and for each one GPN_ID/GNN_ID are run to get Port/Node WWNs. A tighter auditting of FS_ACC/FS_RJT is made. So, for all of you out there with Brocade 3.0 f/w that use zoning- the isp driver should start working for you again. Ahem. If there is anyone this list who this applies to. You can go back to the old behaviour by uncommenting the line in ispvar.h that is: /* #define ISP_USE_GA_NXT 1 */ /* Use GA_NXT with switches */ -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 5 0:52: 7 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from s096-n062.tele2.cz (s096-n062.tele2.cz [213.246.96.62]) by hub.freebsd.org (Postfix) with ESMTP id 1743037B419; Fri, 5 Apr 2002 00:51:55 -0800 (PST) Received: from localhost (plusik@localhost) by s096-n062.tele2.cz (8.11.6/8.11.6) with ESMTP id g358pmR00371; Fri, 5 Apr 2002 10:51:48 +0200 (CEST) (envelope-from plusik@pohoda.cz) X-Authentication-Warning: s096-n062.tele2.cz: plusik owned process doing -bs Date: Fri, 5 Apr 2002 10:51:48 +0200 (CEST) From: Tomas Pluskal X-X-Sender: plusik@s096-n062.tele2.cz To: freebsd-scsi@freebsd.org, Subject: umass0: BBB reset failed, TIMEOUT Message-ID: <20020405104357.K305-100000@s096-n062.tele2.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I am trying to connect a nikon 775 camera via USB. When I plug it in BEFORE I boot the kernel, it works ok (it detects da0 and I can mount it). When I plug it when system is already up, it doesn't work. It detects umass0 (umass0: NIKON NIKON DSC E775, rev 1.10/1.00, addr 2), but it doesn't attach it to da0 and in dmesg I see: umass0: BBB reset failed, TIMEOUT umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR about 10 times... I have all drivers compiled in kernel (no modules), I've been searching throught lists, but I found only similar problem reports (with different USB devices), but no solution. Is there any ? Thanks Tomas Pluskal -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8rWWkqlO9Q2aZisoRAr1tAJ9DyAw2eaYP+7390ALLSZpW062DEACfTIwf GLZu0RxwOFE5KcELlKlLelg= =3hJh -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 5 8:57:55 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by hub.freebsd.org (Postfix) with ESMTP id C77C337B417; Fri, 5 Apr 2002 08:57:49 -0800 (PST) Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id 5BD19943A; Fri, 5 Apr 2002 09:57:49 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.cos.agilent.com (Postfix) with ESMTP id E9BF7332; Fri, 5 Apr 2002 09:57:48 -0700 (MST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_22672)/8.9.3 SMKit7.1.1_Agilent) with ESMTP id IAA09787; Fri, 5 Apr 2002 08:57:48 -0800 (PST) Message-Id: <200204051657.IAA09787@mina.soco.agilent.com> To: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: umass0: BBB reset failed, TIMEOUT Reply-To: Darryl Okahata In-Reply-To: Your message of "Fri, 05 Apr 2002 10:51:48 +0200." <20020405104357.K305-100000@s096-n062.tele2.cz> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Fri, 05 Apr 2002 08:57:46 -0800 From: Darryl Okahata 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 Tomas Pluskal wrote: > When I plug it when system is already up, it doesn't work. It detects > umass0 (umass0: NIKON NIKON DSC E775, rev 1.10/1.00, addr 2), but it > doesn't attach it to da0 and in dmesg I see: > umass0: BBB reset failed, TIMEOUT When I got this message with my USB hard disk, I was able to fix it by upgrading to FreeBSD-STABLE; you can read about my saga in: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=284919+0+archive/2002/freebsd-stable/20020331.freebsd-stable -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 5 10:29: 1 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from s096-n062.tele2.cz (s096-n062.tele2.cz [213.246.96.62]) by hub.freebsd.org (Postfix) with ESMTP id E7F5337B41B; Fri, 5 Apr 2002 10:28:55 -0800 (PST) Received: from localhost (plusik@localhost) by s096-n062.tele2.cz (8.11.6/8.11.6) with ESMTP id g35ISkK00240; Fri, 5 Apr 2002 20:28:47 +0200 (CEST) (envelope-from plusik@pohoda.cz) X-Authentication-Warning: s096-n062.tele2.cz: plusik owned process doing -bs Date: Fri, 5 Apr 2002 20:28:46 +0200 (CEST) From: Tomas Pluskal X-X-Sender: plusik@s096-n062.tele2.cz To: darrylo@soco.agilent.com Cc: freebsd-scsi@FreeBSD.ORG, Subject: Re: umass0: BBB reset failed, TIMEOUT Message-ID: <20020405202418.J216-100000@s096-n062.tele2.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > When I got this message with my USB hard disk, I was able to fix it > by upgrading to FreeBSD-STABLE; you can read about my saga in: > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=284919+0+archive/2002/freebsd-stable/20020331.freebsd-stable > Darryl Okahata Thanks for your help, I just tried to compile FreeBSD-STABLE kernel, and the result is.... still the same :) Perhaps USB hard disks are treated in a different way than USB Cameras, but it's strange (both use umass protocol). bye Tomas Pluskal -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8rezeqlO9Q2aZisoRApeXAJ9t6uVRhy+kGCtywMqmh8PIKQyn+ACfY0GF ANRRTUORXa2LCMSCWRBRd8g= =eTjT -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 5 10:51:40 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by hub.freebsd.org (Postfix) with ESMTP id 451E437B405; Fri, 5 Apr 2002 10:51:34 -0800 (PST) Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id D7E75DA65; Fri, 5 Apr 2002 11:51:33 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.cos.agilent.com (Postfix) with ESMTP id 3B523332; Fri, 5 Apr 2002 11:51:33 -0700 (MST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_22672)/8.9.3 SMKit7.1.1_Agilent) with ESMTP id KAA21431; Fri, 5 Apr 2002 10:51:32 -0800 (PST) Message-Id: <200204051851.KAA21431@mina.soco.agilent.com> To: Tomas Pluskal Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: umass0: BBB reset failed, TIMEOUT Reply-To: Darryl Okahata In-Reply-To: Your message of "Fri, 05 Apr 2002 20:28:46 +0200." <20020405202418.J216-100000@s096-n062.tele2.cz> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Fri, 05 Apr 2002 10:51:31 -0800 From: Darryl Okahata 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 [ -scsi removed, because this doesn't really belong there. ] Tomas Pluskal wrote: > Thanks for your help, I just tried to compile FreeBSD-STABLE kernel, and > the result is.... still the same :) Did you also do an installworld/mergemaster? I'm not sure that a new kernel is enough. I assume that you just did the upgrade, as there were some new USB fixes added a day or two ago. > Perhaps USB hard disks are treated in a different way than USB Cameras, > but it's strange (both use umass protocol). If you're really brave, you can turn on USB kernel debugging (UMASS_DEBUG, among possible others), but you may have to write a C program, in addition to rebuilding the kernel. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message