From owner-freebsd-scsi Sun Nov 7 3:58: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7CE4C14F9A; Sun, 7 Nov 1999 03:57:52 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p07-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.136]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id UAA19857; Sun, 7 Nov 1999 20:57:13 +0900 (JST) Message-ID: <38256738.C826C9FF@newsguy.com> Date: Sun, 07 Nov 1999 20:49:12 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Geoff Buckingham Cc: "Kenneth D. Merry" , "Gandalf T. Grey" , freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: 2nd Query: Is someone 'camifying' ncv0 scsi? References: <19991105233303.83205.qmail@hotmail.com> <199911052351.QAA02229@panzer.kdm.org> <19991106112310.A39348@chuggalug.clues.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Geoff Buckingham wrote: > > ALPHA DATA AD-PCS201 OK nin *14 > CyQ've SFC-201 OK nin *14 > IO DATA PCSC-F OK nin *14 > Pioneer PCP-PR24 OK nin *14 > > stg is a future domain card, nin and spc are a mystery to me. What does the *14 refers to? I own an IO DATA PCSC-F UltraSMIT and I'll be porting the nin driver to -current as soon as I can find time. (The cis for it says Ninja SCSI-3, btw.) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 7 3:59:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.powertech.no (intentia.powertech.no [195.159.0.220]) by hub.freebsd.org (Postfix) with ESMTP id CCD2214C02 for ; Sun, 7 Nov 1999 03:59:32 -0800 (PST) (envelope-from shamz@login1.powertech.no) Received: from login1.powertech.no (IDENT:root@login1.powertech.no [195.159.0.151]) by mail.powertech.no (8.9.3/8.8.5) with ESMTP id OAA30143; Sun, 7 Nov 1999 14:04:54 +0100 Received: (from shamz@localhost) by login1.powertech.no (8.9.3/8.9.3) id MAA21311; Sun, 7 Nov 1999 12:59:30 +0100 Date: Sun, 7 Nov 1999 12:59:30 +0100 From: Shaun Jurrens To: "Justin T. Gibbs" Cc: scsi@freebsd.org Subject: Re: scsi bus errors Message-ID: <19991107125930.A20165@shamz.net> References: <19991105120951.C1083@shamz.net> <199911051943.MAA69413@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: <199911051943.MAA69413@narnia.plutotech.com>; from Justin T. Gibbs on Fri, Nov 05, 1999 at 12:43:02PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Nov 05, 1999 at 12:43:02PM -0700, Justin T. Gibbs wrote: #> In article <19991105120951.C1083@shamz.net> you wrote: #> #> [ #> I've reformatted your mail so it fits in 80 columns. This makes #> it much easier to read. #> ] sorry, forgot to import my nexrc to this acct #> #> > Hi, #> > #> > After reading the lists and trying about everything under the sun #> > to get the errors to abate, I am finally writing. The setup is #> > about the same as all the others with SCB timeout errors. #> #> ... #> #> > I left out the logs because they don't seem to have been more than #> > grounds for speculation about termination and such up until now. #> #> As far as I know, we've resolved all other "timeout" type errors #> with the ahc driver. This was only possible because the people #> having the problems gave detailed information about their setup #> and the errors that occurred. In other words, provide the output #> from 'dmesg' for the system having problems as well as the messages #> output by the driver when the errors occur and we'll see what we #> can do. Leave the determination of what is valuable information #> to the experts. #> #> -- #> Justin Well then let's begin with dmesg: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.3-STABLE #0: Sun Oct 24 17:54:31 CEST 1999 root@dakota.shamz.net:/usr/src/sys/compile/DAKOTA Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 350797513 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bf AMD Features=0x80000800 real memory = 67108864 (65536K bytes) avail memory = 61997056 (60544K bytes) Preloaded elf kernel "kernel" at 0xc0312000. Probing for devices on PCI bus 0: chip0: rev 0x04 on pci0.0.0 chip1: rev 0x00 on pci0.1.0 chip2: rev 0x41 on pci0.7.0 chip3: rev 0x10 on pci0.7.3 ahc0: rev 0x03 int a irq 9 on pci0.8.0 ahc0: aic7870 Wide Channel A, SCSI Id=7, 16/255 SCBs vga0: rev 0x03 int a irq 10 on pci0.9.0 rl0: rev 0x10 int a irq 11 on pci0.10.0 rl0: Ethernet address: 00:e0:7d:01:00:99 rl0: autoneg complete, link status good (half-duplex, 10Mbps) Probing for devices on PCI bus 1: Probing for PnP devices: CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] This is a Vibra16X, but LDN 0 is disabled Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 flags 0x10 on isa sio1: type 16550A atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 ppc0 at 0x378 irq 7 on isa ppc0: Winbond chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppb0: IEEE1284 device found /ECP Probing for PnP devices on ppbus0: ppbus0: MEDIA lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pcm0 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in npx0 on motherboard npx0: INT 16 interface vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default IP Filter: initialized. Default = pass all, Logging = enabled Waiting 8 seconds for SCSI devices to settle da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 16.128MB/s transfers (8.064MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4101MB (8399520 512 byte sectors: 255H 63S/T 522C) da2 at ahc0 bus 0 target 9 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 16.128MB/s transfers (8.064MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 1075MB (2203480 512 byte sectors: 255H 63S/T 137C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 1010MB (2069860 512 byte sectors: 64H 32S/T 1010C) cd0 at ahc0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.629MB/s transfers (4.629MHz, offset 8) cd0: cd present [105372 x 2048 byte records] cd9660: Joliet Extension rl0: selecting MII, 10Mbps, half duplex As you can see, i have tried to take the transfer speed down between the controler and the quantum drives, but that did not result in any noticeable reduction in errors (as suggested in the man page). I am currently trying to retrieve the drive specs to check the jumpers on all drives once again, just to be sure and have retrieved a new bios for my fic board, after i noticed that at least one other had the same board as I do. BTW, i am still not on the list. I'm working on that too, but the machine crashed this morning, so now I have to get this hardware problem taken care of first. A few console errors too, just for length and completeness... Oct 3 19:03:34 dakota /kernel: (da2:ahc0:0:9:0): Queuing a BDR SCB Oct 3 19:03:34 dakota /kernel: (da2:ahc0:0:9:0): Bus Device Reset Message Sent Oct 3 19:03:34 dakota /kernel: (da2:ahc0:0:9:0): no longer in timeout, status = 34b Oct 3 19:03:34 dakota /kernel: ahc0: Bus Device Reset on A:9. 3 SCBs aborted Oct 4 21:40:03 dakota /kernel: (da2:ahc0:0:9:0): data overrun detected in Data- In phase. Tag == 0x45. Oct 4 21:40:03 dakota /kernel: (da2:ahc0:0:9:0): Have seen Data Phase. Length = 40960. NumSGs = 10. Oct 4 21:40:03 dakota /kernel: sg[0] - Addr 0x2735000 : Length 4096 Oct 4 21:40:03 dakota /kernel: sg[1] - Addr 0x1d36000 : Length 4096 Oct 4 21:40:03 dakota /kernel: sg[2] - Addr 0x3d77000 : Length 4096 Oct 4 21:40:03 dakota /kernel: sg[3] - Addr 0x2878000 : Length 4096 Oct 4 21:40:03 dakota /kernel: sg[4] - Addr 0x2179000 : Length 4096 Oct 4 21:40:03 dakota /kernel: sg[5] - Addr 0x2eba000 : Length 4096 Oct 4 21:40:03 dakota /kernel: sg[6] - Addr 0x113b000 : Length 4096 Oct 4 21:40:03 dakota /kernel: sg[7] - Addr 0x243c000 : Length 4096 Oct 4 21:40:03 dakota /kernel: sg[8] - Addr 0x39fd000 : Length 4096 Oct 4 21:47:34 dakota /kernel: pid 808 (navigator-4.61.b), uid 1002: exited on signal 10 here, it obviously killed netscape, but that's not hard Oct 8 12:56:35 dakota /kernel: (da2:ahc0:0:9:0): data overrun detected in Data- Out phase. Tag == 0x1a. Oct 8 12:56:35 dakota /kernel: (da2:ahc0:0:9:0): Have seen Data Phase. Length = 8192. NumSGs = 2. Oct 8 12:56:35 dakota /kernel: sg[0] - Addr 0x3075000 : Length 4096 Oct 9 21:03:04 dakota mountd[143]: mount request succeeded from 192.168.0.17 fo r /usr/local/public/root/midge Oct 9 21:28:07 dakota /kernel: (da1:ahc0:0:1:0): data overrun detected in Data- Out phase. Tag == 0x21. Oct 9 21:28:07 dakota /kernel: (da1:ahc0:0:1:0): Have seen Data Phase. Length = 8192. NumSGs = 2. Oct 9 21:28:07 dakota /kernel: sg[0] - Addr 0x1d89000 : Length 4096 Oct 9 21:29:03 dakota /kernel: (da1:ahc0:0:1:0): SCB 0x2c - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0xb Oct 9 21:29:03 dakota /kernel: (da1:ahc0:0:1:0): Queuing a BDR SCB Oct 9 21:29:03 dakota /kernel: (da1:ahc0:0:1:0): Bus Device Reset Message Sent Oct 9 21:29:03 dakota /kernel: (da1:ahc0:0:1:0): no longer in timeout, status = 34b Oct 9 21:29:03 dakota /kernel: ahc0: Bus Device Reset on A:1. 10 SCBs aborted Oct 9 21:29:31 dakota /kernel: (da1:ahc0:0:1:0): data overrun detected in Data- Out phase. Tag == 0x21. Oct 9 21:29:31 dakota /kernel: (da1:ahc0:0:1:0): Have seen Data Phase. Length = 8192. NumSGs = 2. Oct 9 21:29:31 dakota /kernel: sg[0] - Addr 0xeb5000 : Length 4096 Oct 9 21:31:22 dakota /kernel: (da1:ahc0:0:1:0): data overrun detected in Data- Out phase. Tag == 0xf0. Oct 9 21:31:22 dakota /kernel: (da1:ahc0:0:1:0): Have seen Data Phase. Length = 8192. NumSGs = 2. Oct 9 21:31:22 dakota /kernel: sg[0] - Addr 0x2cdd000 : Length 4096 Oct 9 21:34:43 dakota /kernel: (da2:ahc0:0:9:0): data overrun detected in Data- In phase. Tag == 0x23. Oct 9 21:34:43 dakota /kernel: (da2:ahc0:0:9:0): Have seen Data Phase. Length = 8192. NumSGs = 2. Oct 9 21:34:43 dakota /kernel: sg[0] - Addr 0x3e86000 : Length 4096 Oct 9 21:42:59 dakota /kernel: pid 45161 (ld), uid 0: exited on signal 11 (core dumped) this was not nice. Oct 12 02:06:20 dakota /kernel: (da1:ahc0:0:1:0): data overrun detected in Data- In phase. Tag == 0x26. Oct 12 02:06:20 dakota /kernel: (da1:ahc0:0:1:0): Have seen Data Phase. Length = 1024. NumSGs = 1. Oct 12 07:43:27 dakota /kernel: (da2:ahc0:0:9:0): SCB 0xa - timed out while idle , LASTPHASE == 0x1, SEQADDR == 0xc Oct 12 07:43:35 dakota /kernel: (da2:ahc0:0:9:0): Queuing a BDR SCB Oct 12 07:43:35 dakota /kernel: (da2:ahc0:0:9:0): Bus Device Reset Message Sent Oct 12 07:43:35 dakota /kernel: (da2:ahc0:0:9:0): no longer in timeout, status = 34b Oct 12 07:43:35 dakota /kernel: ahc0: Bus Device Reset on A:9. 1 SCBs aborted Oct 12 07:44:27 dakota /kernel: (da1:ahc0:0:1:0): SCB 0x9 - timed out while idle , LASTPHASE == 0x1, SEQADDR == 0x9 Oct 12 07:44:27 dakota /kernel: (da1:ahc0:0:1:0): Queuing a BDR SCB Oct 12 07:44:27 dakota /kernel: (da1:ahc0:0:1:0): Bus Device Reset Message Sent Oct 12 07:44:27 dakota /kernel: (da1:ahc0:0:1:0): no longer in timeout, status = 34b Oct 12 07:44:27 dakota /kernel: ahc0: Bus Device Reset on A:1. 7 SCBs aborted Oct 12 07:45:00 dakota /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET Oct 12 07:45:00 dakota /kernel: SAVED_TCL == 0x10, ARG_1 == 0x6, SEQ_FLAGS == 0x 40 Oct 12 07:45:00 dakota /kernel: ahc0: Bus Device Reset on A:1. 13 SCBs aborted Oct 12 07:45:27 dakota /kernel: (da2:ahc0:0:9:0): SCB 0x11 - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0x9 Oct 12 07:45:35 dakota /kernel: (da2:ahc0:0:9:0): Queuing a BDR SCB Oct 12 07:45:35 dakota /kernel: (da2:ahc0:0:9:0): Bus Device Reset Message Sent Oct 12 07:45:35 dakota /kernel: (da2:ahc0:0:9:0): no longer in timeout, status = 34b Oct 12 07:45:35 dakota /kernel: ahc0: Bus Device Reset on A:9. 3 SCBs aborted Oct 12 07:49:58 dakota /kernel: pid 27230 (cc), uid 0: exited on signal 11 (core dumped) again, not very nice when you're compiling Oct 18 21:31:25 dakota /kernel: (da2:ahc0:0:9:0): data overrun detected in Data- Out phase. Tag == 0x2. Oct 18 21:31:25 dakota /kernel: (da2:ahc0:0:9:0): Have seen Data Phase. Length = 8192. NumSGs = 2. Oct 18 21:31:25 dakota /kernel: sg[0] - Addr 0x287b000 : Length 4096 Oct 21 22:02:16 dakota /kernel: (da2:ahc0:0:9:0): data overrun detected in Data- Out phase. Tag == 0x3e. Oct 21 22:02:16 dakota /kernel: (da2:ahc0:0:9:0): Have seen Data Phase. Length = 8192. NumSGs = 2. Oct 21 22:02:16 dakota /kernel: sg[0] - Addr 0x2a01000 : Length 4096 Oct 22 02:08:04 dakota /kernel: ahc0:A:9: ahc_intr - referenced scb not valid du ring seqint 0x71 scb(36) Oct 22 02:09:12 dakota /kernel: ahc0: WARNING no command for scb 36 (cmdcmplt) Oct 22 02:09:12 dakota /kernel: QOUTPOS = 102 Oct 22 02:09:12 dakota /kernel: (da2:ahc0:0:9:0): SCB 0x14 - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0x9 Oct 22 02:09:12 dakota /kernel: (da2:ahc0:0:9:0): Queuing a BDR SCB Oct 22 02:09:12 dakota /kernel: (da2:ahc0:0:9:0): Bus Device Reset Message Sent Oct 22 02:09:12 dakota /kernel: (da2:ahc0:0:9:0): no longer in timeout, status = 34b Oct 22 02:09:12 dakota /kernel: ahc0: Bus Device Reset on A:9. 2 SCBs aborted Oct 22 09:40:29 dakota /kernel: (da2:ahc0:0:9:0): data overrun detected in Data- Out phase. Tag == 0x6. Oct 22 09:40:29 dakota /kernel: (da2:ahc0:0:9:0): Have seen Data Phase. Length = 8192. NumSGs = 2. and so on ad infinitum. an avg. of two per day under minimum load. Sorry this got so long and I hope the formatting worked. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 7 4:13:13 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 5358A14DA0; Sun, 7 Nov 1999 04:12:57 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id MAA43448; Sun, 7 Nov 1999 12:12:48 GMT (envelope-from geoffb) Date: Sun, 7 Nov 1999 12:12:48 +0000 From: Geoff Buckingham To: "Daniel C. Sobral" Cc: "Kenneth D. Merry" , "Gandalf T. Grey" , freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: 2nd Query: Is someone 'camifying' ncv0 scsi? Message-ID: <19991107121248.A42869@chuggalug.clues.com> References: <19991105233303.83205.qmail@hotmail.com> <199911052351.QAA02229@panzer.kdm.org> <19991106112310.A39348@chuggalug.clues.com> <38256738.C826C9FF@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38256738.C826C9FF@newsguy.com>; from Daniel C. Sobral on Sun, Nov 07, 1999 at 08:49:12PM +0900 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Nov 07, 1999 at 08:49:12PM +0900, Daniel C. Sobral wrote: > Geoff Buckingham wrote: > > > > ALPHA DATA AD-PCS201 OK nin *14 > > CyQ've SFC-201 OK nin *14 > > IO DATA PCSC-F OK nin *14 > > Pioneer PCP-PR24 OK nin *14 > > > > stg is a future domain card, nin and spc are a mystery to me. > > What does the *14 refers to? I own an IO DATA PCSC-F UltraSMIT and > I'll be porting the nin driver to -current as soon as I can find > time. (The cis for it says Ninja SCSI-3, btw.) > From http://home.jp.FreeBSD.org/~toshi/PAO/SUPPORTED.CARDS *14 The driver for Ninja SCSI-3 is available to the public from WORKBIT Corporation, which is already included in pao228. These cards can be used with earlier versions of PAO if the new driver is installed. http://www.workbit.co.jp/workbit/products/driver/sc3-unix.html __ GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 8 7:10: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from exchange.isgcolumbia.com (exchange.computerland.net [207.1.227.179]) by hub.freebsd.org (Postfix) with ESMTP id 0423F14CA9 for ; Mon, 8 Nov 1999 07:10:07 -0800 (PST) (envelope-from bkerr@isgcolumbia.com) Received: by EXCHANGE with Internet Mail Service (5.5.2448.0) id ; Mon, 8 Nov 1999 09:05:54 -0600 Message-ID: From: Brian Kerr To: "'scsi@freebsd.org'" Subject: problems with ncr adapter Date: Mon, 8 Nov 1999 09:05:46 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am having problems with a NCR/Symbios 53c875 controller, configured as ncr0 in my kernel. This is on a 3.3-stable machine. The problem occurs when "large" amounts of data are being written, or deleted from either da0 or da1, my two scsi drives. They are barracuda 4.5gig drives. The system goes into a userspace hang and the error respawns every 5 seconds or so on ttyv0 and in /var/log/messages, here is the message... /kernel: ncr0 queue is empty It causes the system to become unusable, anyone with any idea how to fix this please let me know. Thanks in advance ---------------------------------------------------------------- Brian Kerr - 573.446.8881 x51 Systems Administrator Midamerica/Computerland Internet Services - www.computerland.net The Digital Missourian - www.digmo.com ---------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 8 7:14:49 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id E761914FEB for ; Mon, 8 Nov 1999 07:14:46 -0800 (PST) (envelope-from gibbs@pluto.plutotech.com) Received: (from gibbs@localhost) by pluto.plutotech.com (8.9.2/8.9.1) id IAA39538; Mon, 8 Nov 1999 08:14:37 -0700 (MST) (envelope-from gibbs) From: Justin Gibbs Message-Id: <199911081514.IAA39538@pluto.plutotech.com> Subject: Re: scsi bus errors In-Reply-To: <19991107125930.A20165@shamz.net> from Shaun Jurrens at "Nov 7, 1999 12:59:30 pm" To: shamz@powertech.no (Shaun Jurrens) Date: Mon, 8 Nov 1999 08:14:37 -0700 (MST) Cc: scsi@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Well then let's begin with dmesg: ... > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.3-STABLE #0: Sun Oct 24 17:54:31 CEST 1999 > root@dakota.shamz.net:/usr/src/sys/compile/DAKOTA ... > da1: Fixed Direct Access SCSI-2 device > da1: 16.128MB/s transfers (8.064MHz, offset 8, 16bit), Tagged Queueing Enabled > da1: 4101MB (8399520 512 byte sectors: 255H 63S/T 522C) > da2 at ahc0 bus 0 target 9 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 16.128MB/s transfers (8.064MHz, offset 8, 16bit), Tagged Queueing Enabled > da2: 1075MB (2203480 512 byte sectors: 255H 63S/T 137C) ... Both of these drives have known buggy firmware on them. You need to be running L915 which is available from ftp.quantum.com. This could explain] all of the problems you've reported. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 8 12:23:25 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 96B4214A17 for ; Mon, 8 Nov 1999 12:23:17 -0800 (PST) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id PAA18644 for ; Mon, 8 Nov 1999 15:19:18 -0500 (EST) Reply-To: Randell Jesup To: scsi@freebsd.org Subject: CRD RAID controller and 3.3 From: Randell Jesup Date: 08 Nov 1999 16:19:59 +0000 In-Reply-To: Brian Kerr's message of "Mon, 8 Nov 1999 09:05:46 -0600" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone know if I'd have any problems using this RAID controller under 3.3-stable? Thanks. CRD-5644-200 RAID Controller -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 8 13: 5:55 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1]) by hub.freebsd.org (Postfix) with ESMTP id 9390D14DD0 for ; Mon, 8 Nov 1999 13:05:52 -0800 (PST) (envelope-from hinman@us.networkcs.com) Received: from us.networkcs.com (us.networkcs.com [137.66.11.15]) by marcos.networkcs.com (8.9.3/8.9.3) with ESMTP id PAA55627; Mon, 8 Nov 1999 15:05:51 -0600 (CST) (envelope-from hinman@us.networkcs.com) Received: (from hinman@localhost) by us.networkcs.com (8.9.2/8.8.7) id PAA69195; Mon, 8 Nov 1999 15:05:51 -0600 (CST) From: "Lee E. Hinman Ph.D." Message-Id: <199911082105.PAA69195@us.networkcs.com> Subject: Re: CRD RAID controller and 3.3 In-Reply-To: from Randell Jesup at "Nov 8, 99 04:19:59 pm" To: rjesup@wgate.com Date: Mon, 8 Nov 1999 15:05:51 -0600 (CST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Randell Jesup wrote: >Does anyone know if I'd have any problems using this RAID controller >under 3.3-stable? Thanks. > > CRD-5644-200 RAID Controller > >-- >Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) >rjesup@wgate.com > > We have a 5640 and we did have some odd double faults. Flashing the firmware to 1.9 seems to have fixed our problems and everything is running smoothly. Lee -- Lee E. Hinman Ph.D. Network Computing Services Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 8 14:25: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from wendy.auctionwatch.com (wendy.auctionwatch.com [216.32.245.130]) by hub.freebsd.org (Postfix) with ESMTP id 97E5E152E2; Mon, 8 Nov 1999 14:24:45 -0800 (PST) (envelope-from michael@wendy.auctionwatch.com) Received: from localhost (michael@localhost) by wendy.auctionwatch.com (8.9.3/8.9.3) with ESMTP id OAA01453; Mon, 8 Nov 1999 14:24:43 -0800 Date: Mon, 8 Nov 1999 14:24:43 -0800 (PST) From: "Michael S. Fischer" To: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: Trouble with QLogic 2200 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there, We're attempting to do some tests for a potential rollout of a new service, and we really want to use FreeBSD with FC-AL storage. We checked the hardware compatibility lists, and decided to go with a QLogic QLC-2200 PCI Fibre Channel controller. The card has been installed, and the BIOS works just fine. However, when we attempt to boot from the 3.3-RELEASE CD, the kernel recognizes the card during the device probe, but hangs with the following message: ... Waiting 15 seconds for SCSI devices to settle isp0: Firmware State Config Wait -> Loss Of Sync ... At this point, my only choice is to reboot. Our hardware profile: Tyan Thunderbolt (S1837) ATX motherboard 768MB RAM Onboard Adaptec AIC-7896 dual-channel U2W SCSI controller Seagate boot disk (ST39103LW, 9GB) on channel B, ID 0 Qlogic ISP2200 PCI card If I remove the Qlogic 2200 card, the machine boots gracefully. Is my only choice here to boot with some sort of Fibre Channel disk attached? Ours have not arrived yet, so I can't test whether or not the kernel will finish loading if the card is connected to a loop. -- Michael S. Fischer Sr. Engineer, AuctionWatch.com Phone: +1 650 808 5842 FAX: +1 650 875 0915 require Std::Disclaimer; "From the bricks of shame is built the hope"--Alan Wilder To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 8 14:30:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front1m.grolier.fr (front1m.grolier.fr [195.36.216.51]) by hub.freebsd.org (Postfix) with ESMTP id 00E6F15245 for ; Mon, 8 Nov 1999 14:29:48 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-164-34.villette.club-internet.fr [195.36.164.34]) by front1m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id XAA20100 for ; Mon, 8 Nov 1999 23:29:43 +0100 (MET) Date: Tue, 9 Nov 1999 00:53:17 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: scsi@FreeBSD.org Subject: Q: pci #bus #dev #func from device_t Message-ID: 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 X-Loop: FreeBSD.org I need to know about the actual bus number, device number and function number of a PCI device from some driver that attached this device. Is there some method to get this information from device_t? For now I just fell back on the old pci bus methods that are #ifdefed in the driver source against the new bus methods. The corresponding informations seem to be stored in the device.ivars field that points to a structure that is private to the pci.c driver. Sorry if I missed something important. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 8 14:35:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1A23F14BE4 for ; Mon, 8 Nov 1999 14:35:40 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA07232; Mon, 8 Nov 1999 14:35:44 -0800 Date: Mon, 8 Nov 1999 14:35:44 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Michael S. Fischer" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Trouble with QLogic 2200 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (trimmed to just -scsi). On Mon, 8 Nov 1999, Michael S. Fischer wrote: > Hi there, > > We're attempting to do some tests for a potential rollout of a new > service, and we really want to use FreeBSD with FC-AL storage. We checked > the hardware compatibility lists, and decided to go with a QLogic QLC-2200 > PCI Fibre Channel controller. The card has been installed, and the BIOS > works just fine. However, when we attempt to boot from the 3.3-RELEASE > CD, the kernel recognizes the card during the device probe, but hangs with > the following message: > > ... > Waiting 15 seconds for SCSI devices to settle > isp0: Firmware State Config Wait -> Loss Of Sync This means that a good loop is not being made. Unfortunately there isn't a good fix for this yet in the driver. I need to do some work to make the wait period much shorter for the initial probe so that an unconnected card doesn't hang you. This is tricky because you don't want to invalidate devices you've attached just because somebody has kicked the cable loose. > Is my only choice here to boot with some sort of Fibre Channel disk > attached? Ours have not arrived yet, so I can't test whether or not the > kernel will finish loading if the card is connected to a loop. Try disabling the card from either the boot prompt or loader.conf, i.e. in loader.conf: isp_disable=1 or from the boot prompt set isp_disable=1 I am very eager to hear about additional FC-AL experiences you will have. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 8 14:47:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id EEA23150EA for ; Mon, 8 Nov 1999 14:47:27 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id PAA75614; Mon, 8 Nov 1999 15:37:02 -0700 (MST) Date: Mon, 8 Nov 1999 15:37:02 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199911082237.PAA75614@narnia.plutotech.com> To: Gerard Roudier Cc: scsi@FreeBSD.org Subject: Re: Q: pci #bus #dev #func from device_t X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > I need to know about the actual bus number, device number and function > number of a PCI device from some driver that attached this device. > Is there some method to get this information from device_t? Yes. Use the pci_get/pci_set functions as defined in pcivar.h. ahc_pci.c uses these to get function numbers, etc. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 8 15: 6:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front3m.grolier.fr (front3m.grolier.fr [195.36.216.53]) by hub.freebsd.org (Postfix) with ESMTP id 9589614A05 for ; Mon, 8 Nov 1999 15:06:21 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-169-126.villette.club-internet.fr [195.36.169.126]) by front3m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id AAA05554; Tue, 9 Nov 1999 00:06:04 +0100 (MET) Date: Tue, 9 Nov 1999 01:29:38 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Q: pci #bus #dev #func from device_t In-Reply-To: <199911082237.PAA75614@narnia.plutotech.com> Message-ID: 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 X-Loop: FreeBSD.org On Mon, 8 Nov 1999, Justin T. Gibbs wrote: > In article you wrote: > >=20 > > I need to know about the actual bus number, device number and function > > number of a PCI device from some driver that attached this device. > > Is there some method to get this information from device_t? >=20 > Yes. Use the pci_get/pci_set functions as defined in pcivar.h. ahc_pci.= c > uses these to get function numbers, etc. Thanks very much. 'grep' is indeed not skilled enough to get them. :-) G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 8 15:24:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 35D741510A; Mon, 8 Nov 1999 15:24:03 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA90532; Mon, 8 Nov 1999 16:23:59 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA13190; Mon, 8 Nov 1999 16:23:21 -0700 (MST) Message-Id: <199911082323.QAA13190@harmony.village.org> To: Geoff Buckingham Subject: Re: 2nd Query: Is someone 'camifying' ncv0 scsi? Cc: "Kenneth D. Merry" , "Gandalf T. Grey" , freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG In-reply-to: Your message of "Sat, 06 Nov 1999 11:23:10 GMT." <19991106112310.A39348@chuggalug.clues.com> References: <19991106112310.A39348@chuggalug.clues.com> <19991105233303.83205.qmail@hotmail.com> <199911052351.QAA02229@panzer.kdm.org> Date: Mon, 08 Nov 1999 16:23:21 -0700 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19991106112310.A39348@chuggalug.clues.com> Geoff Buckingham writes: : However PAO for 3.x seems to have lost all scsi support. Is this because : of some clash with cam, or simply non of the chipsets have cam drivers? CAM is the reason. : 2.2.8 PAO support SCSI PC-cards: : : Adaptec SlimSCSI APA-1460 OK aic : Adaptec SlimSCSI APA-1460A OK aic : Adaptec SlimSCSI APA-1460AJ OK aic : Adaptec SlimSCSI APA-1460B OK aic : Adaptec SlimSCSI APA-1460J OK aic : Fujitsu FMV-J123 OK aic : MELCO IFC-DC2 (SCSI2) OK aic : MELCO IFC-SCD OK aic : NewMedia BusToaster OK aic : SONY PRD-250 CD-ROM Diskman OK aic *8 : SONY PRD-650 CD-ROM Diskman OK aic *8 aic is good now. There are pccard attachments that have been posted. I know that they at least it has been posted to nomads. I recently forwarded some patches from there to Justin and Ken to allow detaching to happen more easily or reliabily. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 9 14:33:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from surf.iae.nl (surf.IAE.nl [194.151.66.2]) by hub.freebsd.org (Postfix) with ESMTP id E4B8215394 for ; Tue, 9 Nov 1999 14:33:13 -0800 (PST) (envelope-from wjw@iae.nl) Received: by surf.iae.nl (Postfix, from userid 74) id DBEEEBFD1A; Tue, 9 Nov 1999 23:33:11 +0100 (CET) To: tom@sdf.com Subject: Re: DPT SmartRAID IV (da0:dpt0:0:0:0) : CCB 0xc550807c - timeout. X-Newsgroups: list.freebsd.scsi In-Reply-To: References: Organization: Internet Access Eindhoven BV Cc: scsi@freebsd.org Message-Id: <19991109223311.DBEEEBFD1A@surf.iae.nl> Date: Tue, 9 Nov 1999 23:33:11 +0100 (CET) From: wjw@iae.nl (Willem Jan Withagen) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: > >On Sat, 30 Oct 1999, Mike wrote: > >> Hi all! >> >> It seems once awhile the FreeBSD-3.3-Release system hangs with the >> following message: >> >> /kernel: (da0:dpt0:0:0:0) : CCB 0xc550807c - timeout. >> /kernel: (da0:dpt0:0:0:0) : CCB 0xc5508744 - timeout. > > You probably want to put the "DPT_VERIFY_HINTR" and "DPT_LOST_IRQ" >options into your kernel config file. I once discussed this problem with Simon, and it turned out that the version on that card was newer. Reverting to an older version fixed the problem. I'm currently running: dpt0: rev 0x02 int a irq 10 on pci0.11.0 dpt0: DPT PM3334UW FW Rev. 07M0, 1 channel, 64 CCBs Other arguments for trouble were: - defect disks - bad cableing - bad termination --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 9.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 10 7:20: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 95B4B14DDA for ; Wed, 10 Nov 1999 07:20:01 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-136.skylink.it [194.185.55.136]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id QAA11736 for ; Wed, 10 Nov 1999 16:20:54 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with SMTP id HAA06279 for ; Wed, 10 Nov 1999 07:39:36 -0700 (MST) (envelope-from hibma@skylink.it) Date: Wed, 10 Nov 1999 07:39:35 -0700 (MST) From: Nick Hibma X-Sender: n_hibma@henny.plazza.it Reply-To: Nick Hibma To: FreeBSD SCSI Mailing List Subject: queues in CAM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to understand the queueing thing in CAM. The following code fragment (which is found in all the SIMs) devq = cam_simq_alloc(MO /*maximum openings*/); sc->sim = cam_sim_alloc(umass_cam_action, umass_cam_poll, "umass", sc, device_get_unit(sc->sc_dev), MDO /*max_dev_openings*/, MTDO /*max_tagged_dev_openings*/, devq); confuses me. Are the MDO and MTDO values related to per device queues? And is the MO value related to a per SIM queue? The values in for example the dpt_scsi.c driver indicate that if 1 device has 255 tagged commands outstanding, it blocks the SIM from accepting more requests. Or are requests transferred from the SIM queue to the device queue as soon as the SIM accepts them? Values for other drivers (random selection): (MO = Maximum openings, MDO = Maximum Device Openings, MTDO = Maximum Tagged Device Openings) dev/aic7xxx/aic7xxx.c: MO=MTDO=255, MDO=1 ./dev/dpt/dpt_scsi.c: MO=MTDO=256, MDO=2 ./dev/buslogic/bt.c: MO=MTDO+1=192, MDO=2 ./dev/buslogic/bt.c: MO=192, MTDO=0, MDO=2 (tagged not supported) ./pci/ncr.c: MO=255, MTDO=32, MDO=1 In my case (dev/usb/umass.c, new version) should it be the following? MO=1, MDO=1, MTDO=0 USB Bulk-Only SIM has a maximum of one device and the device does not support tagged command queueing. Any (partial) explanation would be appreciated. Cheers, Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 10 7:20: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 5D43E14E1F for ; Wed, 10 Nov 1999 07:20:03 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-136.skylink.it [194.185.55.136]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id QAA11740 for ; Wed, 10 Nov 1999 16:20:56 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with SMTP id HAA06284 for ; Wed, 10 Nov 1999 07:44:30 -0700 (MST) (envelope-from hibma@skylink.it) Date: Wed, 10 Nov 1999 07:44:30 -0700 (MST) From: Nick Hibma X-Sender: n_hibma@henny.plazza.it Reply-To: Nick Hibma To: FreeBSD SCSI Mailing List Subject: renaming transactions to openings in cam_sim.c Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I suggest the following name change for consistency. If there are no comments I'll commit it tomorrow. heidi:n_hibma% lcvs diff cam_sim.c Index: cam_sim.c =================================================================== RCS file: /home/ncvs/src/sys/cam/cam_sim.c,v retrieving revision 1.3 diff -u -w -r1.3 cam_sim.c --- cam_sim.c 1999/08/28 00:40:42 1.3 +++ cam_sim.c 1999/11/10 14:44:53 @@ -40,9 +40,9 @@ #define CAM_PATH_ANY (u_int32_t)-1 struct cam_devq * -cam_simq_alloc(u_int32_t max_sim_transactions) +cam_simq_alloc(u_int32_t max_sim_openings) { - return (cam_devq_alloc(/*size*/0, max_sim_transactions)); + return (cam_devq_alloc(/*size*/0, max_sim_openings)); } void @@ -54,8 +54,8 @@ struct cam_sim * cam_sim_alloc(sim_action_func sim_action, sim_poll_func sim_poll, char *sim_name, void *softc, u_int32_t unit, - int max_dev_transactions, - int max_tagged_dev_transactions, struct cam_devq *queue) + int max_dev_openings, + int max_tagged_dev_openings, struct cam_devq *queue) { struct cam_sim *sim; @@ -80,8 +80,8 @@ sim->path_id = CAM_PATH_ANY; sim->unit_number = unit; sim->bus_id = 0; /* set in xpt_bus_register */ - sim->max_tagged_dev_openings = max_tagged_dev_transactions; - sim->max_dev_openings = max_dev_transactions; + sim->max_tagged_dev_openings = max_tagged_dev_openings; + sim->max_dev_openings = max_dev_openings; sim->flags = 0; callout_handle_init(&sim->c_handle); sim->devq = queue; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 10 13: 0:18 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 2A8A014E16 for ; Wed, 10 Nov 1999 13:00:10 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id NAA77764; Wed, 10 Nov 1999 13:49:53 -0700 (MST) Date: Wed, 10 Nov 1999 13:49:53 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199911102049.NAA77764@narnia.plutotech.com> To: Nick Hibma Cc: scsi@FreeBSD.org Subject: Re: renaming transactions to openings in cam_sim.c X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > I suggest the following name change for consistency. If there are no > comments I'll commit it tomorrow. No. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 10 13: 9:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 31B9014D90 for ; Wed, 10 Nov 1999 13:09:29 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id NAA77778; Wed, 10 Nov 1999 13:59:12 -0700 (MST) Date: Wed, 10 Nov 1999 13:59:12 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199911102059.NAA77778@narnia.plutotech.com> To: Nick Hibma Cc: scsi@FreeBSD.org Subject: Re: queues in CAM X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > I'm trying to understand the queueing thing in CAM. The following code > fragment (which is found in all the SIMs) > > > devq = cam_simq_alloc(MO /*maximum openings*/); > sc->sim = cam_sim_alloc(umass_cam_action, umass_cam_poll, > "umass", sc, > device_get_unit(sc->sc_dev), > MDO /*max_dev_openings*/, > MTDO /*max_tagged_dev_openings*/, > devq); > > confuses me. Are the MDO and MTDO values related to per device queues? > And is the MO value related to a per SIM queue? Yes and yes. Some controllers, although they can accept a rather large number of transactions, cannot queue that many to just a single device. MDO exports the controller's ability to queue untagged transactions to a single device. MTDO does the same thing for tagged transactions. > > The values in for example the dpt_scsi.c driver indicate that if 1 > device has 255 tagged commands outstanding, it blocks the SIM from > accepting more requests. Or are requests transferred from the SIM queue > to the device queue as soon as the SIM accepts them? MO is a controller global limit. MDO and MTDO are device specific limits with only one or the other in effect (you can't mix tagged and untagged transactions). So, if only a single device is active on the bus, and the controller can support queuing all of its transactions to a single device, then yes, a single device can take them all. Of course, CAM uses a round-robin, per-priority level scheduler, so as soon as another device becomes active on the bus it will take transaction resources away from the hog very quickly. See http://www.FreeBSD.org/~gibbs/cam.html > In my case (dev/usb/umass.c, new version) should it be the following? > > MO=1, MDO=1, MTDO=0 Some controllers queue up additional untagged transactions so that the RTT for commands is reduced. This would be the only reason to bump the MDO number. Since you have a 1-1 mapping of devices to SIMs, MO should be equal to MDO. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 10 14:52:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front4m.grolier.fr (front4m.grolier.fr [195.36.216.54]) by hub.freebsd.org (Postfix) with ESMTP id 5B8F314CA3 for ; Wed, 10 Nov 1999 14:52:38 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-159-141.villette.club-internet.fr [195.36.159.141]) by front4m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id XAA18278; Wed, 10 Nov 1999 23:52:28 +0100 (MET) Date: Thu, 11 Nov 1999 01:16:12 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: "Justin T. Gibbs" Cc: Nick Hibma , scsi@FreeBSD.ORG Subject: Re: queues in CAM In-Reply-To: <199911102059.NAA77778@narnia.plutotech.com> Message-ID: 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 X-Loop: FreeBSD.org On Wed, 10 Nov 1999, Justin T. Gibbs wrote: > In article you = wrote: > >=20 > > I'm trying to understand the queueing thing in CAM. The following code > > fragment (which is found in all the SIMs) > >=20 > >=20 > > devq =3D cam_simq_alloc(MO /*maximum openings*/); > > sc->sim =3D cam_sim_alloc(umass_cam_action, umass_cam_poll, > > =09=09=09=09"umass", sc, > > device_get_unit(sc->sc_dev), > > =09=09=09=09MDO /*max_dev_openings*/, > > =09=09=09=09MTDO /*max_tagged_dev_openings*/, > > =09=09=09=09devq); > >=20 > > confuses me. Are the MDO and MTDO values related to per device queues? > > And is the MO value related to a per SIM queue? >=20 > Yes and yes. Some controllers, although they can accept a rather large > number of transactions, cannot queue that many to just a single device. And some controllers may want to accept more than 256 transactions and then have to be careful of not queuing all the transactions to a single=20 device. =20 G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 10 15:13: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id C286B14E5B for ; Wed, 10 Nov 1999 15:13:03 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-152.skylink.it [194.185.55.152]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id AAA06053; Thu, 11 Nov 1999 00:13:55 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with SMTP id QAA00774; Wed, 10 Nov 1999 16:12:34 -0700 (MST) (envelope-from hibma@skylink.it) Date: Wed, 10 Nov 1999 16:12:34 -0700 (MST) From: Nick Hibma X-Sender: n_hibma@henny.plazza.it Reply-To: Nick Hibma To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: renaming transactions to openings in cam_sim.c In-Reply-To: <199911102049.NAA77764@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I suggest the following name change for consistency. If there are no > > comments I'll commit it tomorrow. > > No. :-) No what? No comments? Or no, don't change? Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 10 16: 5:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id D829C14F2F for ; Wed, 10 Nov 1999 16:05:35 -0800 (PST) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id QAA00641; Wed, 10 Nov 1999 16:06:31 -0700 (MST) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199911102306.QAA00641@caspian.plutotech.com> X-Mailer: exmh version 2.1.0 09/18/1999 To: Nick Hibma Cc: "Justin T. Gibbs" , scsi@FreeBSD.org Subject: Re: renaming transactions to openings in cam_sim.c In-reply-to: Your message of "Wed, 10 Nov 1999 16:12:34 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Nov 1999 16:06:31 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> > I suggest the following name change for consistency. If there are no >> > comments I'll commit it tomorrow. >> >> No. > >:-) No what? No comments? Or no, don't change? > >Nick 1) A 24 hour request for review time-limit is way too short. I frequently get so bogged down with other work that I don't read this list for days at a time. I'm sure I'm not the only one. 2) I see this as a gratuitous change. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 10 23:16:12 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3B27714CB7; Wed, 10 Nov 1999 23:16:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id XAA16615; Wed, 10 Nov 1999 23:16:28 -0800 Date: Wed, 10 Nov 1999 23:16:28 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: Nick Hibma , "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: renaming transactions to openings in cam_sim.c In-Reply-To: <199911102306.QAA00641@caspian.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 10 Nov 1999, Justin T. Gibbs wrote: > > > >> > I suggest the following name change for consistency. If there are no > >> > comments I'll commit it tomorrow. > >> > >> No. > > > >:-) No what? No comments? Or no, don't change? > > > >Nick > > 1) A 24 hour request for review time-limit is way too short. I frequently > get so bogged down with other work that I don't read this list for days > at a time. I'm sure I'm not the only one. > > 2) I see this as a gratuitous change. It seemd to clarify things for Nick- how about a comment in the source, Nick? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 10 23:37: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.vera.net (mail.vera.net [200.33.116.55]) by hub.freebsd.org (Postfix) with ESMTP id 2BC4514CCE for ; Wed, 10 Nov 1999 23:36:56 -0800 (PST) (envelope-from mdragon@vera.net) Received: from mail.vera.net (mail.vera.net [200.33.116.55]) by mail.vera.net (8.9.3/8.9.3) with ESMTP id BAA18655 for ; Thu, 11 Nov 1999 01:36:52 -0600 (CST) Date: Thu, 11 Nov 1999 01:36:52 -0600 (CST) From: mdragon@vera.net To: freebsd-scsi@FreeBSD.ORG Subject: SYM 0.9.0-19991024 O.K. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Last night we tested this controller on a HP-Netserver LH4 (53c895 fast40 scsi) this machine has 2 Xeons and 4 9Gb-10,000 rpm. disks and we found no problems and a performace(*) gain of roughly 3-4% over the standard ncr0 controller. 3 disks are configured as a ccd device with a 8192 interleave, Kernel 3.3-stable. [(*) not even a real benchmark: just running du, dd, find . -exec grep, and tar cf - | tar xf - ] A fact that troubles me is that sym0 was able to set the transfer speed to 80.000 MB/s. and the only change in the kernel configuration file was adding the sym0 line, I can't figure out why ncr0 always sets transfer speed to 40 MB/s. I remember that a similar kernel was built on a HP LPr (same 53c895 controller, same disks) and ncr0 also set the transfers speeds to fast40-wide. What am I doing wrong? My list of questions: - Is vinum prefered over ccd ? - Is someone working on the AMI MegaRAID controller ? - Is it possible to use this raid somehow ? (maybe through bios, at least the bootloader can recognize it) Would sym0 find the raid ? I have the idea that it should, since it appears in the SCSI bus as id #0 lun #1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 11 1:44:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id E834A14C8E; Thu, 11 Nov 1999 01:44:14 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA07689; Thu, 11 Nov 1999 09:46:07 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 11 Nov 1999 09:46:06 +0000 (GMT) From: Doug Rabson To: Matthew Jacob Cc: "Justin T. Gibbs" , Nick Hibma , "Justin T. Gibbs" , scsi@freebsd.org Subject: Re: renaming transactions to openings in cam_sim.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 10 Nov 1999, Matthew Jacob wrote: > > > On Wed, 10 Nov 1999, Justin T. Gibbs wrote: > > > > > > >> > I suggest the following name change for consistency. If there are no > > >> > comments I'll commit it tomorrow. > > >> > > >> No. > > > > > >:-) No what? No comments? Or no, don't change? > > > > > >Nick > > > > 1) A 24 hour request for review time-limit is way too short. I frequently > > get so bogged down with other work that I don't read this list for days > > at a time. I'm sure I'm not the only one. > > > > 2) I see this as a gratuitous change. > > It seemd to clarify things for Nick- how about a comment in the source, > Nick? The word 'transactions' always seemed more informative than 'openings' to me. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 11 1:56:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front1.grolier.fr (front1.grolier.fr [194.158.96.51]) by hub.freebsd.org (Postfix) with ESMTP id 6A5DC14C8E for ; Thu, 11 Nov 1999 01:56:48 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-159-45.villette.club-internet.fr [195.36.159.45]) by front1.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id KAA28566; Thu, 11 Nov 1999 10:56:41 +0100 (MET) Date: Thu, 11 Nov 1999 12:20:27 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: mdragon@vera.net Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SYM 0.9.0-19991024 O.K. In-Reply-To: Message-ID: 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 X-Loop: FreeBSD.org On Thu, 11 Nov 1999 mdragon@vera.net wrote: > Last night we tested this controller on a HP-Netserver LH4 (53c895 fast40 > scsi) this machine has 2 Xeons and 4 9Gb-10,000 rpm. disks and we found > no problems and a performace(*) gain of roughly 3-4% over the standard > ncr0 controller. 3 disks are configured as a ccd device with a 8192 > interleave, Kernel 3.3-stable. Thanks for your report. I am very glad of the driver being solid. In my opinion, the conditions for getting performance gain using the sym driver are the following: - Disk capable of very low command overhead. The sym driver has been measured by me 62 micro-seconds while the ncr got more than twice this value in the same situations. - Large numbers of tags. The sym driver uses O(1) on all pathes but the ncr scans lists of CCBs from the C code and from the SCRIPTS as well. But, if the load of your machine does not experience a bottleneck on any resource (including CPU on heavy IO load), then the caching and prefetching does eat latencies for both drivers and no significant performance gain will probably be observed.=20 You must also consider other sym driver features as: - NVRAM support. - Hardware phase mismatch handling for the 896/895A that ensures the system will get at _most_ 1 interrupt per actual IO. > [(*) not even a real benchmark: just running du, dd, > find . -exec grep, and tar cf - | tar xf - ] >=20 > A fact that troubles me is that sym0 was able to set the transfer speed t= o > 80.000 MB/s. and the only change in the kernel configuration file was > adding the sym0 line, I can't figure out why ncr0 always sets transfer > speed to 40 MB/s. It does not seem to exist a really clean way for that, since: - If SCSI_NCR_MAX_SYNC is not defined, the ncr driver will assume default sync period factor to be 12 (20 mega-transfers/second) - If defined, the driver will calculate default sync factor as: #define=09SCSI_NCR_DFLT_SYNC (250000 / SCSI_NCR_MAX_SYNC) which is incorrect for MAX_SYNC >=3D 20000 (SCSI > 2) But the ncr init code (I adapted to ULTRA/ULTRA2 SCSI support two years ago) keeps track of _actual_ min sync factor based on controller capability and a correct value will be proposed to SCSI devices in any situation. So, something like the following in your kernel config file: options SCSI_NCR_MAX_SYNC=3D40000 should do the trick. (25000 should work as well, see above) > I remember that a similar kernel was built on a HP LPr (same 53c895 > controller, same disks) and ncr0 also set the transfers speeds to > fast40-wide. What am I doing wrong? >=20 > My list of questions: > - Is vinum prefered over ccd ? > - Is someone working on the AMI MegaRAID controller ? I am not competent for these ones (notably :) ). > - Is it possible to use this raid somehow ?=20 I would be highly surprised an AMI-raid volume be recognized by either ccd or vinum, so a SIM for AMI-raid may actually be required. > (maybe through bios, at least the bootloader can recognize it) > Would sym0 find the raid ? I have the idea that it should, since it > appears in the SCSI bus as id #0 lun #1 sym and ncr donnot know about what RAID is. They just communicate with SCSI devices using the SCSI chip capabilities. In order to access AMI-raid volumes you need a specific driver that supports AMI-raid interface. For software raid, the RAID feature is handled by upper layers. For hardware raid (AMI-raid for example) the controller (that consists in some software executed by some Intel IO processor for the AMI-raid) handles RAID and presents logical volumes as LUNs to SIM. When using hardware RAID capable of interfacing SYM53C8XX devices that are visible from the PCI BUS, you must ensure that only a single entity will attach directly (ncr/sym) or indirectly (AMI-RAID) each SYM53C8XX device, otherwise this will not work for sure.=20 G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 11 2:12:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front6m.grolier.fr (front6m.grolier.fr [195.36.216.56]) by hub.freebsd.org (Postfix) with ESMTP id 3942314A10; Thu, 11 Nov 1999 02:12:42 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-101-92.villette.club-internet.fr [194.158.101.92]) by front6m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id LAA25254; Thu, 11 Nov 1999 11:11:47 +0100 (MET) Date: Thu, 11 Nov 1999 12:35:33 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: Doug Rabson Cc: Matthew Jacob , "Justin T. Gibbs" , Nick Hibma , "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: renaming transactions to openings in cam_sim.c In-Reply-To: Message-ID: 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 X-Loop: FreeBSD.org On Thu, 11 Nov 1999, Doug Rabson wrote: > On Wed, 10 Nov 1999, Matthew Jacob wrote: >=20 > >=20 > >=20 > > On Wed, 10 Nov 1999, Justin T. Gibbs wrote: > >=20 > > > > > > > >> > I suggest the following name change for consistency. If there ar= e no > > > >> > comments I'll commit it tomorrow. > > > >>=20 > > > >> No. > > > > > > > >:-) No what? No comments? Or no, don't change? > > > > > > > >Nick > > >=20 > > > 1) A 24 hour request for review time-limit is way too short. I frequ= ently > > > get so bogged down with other work that I don't read this list for= days > > > at a time. I'm sure I'm not the only one. > > >=20 > > > 2) I see this as a gratuitous change. > >=20 > > It seemd to clarify things for Nick- how about a comment in the source, > > Nick? >=20 > The word 'transactions' always seemed more informative than 'openings' to > me. It does not in the BSD SCSI world given the history. 'openings' makes full sense and 'transactions' makes some generic sense that is close to no-informative. I have had to learn about 3000 english words in order to understand software and 'openings' didn't make any problem to me, even with the initial spelling mistake or difference (opennings).=20 But, may-be, you want the kernel to use academic english wording and indeed it is not in my fields at all. ;-)=20 G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 11 2:15:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 1BA3314A10 for ; Thu, 11 Nov 1999 02:15:28 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id KAA59448; Thu, 11 Nov 1999 10:15:04 GMT (envelope-from geoffb) Date: Thu, 11 Nov 1999 10:15:04 +0000 From: Geoff Buckingham To: mdragon@vera.net Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SYM 0.9.0-19991024 O.K. Message-ID: <19991111101504.A59396@chuggalug.clues.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from mdragon@vera.net on Thu, Nov 11, 1999 at 01:36:52AM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 11, 1999 at 01:36:52AM -0600, mdragon@vera.net wrote: > > My list of questions: > - Is vinum prefered over ccd ? Vinum is more fully featured than ccd and more activly being developed, I switched to vinum for stripes and mirrors on production machines about six months ago. I would still be cautios about using the RAID 5 in production. > - Is someone working on the AMI MegaRAID controller ? Mike Smith has written a driver available at: http://www.freebsd.org/~msmith/RAID/ami/amr-stable-991109.tar.gz Which he announced to freebsd-stable with the following notes: } - This is the first revision. It should work OK, but I will } appreciate feedback on how well it works for you. } - You can't boot from a RAID volume. The fix for this is quite } nontrivial, and may not ever make it back into the 3.x family. } - Unlike with the Mylex cards, you _don't_ need to update the } bootstrap and loader before installing the card. > - Is it possible to use this raid somehow ? > (maybe through bios, at least the bootloader can recognize it) > Would sym0 find the raid ? I have the idea that it should, since it > appears in the SCSI bus as id #0 lun #1 -- GeoffB> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 11 3:24:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from proteus.eclipse.net.uk (proteus.eclipse.net.uk [195.188.32.118]) by hub.freebsd.org (Postfix) with ESMTP id 17E1B14C36 for ; Thu, 11 Nov 1999 03:24:49 -0800 (PST) (envelope-from stuart@eclipse.net.uk) Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31]) by proteus.eclipse.net.uk (Postfix) with ESMTP id 934F29B29; Thu, 11 Nov 1999 11:24:48 +0000 (GMT) Message-ID: <382AA79C.FE26B97F@eclipse.net.uk> Date: Thu, 11 Nov 1999 11:25:16 +0000 From: Stuart Henderson Organization: Eclipse Networking X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-GB MIME-Version: 1.0 To: mdragon@vera.net Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SYM 0.9.0-19991024 O.K. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Last night we tested this controller on a HP-Netserver LH4 (53c895 fast40 > scsi) this machine has 2 Xeons and 4 9Gb-10,000 rpm. disks and we found > no problems and a performace(*) gain of roughly 3-4% over the standard > ncr0 controller. 3 disks are configured as a ccd device with a 8192 > interleave, Kernel 3.3-stable. I have been running SYM 0.9.0 on an HP LPr, 2x7200rpm 9gb (50-100tps on a webcache) for two days. I am happy with the driver so far. > - Is someone working on the AMI MegaRAID controller ? Mike Smith has requested Mylex, AMI, DELL, and HP RAID controllers for driver development and testing. http://www.freebsd.org/cgi/getmsg.cgi?fetch=63596+0+/usr/local/www/db/text/1999/freebsd-isp/19991010.freebsd-isp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 11 6:41: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 9B07814CAE; Thu, 11 Nov 1999 06:41:02 -0800 (PST) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-139.skylink.it [194.185.55.139]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id PAA11563; Thu, 11 Nov 1999 15:41:53 +0100 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id BAA05976; Thu, 11 Nov 1999 01:15:48 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Thu, 11 Nov 1999 01:15:48 GMT Date: Thu, 11 Nov 1999 02:15:48 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: "Justin T. Gibbs" Cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: renaming transactions to openings in cam_sim.c In-Reply-To: <199911102306.QAA00641@caspian.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The change was a change of variable names. But I'll keep your comment in mind next time. Cheers, Nick P.S.: I'll leave it as it is. > 1) A 24 hour request for review time-limit is way too short. I frequently > get so bogged down with other work that I don't read this list for days > at a time. I'm sure I'm not the only one. > > 2) I see this as a gratuitous change. > > -- > Justin > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 11 12: 6:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 2D61914F15; Thu, 11 Nov 1999 12:06:16 -0800 (PST) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id MAA01952; Thu, 11 Nov 1999 12:07:00 -0700 (MST) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199911111907.MAA01952@caspian.plutotech.com> X-Mailer: exmh version 2.1.0 09/18/1999 To: mjacob@feral.com Cc: "Justin T. Gibbs" , Nick Hibma , "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: renaming transactions to openings in cam_sim.c In-reply-to: Your message of "Wed, 10 Nov 1999 23:16:28 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Nov 1999 12:07:00 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> 1) A 24 hour request for review time-limit is way too short. I frequently >> get so bogged down with other work that I don't read this list for days >> at a time. I'm sure I'm not the only one. >> >> 2) I see this as a gratuitous change. > >It seemd to clarify things for Nick- how about a comment in the source, >Nick? If anything, the max fields should be renamed. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 11 12: 9:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id A09F114CA4; Thu, 11 Nov 1999 12:09:34 -0800 (PST) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id MAA01964; Thu, 11 Nov 1999 12:08:49 -0700 (MST) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199911111908.MAA01964@caspian.plutotech.com> X-Mailer: exmh version 2.1.0 09/18/1999 To: Doug Rabson Cc: Matthew Jacob , "Justin T. Gibbs" , Nick Hibma , "Justin T. Gibbs" , scsi@freebsd.org Subject: Re: renaming transactions to openings in cam_sim.c In-reply-to: Your message of "Thu, 11 Nov 1999 09:46:06 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Nov 1999 12:08:49 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> > >> > I suggest the following name change for consistency. If there are no >> > >> > comments I'll commit it tomorrow. >> > >> >> > >> No. >> > > >> > >:-) No what? No comments? Or no, don't change? >> > > >> > >Nick >> > >> > 1) A 24 hour request for review time-limit is way too short. I frequently >> > get so bogged down with other work that I don't read this list for days >> > at a time. I'm sure I'm not the only one. >> > >> > 2) I see this as a gratuitous change. >> >> It seemd to clarify things for Nick- how about a comment in the source, >> Nick? > >The word 'transactions' always seemed more informative than 'openings' to >me. Yes. 'openings' should only be used for the counters that track capacity, but perhaps even there a better term could be used. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 11 14:15:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id 005BB14ED7; Thu, 11 Nov 1999 14:15:41 -0800 (PST) (envelope-from hpc@teaser.fr) Received: from asus.teaser.fr (dip227.teaser.fr [194.51.100.227]) by reliam.teaser.fr (8.9.3/8.9.3) with ESMTP id XAA01326; Thu, 11 Nov 1999 23:15:25 +0100 (MET) Received: from (hpc@localhost) by asus.teaser.fr (8.9.3/jtpda-5.3.1) id XAA00539 ; Thu, 11 Nov 1999 23:15:35 +0100 (CET) Date: Thu, 11 Nov 1999 23:15:35 +0100 From: Charles Henri-Pierre To: freebsd-questions@FreeBSD.ORG, freebsd-Multimedia@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Cc: Charles Henri-Pierre Subject: Any success story for an SCSI scanner Message-ID: <19991111231534.A508@asus.teaser.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I want to buy a scanner. SCSI seem a good solution. As anybody successfuly used one of these : Mustek Scan Express 12 000 SP or Epson Perfection 1200 S ? Sane home page and FreeBSD mailing list don't speak about theses. I use a PII box with an asus P2B-S motherboard, and I run 3.3-STABLE. Thanks for all anwers H-P To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 11 14:16: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id DFC4D14ED7; Thu, 11 Nov 1999 14:16:00 -0800 (PST) (envelope-from hpc@teaser.fr) Received: from asus.teaser.fr (dip227.teaser.fr [194.51.100.227]) by reliam.teaser.fr (8.9.3/8.9.3) with ESMTP id XAA17764; Thu, 11 Nov 1999 23:15:47 +0100 (MET) Received: from (hpc@localhost) by asus.teaser.fr (8.9.3/jtpda-5.3.1) id XAA00549 ; Thu, 11 Nov 1999 23:15:58 +0100 (CET) Date: Thu, 11 Nov 1999 23:15:58 +0100 From: Charles Henri-Pierre To: freebsd-questions@FreeBSD.ORG, freebsd-Multimedia@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Cc: hpc@asus.teaser.fr Subject: Any success story for an SCSI scanner Message-ID: <19991111231534.A508@asus.teaser.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I want to buy a scanner. SCSI seem a good solution. As anybody successfuly used one of these : Mustek Scan Express 12 000 SP or Epson Perfection 1200 S ? Sane home page and FreeBSD mailing list don't speak about theses. I use a PII box with an asus P2B-S motherboard, and I run 3.3-STABLE. Thanks for all anwers H-P To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 11 14:30:41 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 458CB14F79 for ; Thu, 11 Nov 1999 14:30:34 -0800 (PST) (envelope-from dkelly@mail.HiWAAY.net) Received: (from dkelly@localhost) by mail.HiWAAY.net (8.9.3/8.9.0) id QAA28949; Thu, 11 Nov 1999 16:30:32 -0600 (CST) Date: Thu, 11 Nov 1999 16:30:32 -0600 (CST) From: David Kelly Message-Id: <199911112230.QAA28949@mail.HiWAAY.net> To: freebsd-scsi@freebsd.org Subject: AIWA DDS-2 drives? Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Have found some Aiwa GD-80001HC drives for cheap and wondered if anyone has used one under FreeBSD yet? `grep -i aiwa /usr/src/cam` didn't turn up anything. So presumably if something is known about this model its not bad but that doesn't say if anything good is known either. -- David Kelly N4HHE, dkelly@hiwaay.net (hm) ====================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 11 15: 9:37 1999 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 3F01414E4A for ; Thu, 11 Nov 1999 15:09:34 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA30105; Thu, 11 Nov 1999 16:09:23 -0700 (MST) (envelope-from ken) Message-Id: <199911112309.QAA30105@panzer.kdm.org> Subject: Re: AIWA DDS-2 drives? In-Reply-To: <199911112230.QAA28949@mail.HiWAAY.net> from David Kelly at "Nov 11, 1999 04:30:32 pm" To: dkelly@mail.HiWAAY.net (David Kelly) Date: Thu, 11 Nov 1999 16:09:22 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Kelly wrote... > Have found some Aiwa GD-80001HC drives for cheap and wondered if anyone > has used one under FreeBSD yet? `grep -i aiwa /usr/src/cam` didn't turn > up anything. So presumably if something is known about this model its > not bad but that doesn't say if anything good is known either. From the web page (http://www.aiwa.com/csd/product/dds2mn.htm), it looks like just another DDS-2 drive. My guess is that they probably just OEM someone else's drive mechanism, but who knows. It should function fine, but of course you never know until someone tries it. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 12 3:38:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 8F6E914D81 for ; Fri, 12 Nov 1999 03:38:27 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id LAA63214 for scsi@freebsd.org; Fri, 12 Nov 1999 11:38:22 GMT (envelope-from geoffb) Date: Fri, 12 Nov 1999 11:38:18 +0000 From: Geoff Buckingham To: scsi@freebsd.org Subject: rawio error Message-ID: <19991112113818.A63087@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am seeing a number of errors with one particular drive when using rawio, bot read and write. However I am not seeing any errors going to syslog from the kernel. Is this something others have seen ? Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec anon 1522.3 94 2723.4 166 Child 4 Bad write at 2097414144: 0 of 12288 bytes 1433.2 89 2055.4 125 -- GeofffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 12 5:13:22 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 98D9114D94 for ; Fri, 12 Nov 1999 05:13:16 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id NAA63331 for scsi@FreeBSD.ORG; Fri, 12 Nov 1999 13:13:10 GMT (envelope-from geoffb) Date: Fri, 12 Nov 1999 13:13:10 +0000 From: Geoff Buckingham To: scsi@FreeBSD.ORG Subject: Re: rawio error Message-ID: <19991112131310.B63087@chuggalug.clues.com> References: <19991112113818.A63087@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19991112113818.A63087@chuggalug.clues.com>; from Geoff Buckingham on Fri, Nov 12, 1999 at 11:38:18AM +0000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Nov 12, 1999 at 11:38:18AM +0000, Geoff Buckingham wrote: > > I am seeing a number of errors with one particular drive when using rawio, > bot read and write. However I am not seeing any errors going to syslog from > the kernel. Is this something others have seen ? > > > > > Random read Sequential read Random write Sequential write > ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec > anon 1522.3 94 2723.4 166 Child 4 Bad write at 2097414144: 0 of 12288 bytes > 1433.2 89 2055.4 125 > Should add 3.3 stable disk in question da1: avail memory = 30035968 (29332K bytes) Preloaded elf kernel "kernel" at 0xc02b5000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02b509c. Probing for devices on PCI bus 0: iha0: rev 0x02 int a irq 9 on pci0.14.0 iha0: Reset SCSI Bus ... fxp0: rev 0x05 int a irq 11 on pci0.15.0 fxp0: Ethernet address 00:90:27:42:14:bb chip0: rev 0x01 on pci0.16.0 chip1: rev 0x01 on pci0.18.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-8 wd0: 514MB (1054368 sectors), 1046 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , 32-bit, multi-block-8 wd1: 514MB (1054368 sectors), 1046 cyls, 16 heads, 63 S/T, 512 B/S ppc0 not found vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: 387 emulator Waiting 15 seconds for SCSI devices to settle da0 at iha0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da1 at iha0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 2006MB (4110000 512 byte sectors: 255H 63S/T 255C) changing root device to wd0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 12 7:21:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp2.free.fr (smtp2.free.fr [212.27.32.6]) by hub.freebsd.org (Postfix) with ESMTP id 6586214DFC; Fri, 12 Nov 1999 07:21:39 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr ([213.228.23.183]) by smtp2.free.fr (8.9.3/8.9.3/Debian/GNU) with ESMTP id QAA31815; Fri, 12 Nov 1999 16:21:07 +0100 Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id RAA12415; Fri, 12 Nov 1999 17:25:27 +0100 (CET) (envelope-from nsouch) Message-ID: <19991112172526.36283@breizh.free.fr> Date: Fri, 12 Nov 1999 17:25:26 +0100 From: Nicolas Souchu To: "Kenneth D. Merry" Cc: BOISSEAU Jean-Philippe , freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Tekram DC 395 References: <3816B0BB.388315AB@sextant.thomson-csf.com> <199910280226.UAA12960@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199910280226.UAA12960@panzer.kdm.org>; from Kenneth D. Merry on Wed, Oct 27, 1999 at 08:26:49PM -0600 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Oct 27, 1999 at 08:26:49PM -0600, Kenneth D. Merry wrote: > >[ CCed to -scsi, as people there might be interested ] > >BOISSEAU Jean-Philippe wrote... >> Hi. >> I'd like to know if there is a work in progress for Tekram DC 395 SCSI >> card. > >Actually, Tekram has written a driver for the card. I don't know much >about the card or driver, but the driver is available at ftp.tekram.com. Nice. > >I have a slightly newer version (1.06, the version on the ftp site is 1.05) >that Erich Chen sent me in early September, but I haven't had a chance to >do much with it. Is yours -current ported? Nicholas -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 12 9:35:51 1999 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 A473D14E93; Fri, 12 Nov 1999 09:35:40 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA35878; Fri, 12 Nov 1999 10:35:30 -0700 (MST) (envelope-from ken) Message-Id: <199911121735.KAA35878@panzer.kdm.org> Subject: Re: Tekram DC 395 In-Reply-To: <19991112172526.36283@breizh.free.fr> from Nicolas Souchu at "Nov 12, 1999 05:25:26 pm" To: nsouch@free.fr (Nicolas Souchu) Date: Fri, 12 Nov 1999 10:35:30 -0700 (MST) Cc: jean-philipe.boisseau@sextant.thomson-csf.com (BOISSEAU Jean-Philippe), freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nicolas Souchu wrote... > On Wed, Oct 27, 1999 at 08:26:49PM -0600, Kenneth D. Merry wrote: > >I have a slightly newer version (1.06, the version on the ftp site is 1.05) > >that Erich Chen sent me in early September, but I haven't had a chance to > >do much with it. > > Is yours -current ported? Nope, just -stable. 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 Nov 12 14:42:14 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front6m.grolier.fr (front6m.grolier.fr [195.36.216.56]) by hub.freebsd.org (Postfix) with ESMTP id E148314D08; Fri, 12 Nov 1999 14:42:07 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-98-223.villette.club-internet.fr [194.158.98.223]) by front6m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id XAA09687; Fri, 12 Nov 1999 23:41:39 +0100 (MET) Date: Sat, 13 Nov 1999 01:05:29 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: Nicolas Souchu Cc: "Kenneth D. Merry" , BOISSEAU Jean-Philippe , freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Tekram DC 395 In-Reply-To: <19991112172526.36283@breizh.free.fr> Message-ID: 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 X-Loop: FreeBSD.org On Fri, 12 Nov 1999, Nicolas Souchu wrote: > On Wed, Oct 27, 1999 at 08:26:49PM -0600, Kenneth D. Merry wrote: > > > >[ CCed to -scsi, as people there might be interested ] > > > >BOISSEAU Jean-Philippe wrote... > >> Hi. > >> I'd like to know if there is a work in progress for Tekram DC 395 SCSI > >> card. > > > >Actually, Tekram has written a driver for the card. I don't know much > >about the card or driver, but the driver is available at ftp.tekram.com. >=20 > Nice. May-be, but your fast CPU will have to deal with about 5 interrupts per actual IO instead of about 1 using a SCSI chip that has a hardware phase engine. Given the difference in price against the DC 390/F, I am not sure= =20 the DC 395 is an interesting SCSI controller for an O/S like FreeBSD that= =20 offers a state of the art SCSI access method. The DC-395 looks like hardware for clueless Win95 users to me. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 13 6:38:16 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id CB71214E81 for ; Sat, 13 Nov 1999 06:38:12 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id JAA79946 for ; Sat, 13 Nov 1999 09:38:12 -0500 (EST) (envelope-from mike@sentex.net) Received: from ospf-mdt.sentex.net (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id JAA18370 for ; Sat, 13 Nov 1999 09:38:10 -0500 (EST) From: mike@sentex.net (Mike Tancsa) To: freebsd-scsi@FreeBSD.ORG Subject: Re: AIWA DDS-2 drives? Date: Sat, 13 Nov 1999 14:38:57 GMT Message-ID: <382d76d8.434994158@mail.sentex.net> References: <199911112230.QAA28949@mail.HiWAAY.net> In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 11 Nov 1999 18:09:47 -0500, ken@plutotech.com ("Kenneth D. Merry") wrote: >David Kelly wrote... >> Have found some Aiwa GD-80001HC drives for cheap and wondered if anyone >> has used one under FreeBSD yet? `grep -i aiwa /usr/src/cam` didn't turn >> up anything. So presumably if something is known about this model its >> not bad but that doesn't say if anything good is known either. > >From the web page (http://www.aiwa.com/csd/product/dds2mn.htm), it looks >like just another DDS-2 drive. > >My guess is that they probably just OEM someone else's drive mechanism, but >who knows. It should function fine, but of course you never know until >someone tries it. I dont know about the model above, but the one I got at onsale.com seems to work OK... sa0 at ahc0 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 7) DUMP: finished in 48 seconds, throughput 434 KBytes/sec If you ever need NT drivers, you can get them from the Japanese version of the site. ---MikeOn 11 Nov 1999 18:09:47 -0500, in sentex.lists.freebsd.scsi you wrote: >David Kelly wrote... >> Have found some Aiwa GD-80001HC drives for cheap and wondered if anyone >> has used one under FreeBSD yet? `grep -i aiwa /usr/src/cam` didn't turn >> up anything. So presumably if something is known about this model its >> not bad but that doesn't say if anything good is known either. > >From the web page (http://www.aiwa.com/csd/product/dds2mn.htm), it looks >like just another DDS-2 drive. > >My guess is that they probably just OEM someone else's drive mechanism, but >who knows. It should function fine, but of course you never know until >someone tries it. > >Ken >-- >Kenneth Merry >ken@plutotech.com > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-scsi" in the body of the message > >--- Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 13 7:27:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 98E4B14F74 for ; Sat, 13 Nov 1999 07:27:52 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-147.dialup.HiWAAY.net [216.180.14.147]) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id JAA29165; Sat, 13 Nov 1999 09:27:49 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id JAA88892; Sat, 13 Nov 1999 09:27:46 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199911131527.JAA88892@nospam.hiwaay.net> X-Mailer: exmh version 2.1.0 09/18/1999 To: mike@sentex.net (Mike Tancsa) Cc: freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: AIWA DDS-2 drives? In-reply-to: Message from mike@sentex.net (Mike Tancsa) of "Sat, 13 Nov 1999 14:38:57 GMT." <382d76d8.434994158@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Nov 1999 09:27:45 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Tancsa writes: > On 11 Nov 1999 18:09:47 -0500, ken@plutotech.com ("Kenneth D. Merry") > wrote: > > >David Kelly wrote... > >> Have found some Aiwa GD-80001HC drives for cheap and wondered if anyone > >> has used one under FreeBSD yet? `grep -i aiwa /usr/src/cam` didn't turn > >> up anything. So presumably if something is known about this model its > >> not bad but that doesn't say if anything good is known either. > > > >From the web page (http://www.aiwa.com/csd/product/dds2mn.htm), it looks > >like just another DDS-2 drive. > > > >My guess is that they probably just OEM someone else's drive mechanism, but > >who knows. It should function fine, but of course you never know until > >someone tries it. > > I dont know about the model above, but the one I got at onsale.com seems to > work OK... > > sa0 at ahc0 bus 0 target 0 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 10.000MB/s transfers (10.000MHz, offset 7) > > DUMP: finished in 48 seconds, throughput 434 KBytes/sec Goody! Goody! I've got two coming! And a little ashamed that I was too greedy to mention the source to my friends here until after I secured my quota. :-( Anyhow, they have another lot for sale at the moment but appear to have pulled their "quick buy" page which offered the drive for $96 without the uncertainty of bidding. FYI: $79 was good enough in Friday's auction. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 13 13:21:14 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front3.grolier.fr (front3.grolier.fr [194.158.96.53]) by hub.freebsd.org (Postfix) with ESMTP id 6BD9C14D1C for ; Sat, 13 Nov 1999 13:21:11 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-107-103.villette.club-internet.fr [194.158.107.103]) by front3.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id WAA07681 for ; Sat, 13 Nov 1999 22:21:09 +0100 (MET) Date: Sat, 13 Nov 1999 23:45:03 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: scsi@FreeBSD.org Subject: SYM-0.10.0 available Message-ID: 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 X-Loop: FreeBSD.org I have made available SYM driver 0.10.0. The driver should compile fine=20 under FreeBSD 3.2, 3.3 and -CURRENT. Installation requires the following files: ftp://ftp.tux.org/roudier/drivers/freebsd/experimental/SYM-0.9.0-19991024.t= ar.gz ftp://ftp.tux.org/roudier/drivers/freebsd/experimental/PATCH-SYM-0.10.0-199= 91111gz ftp://ftp.tux.org/roudier/drivers/freebsd/experimental/README.sym The latest change-log entry looks like the following: * SYM-0.10.0-19991111 (diff file PATCH-SYM-0.10.0-19991111) Add support for Alpha - UNTESTED. Consists in some minor changes picked= =20 mostly from the ncr driver and some others as ahc_pci.c. Fix the LED support through GPIO0 for pre-896 chips. In fact some code=20 was wrongly conditionned by something that was never met. Switch driver status to BETA-RELEASE given that this driver has been rock= =20 solid even if a small number of users seems to actually use it. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message