From owner-freebsd-scsi Sun Mar 17 09:56:32 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA25848 for freebsd-scsi-outgoing; Sun, 17 Mar 1996 09:56:32 -0800 (PST) Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA25839 for ; Sun, 17 Mar 1996 09:56:29 -0800 (PST) Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id MAA08586 for scsi@freebsd.org; Sun, 17 Mar 1996 12:56:27 -0500 (EST) From: "matthew c. mead" Message-Id: <199603171756.MAA08586@neon.Glock.COM> Subject: more IOmega JAZ drive problem information To: scsi@freebsd.org Date: Sun, 17 Mar 1996 12:56:27 -0500 (EST) X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently mailed about the jaz drive problems I'm having with -current (as of today 11am from sup2). It seems that the JAZ drive can be mounted and unmounted as many times as desired, as long as it has not spun down after 30 minutes of activity. If it has done so and is mounted at the time, it will spin back up and allow itself to be accessed. However, once unmounted after spinning back up, it can no longer be mounted. If it has slept while not mounted, it also can no longer be mounted. Anyone have any ideas? Anyone looking at tackling this that I could help debug for? Thanks! -matt -- Matthew C. Mead mmead@Glock.COM http://www.Glock.COM/~mmead/ From owner-freebsd-scsi Sun Mar 17 14:51:00 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA11792 for freebsd-scsi-outgoing; Sun, 17 Mar 1996 14:51:00 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA11784 for ; Sun, 17 Mar 1996 14:50:56 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA06547; Sun, 17 Mar 1996 23:50:43 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA27652; Sun, 17 Mar 1996 23:50:42 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id XAA22725; Sun, 17 Mar 1996 23:44:26 +0100 (MET) From: J Wunsch Message-Id: <199603172244.XAA22725@uriah.heep.sax.de> Subject: Re: more IOmega JAZ drive problem information To: scsi@freebsd.org Date: Sun, 17 Mar 1996 23:44:25 +0100 (MET) Cc: mmead@Glock.COM (matthew c. mead) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603171756.MAA08586@neon.Glock.COM> from "matthew c. mead" at Mar 17, 96 12:56:27 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As matthew c. mead wrote: > I recently mailed about the jaz drive problems I'm having > with -current (as of today 11am from sup2). It seems that the > JAZ drive can be mounted and unmounted as many times as desired, > as long as it has not spun down after 30 minutes of activity. If > it has done so and is mounted at the time, it will spin back up > and allow itself to be accessed. However, once unmounted after > spinning back up, it can no longer be mounted. If it has slept > while not mounted, it also can no longer be mounted. Anyone have > any ideas? Anyone looking at tackling this that I could help > debug for? Thanks! Weird. Any chance that you'll get a SCSI Reference Manual from them? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sun Mar 17 14:58:57 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA12323 for freebsd-scsi-outgoing; Sun, 17 Mar 1996 14:58:57 -0800 (PST) Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA12290 for ; Sun, 17 Mar 1996 14:58:25 -0800 (PST) Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au id <28441-0@bunyip.cc.uq.oz.au>; Mon, 18 Mar 1996 08:55:57 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id IAA03729; Mon, 18 Mar 1996 08:56:00 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id WAA04935; Sun, 17 Mar 1996 22:58:44 GMT Message-Id: <199603172258.WAA04935@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: risner@stdio.com cc: freebsd-SCSI@freebsd.org Subject: Re: Disk problems In-reply-to: Your message of "Fri, 15 Mar 1996 16:11:15 GMT." <199603151611.QAA00196@install.stdio.com> X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Mar 1996 08:58:43 +1000 From: Stephen Hocking Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have having several problems with 2.2-SNAP 3-3 *AND* 2.1-RELEASE. > > 8 meg, 486-sx-25 ASUS VL/I-486SV2GX4, SMC ethernet > > SCSI = FDC 850 8bit "seagate" > 1 conner 100 meg (Digital RZ23 SCSI) > 1 seagate 235 meg ST1239N > 1 Emulex ESDI - SCSI with one ESDI disk formatted > > > I got it installed on the Seagate, but when adding the other disks I noticed > that the FDC/Seagate controller boots from ID 6 down. FreeBSD assigns disks > from ID 0 and up, so it can't mount the root with more than one disk installed. > > I placed the Emulex on board and booted fine after It was installed on the > Seagate. I used "scsiformat -w sd1" to format the ESDI/SCSI disk. > Then reboot to find it not booting because the New ESDI is BIOS booted > and it is clean. I took it off and moved the seagate disk to ID 6. > > But NOW that I have it installed I get "sea: abritration timeout" a lot > when I add either the Conner or Emulex to the board. > > The seagate driver does not like anything to be at address 6 when it is running on a future domain controller. I've successfully run things from ID 0. I must admit that I've never had the chance to test it's handling of LUNs, and the controller that I used to have has passed out of my hands. I would advise getting hold of an old Adaptec 1542 or Buslogic controller (or failing that, one of the supported VLB controllers). The FD maxes out at 1Mb/s, and uses 100% of any CPU at that data transfer rate. Stephen -- I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that! From owner-freebsd-scsi Sun Mar 17 15:18:09 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA13707 for freebsd-scsi-outgoing; Sun, 17 Mar 1996 15:18:09 -0800 (PST) Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA13697 for ; Sun, 17 Mar 1996 15:18:06 -0800 (PST) Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id SAA02511; Sun, 17 Mar 1996 18:14:15 -0500 (EST) From: "matthew c. mead" Message-Id: <199603172314.SAA02511@neon.Glock.COM> Subject: Re: more IOmega JAZ drive problem information To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 17 Mar 1996 18:14:15 -0500 (EST) Cc: scsi@freebsd.org In-Reply-To: <199603172244.XAA22725@uriah.heep.sax.de> from "J Wunsch" at Mar 17, 96 11:44:25 pm X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch writes: > As matthew c. mead wrote: > > I recently mailed about the jaz drive problems I'm having > > with -current (as of today 11am from sup2). It seems that the > > JAZ drive can be mounted and unmounted as many times as desired, > > as long as it has not spun down after 30 minutes of activity. If > > it has done so and is mounted at the time, it will spin back up > > and allow itself to be accessed. However, once unmounted after > > spinning back up, it can no longer be mounted. If it has slept > > while not mounted, it also can no longer be mounted. Anyone have > > any ideas? Anyone looking at tackling this that I could help > > debug for? Thanks! Oops, I forgot to mention. No matter what happens with its spindown spinup activity, you cannot get it to eject once you have used it under FreeBSD. The little button that normally ejects it will not eject the cartridge unless you reboot and try to eject it before you use it under FreeBSD. > Weird. Any chance that you'll get a SCSI Reference Manual from them? Hmm. I hadn't even thought about trying. I suppose I could, though. Do you know if it is something I'll have to sign an NDA for? -matt -- Matthew C. Mead mmead@Glock.COM http://www.Glock.COM/~mmead/ From owner-freebsd-scsi Sun Mar 17 19:47:10 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA26071 for freebsd-scsi-outgoing; Sun, 17 Mar 1996 19:47:10 -0800 (PST) Received: from burdell.cc.gatech.edu (root@burdell.cc.gatech.edu [130.207.3.207]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA26064 for ; Sun, 17 Mar 1996 19:47:07 -0800 (PST) Received: from oscar.cc.gatech.edu (cau@oscar.cc.gatech.edu [130.207.107.12]) by burdell.cc.gatech.edu (8.7.1/8.6.9) with ESMTP id WAA22923; Sun, 17 Mar 1996 22:46:57 -0500 (EST) Received: (from cau@localhost) by oscar.cc.gatech.edu (8.7.1/8.6.9) id WAA17745; Sun, 17 Mar 1996 22:46:56 -0500 (EST) From: cau@cc.gatech.edu (Carlos Ugarte) Message-Id: <199603180346.WAA17745@oscar.cc.gatech.edu> Subject: Re: Tips on developing a new SCSI driver? To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 17 Mar 1996 22:46:55 -0500 (EST) Cc: freebsd-scsi@freebsd.org, cau@cc.gatech.edu In-Reply-To: <199603152034.VAA02233@uriah.heep.sax.de> from "J Wunsch" at Mar 15, 96 09:34:35 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [about a FD scsi driver] > I didn't see your message there. Nope, it's not a closed list, and i > would encourage to discuss SCSI internals there instead of the noisy > -hackers list. > > There's no written documentation, i think. However, those guys who > wrote the other SCSI drivers might be a good help for you. After all, > the FD16XX series driver is an FRI! (Frequently Requested Item) Hmm, that's strange. I know I did subscribe, and if I ask majordomo, it'll tell me I am signed up ("who freebsd-scsi"). I don't recall seeing any traffic there either, maybe I should pay more attention (-hackers, -questions and -current seem to be used most often). With any luck, I should be able to do something productive. Carlos -- Carlos A. Ugarte cau@cc.gatech.edu Author of PageMage, a virtual desktop util for OS/2 http://www.cc.gatech.edu/people/home/cau/ Computer Science Senior at Georgia Tech From owner-freebsd-scsi Sun Mar 17 22:19:40 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA02186 for freebsd-scsi-outgoing; Sun, 17 Mar 1996 22:19:40 -0800 (PST) Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA02179 for ; Sun, 17 Mar 1996 22:19:37 -0800 (PST) Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id BAA00342 for scsi@freebsd.org; Mon, 18 Mar 1996 01:19:36 -0500 (EST) From: "matthew c. mead" Message-Id: <199603180619.BAA00342@neon.Glock.COM> Subject: a little bit more information on the jaz drive situation... To: scsi@freebsd.org Date: Mon, 18 Mar 1996 01:19:36 -0500 (EST) X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok, I've got some more information for ya, folks! Somewhere in between 2.1.0R and -current, a bug must have crept in. Since I've started running -current (cause it makes the Jaz drive sleep/unsleep properly while it's mounted), I haven't used my SyQuest EZ135 Drive. I tried it tonight. If I mount it, unmount it, and then hit eject, it doesn't eject! It DID under 2.1.0R... It seems like somehow the unmount code isn't telling the drives they are no longer busy... any ideas? I'll keep playing... -matt -- Matthew C. Mead mmead@Glock.COM http://www.Glock.COM/~mmead/ From owner-freebsd-scsi Sun Mar 17 22:28:51 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA02501 for freebsd-scsi-outgoing; Sun, 17 Mar 1996 22:28:51 -0800 (PST) Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA02480 Sun, 17 Mar 1996 22:28:47 -0800 (PST) Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id BAA00389; Mon, 18 Mar 1996 01:28:45 -0500 (EST) From: "matthew c. mead" Message-Id: <199603180628.BAA00389@neon.Glock.COM> Subject: a little more jaz drive info To: scsi@freebsd.org Date: Mon, 18 Mar 1996 01:28:45 -0500 (EST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok, I booted under a 2.1.0R kernel, and found that both my SyQuest EZ135 Drive and my JAZ drive now are able to be mounted, unmounted, ejected, and inserted multiple times. It's pretty clear now that there's some sort of subtle problem with telling removeable scsi devices they're no longer being used once they're umounted under -current. This is probably something we want to fix for the snapshot coming this week, so if someone could help me out with what files to start looking through in the /sys/scsi directory, I'll see if I can turn anything up. Thanks for listening to all this spam! -matt PS - I've CC'd this to current@freebsd.org because I believe it to be important to the development issues being discussed there. If repliers want to remove the CC feel free. -- Matthew C. Mead mmead@Glock.COM http://www.Glock.COM/~mmead/ From owner-freebsd-scsi Sun Mar 17 23:47:18 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA05442 for freebsd-scsi-outgoing; Sun, 17 Mar 1996 23:47:18 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA05435 for ; Sun, 17 Mar 1996 23:47:14 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA12737; Mon, 18 Mar 1996 18:42:33 +1100 Date: Mon, 18 Mar 1996 18:42:33 +1100 From: Bruce Evans Message-Id: <199603180742.SAA12737@godzilla.zeta.org.au> To: mmead@Glock.COM, scsi@freebsd.org Subject: Re: a little bit more information on the jaz drive situation... Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Ok, I've got some more information for ya, folks! Somewhere >in between 2.1.0R and -current, a bug must have crept in. Since >I've started running -current (cause it makes the Jaz drive >sleep/unsleep properly while it's mounted), I haven't used my >SyQuest EZ135 Drive. I tried it tonight. If I mount it, unmount >it, and then hit eject, it doesn't eject! It DID under 2.1.0R... >It seems like somehow the unmount code isn't telling the drives >they are no longer busy... any ideas? I'll keep playing... See PR 1087. Last-close has been broken since approx 1995/03/02 in -current. Bruce From owner-freebsd-scsi Mon Mar 18 00:47:12 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA09697 for freebsd-scsi-outgoing; Mon, 18 Mar 1996 00:47:12 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA09692 for ; Mon, 18 Mar 1996 00:47:08 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id TAA15474; Mon, 18 Mar 1996 19:44:18 +1100 Date: Mon, 18 Mar 1996 19:44:18 +1100 From: Bruce Evans Message-Id: <199603180844.TAA15474@godzilla.zeta.org.au> To: bde@zeta.org.au, mmead@Glock.COM, scsi@freebsd.org Subject: Re: a little bit more information on the jaz drive situation... Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >See PR 1087. Last-close has been broken since approx 1995/03/02 >in -current. Oops. Actually on since approx. 1996/03/02. Bruce From owner-freebsd-scsi Mon Mar 18 00:51:28 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA09841 for freebsd-scsi-outgoing; Mon, 18 Mar 1996 00:51:28 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA09836 for ; Mon, 18 Mar 1996 00:51:18 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA15771 for ; Mon, 18 Mar 1996 09:50:37 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA01575 for freebsd-scsi@freebsd.org; Mon, 18 Mar 1996 09:50:37 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA25325 for freebsd-scsi@freebsd.org; Mon, 18 Mar 1996 09:39:33 +0100 (MET) From: J Wunsch Message-Id: <199603180839.JAA25325@uriah.heep.sax.de> Subject: Re: Tips on developing a new SCSI driver? To: freebsd-scsi@freebsd.org Date: Mon, 18 Mar 1996 09:39:33 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603180346.WAA17745@oscar.cc.gatech.edu> from "Carlos Ugarte" at Mar 17, 96 10:46:55 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Carlos Ugarte wrote: > > I didn't see your message there. > Hmm, that's strange. I know I did subscribe, and if I ask > majordomo, it'll tell me I am signed up ("who freebsd-scsi"). This message was sent to me from owner-freebsd-scsi, so it should be okay now? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Mon Mar 18 00:51:53 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA09868 for freebsd-scsi-outgoing; Mon, 18 Mar 1996 00:51:53 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA09831 for ; Mon, 18 Mar 1996 00:51:13 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA15805; Mon, 18 Mar 1996 09:50:53 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA01583; Mon, 18 Mar 1996 09:50:52 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA25408; Mon, 18 Mar 1996 09:46:00 +0100 (MET) From: J Wunsch Message-Id: <199603180846.JAA25408@uriah.heep.sax.de> Subject: Re: more IOmega JAZ drive problem information To: scsi@freebsd.org Date: Mon, 18 Mar 1996 09:45:59 +0100 (MET) Cc: mmead@Glock.COM (matthew c. mead) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603172314.SAA02511@neon.Glock.COM> from "matthew c. mead" at Mar 17, 96 06:14:15 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As matthew c. mead wrote: > > Weird. Any chance that you'll get a SCSI Reference Manual from them? > > Hmm. I hadn't even thought about trying. I suppose I > could, though. Do you know if it is something I'll have to sign > an NDA for? No idea. Give it a try, and ask them. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Mon Mar 18 04:25:12 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA19307 for freebsd-scsi-outgoing; Mon, 18 Mar 1996 04:25:12 -0800 (PST) Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA19302 for ; Mon, 18 Mar 1996 04:25:10 -0800 (PST) Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id HAA03147; Mon, 18 Mar 1996 07:24:13 -0500 (EST) From: "matthew c. mead" Message-Id: <199603181224.HAA03147@neon.Glock.COM> Subject: Re: a little bit more information on the jaz drive situation... To: bde@zeta.org.au (Bruce Evans) Date: Mon, 18 Mar 1996 07:24:13 -0500 (EST) Cc: bde@zeta.org.au, scsi@freebsd.org In-Reply-To: <199603180844.TAA15474@godzilla.zeta.org.au> from "Bruce Evans" at Mar 18, 96 07:44:18 pm X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans writes: > >See PR 1087. Last-close has been broken since approx 1995/03/02 > >in -current. > Oops. Actually on since approx. 1996/03/02. Who's currently handling this? As all things go I'm probably a pretty green SCSI hacker, but if there isn't someone working on it, I'll fix it. -matt -- Matthew C. Mead mmead@Glock.COM http://www.Glock.COM/~mmead/ From owner-freebsd-scsi Mon Mar 18 04:43:08 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA19815 for freebsd-scsi-outgoing; Mon, 18 Mar 1996 04:43:08 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA19806 for ; Mon, 18 Mar 1996 04:43:04 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id XAA25438; Mon, 18 Mar 1996 23:40:45 +1100 Date: Mon, 18 Mar 1996 23:40:45 +1100 From: Bruce Evans Message-Id: <199603181240.XAA25438@godzilla.zeta.org.au> To: bde@zeta.org.au, mmead@Glock.COM Subject: Re: a little bit more information on the jaz drive situation... Cc: scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >See PR 1087. Last-close has been broken since approx 1995/03/02 >> >in -current. >> Oops. Actually on since approx. 1996/03/02. > Who's currently handling this? As all things go I'm >probably a pretty green SCSI hacker, but if there isn't someone >working on it, I'll fix it. I hope that it will be handled by a vm person. It has nothing to do with SCSI. See PR 1087 for a temporary (wrong) fix. Bruce From owner-freebsd-scsi Mon Mar 18 14:45:12 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA08397 for freebsd-scsi-outgoing; Mon, 18 Mar 1996 14:45:12 -0800 (PST) Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA08370 for ; Mon, 18 Mar 1996 14:45:08 -0800 (PST) Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id RAA00354; Mon, 18 Mar 1996 17:44:25 -0500 (EST) From: "matthew c. mead" Message-Id: <199603182244.RAA00354@neon.Glock.COM> Subject: Re: a little bit more information on the jaz drive situation... To: bde@zeta.org.au (Bruce Evans) Date: Mon, 18 Mar 1996 17:44:25 -0500 (EST) Cc: bde@zeta.org.au, scsi@freebsd.org In-Reply-To: <199603181240.XAA25438@godzilla.zeta.org.au> from "Bruce Evans" at Mar 18, 96 11:40:45 pm X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans writes: > >> >See PR 1087. Last-close has been broken since approx 1995/03/02 > >> >in -current. > >> Oops. Actually on since approx. 1996/03/02. > > Who's currently handling this? As all things go I'm > >probably a pretty green SCSI hacker, but if there isn't someone > >working on it, I'll fix it. > I hope that it will be handled by a vm person. It has nothing to do > with SCSI. See PR 1087 for a temporary (wrong) fix. The suggestion you made about ffs_unmount() and vn_close() halfway worked. I reversed the order of the calls, and the drives are now able to eject once they've been unmounted. Unfortunately, however, something is still wrong because if you try to reinsert the cartridge and mount it again, it ends up complaining that the device is busy. I'm guessing here, but does this have something to do with some other counter not being decremented properly so that the kernel thinks the device is still being used? -matt -- Matthew C. Mead mmead@Glock.COM http://www.Glock.COM/~mmead/ From owner-freebsd-scsi Mon Mar 18 23:00:25 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA10973 for freebsd-scsi-outgoing; Mon, 18 Mar 1996 23:00:25 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA10963 for ; Mon, 18 Mar 1996 23:00:19 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id RAA06722; Tue, 19 Mar 1996 17:54:14 +1100 Date: Tue, 19 Mar 1996 17:54:14 +1100 From: Bruce Evans Message-Id: <199603190654.RAA06722@godzilla.zeta.org.au> To: bde@zeta.org.au, mmead@Glock.COM Subject: Re: a little bit more information on the jaz drive situation... Cc: scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The suggestion you made about ffs_unmount() and >vn_close() halfway worked. I reversed the order of the calls, >and the drives are now able to eject once they've been unmounted. >Unfortunately, however, something is still wrong because if you >try to reinsert the cartridge and mount it again, it ends up >complaining that the device is busy. I'm guessing here, but does >this have something to do with some other counter not being >decremented properly so that the kernel thinks the device is >still being used? Try the fix in -current. The bug affects my zip drive too. It worked a week or two ago, but not today for ufs mounted file systems. It still works for ext2fs mounted file systems because there is no vmio stuff for ext2fs. Bruce From owner-freebsd-scsi Mon Mar 18 23:50:57 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA12419 for freebsd-scsi-outgoing; Mon, 18 Mar 1996 23:50:57 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA12413 for ; Mon, 18 Mar 1996 23:50:51 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA22798; Tue, 19 Mar 1996 08:50:45 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA22858; Tue, 19 Mar 1996 08:50:44 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id IAA01862; Tue, 19 Mar 1996 08:46:57 +0100 (MET) From: J Wunsch Message-Id: <199603190746.IAA01862@uriah.heep.sax.de> Subject: Re: a little bit more information on the jaz drive situation... To: scsi@freebsd.org Date: Tue, 19 Mar 1996 08:46:57 +0100 (MET) Cc: mmead@Glock.COM (matthew c. mead) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603182244.RAA00354@neon.Glock.COM> from "matthew c. mead" at Mar 18, 96 05:44:25 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As matthew c. mead wrote: > I'm guessing here, but does > this have something to do with some other counter not being > decremented properly so that the kernel thinks the device is > still being used? Hmm, the last close of the SCSI device driver should also reset its internal `opened' flag. Perhaps you can track it down with DDB? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Tue Mar 19 00:21:45 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA13774 for freebsd-scsi-outgoing; Tue, 19 Mar 1996 00:21:45 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA13768 for ; Tue, 19 Mar 1996 00:21:39 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA23747; Tue, 19 Mar 1996 09:20:45 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA23072; Tue, 19 Mar 1996 09:20:43 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA02121; Tue, 19 Mar 1996 09:11:26 +0100 (MET) From: J Wunsch Message-Id: <199603190811.JAA02121@uriah.heep.sax.de> Subject: Re: SCSI death in -current with DAT To: freebsd-scsi@freebsd.org Date: Tue, 19 Mar 1996 09:11:26 +0100 (MET) Cc: mrl@teleport.com (Mostyn/Annabella) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603190331.TAA04150@linda.teleport.com> from "Mostyn/Annabella" at Mar 18, 96 07:31:48 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (Moved to freebsd-scsi, fits better there.) As Mostyn/Annabella wrote: > This, with a St. Patrick's Day -current. (Please, keep in mind that this is a project with volunteers scattered around the earth. I don't even have the slightest idea what "St. Patrick's Day" might be, i often do already having a hard time in computing time zone differences and translate "AM" or "PM" into something useful for me. :-) > (ahc0:0:0): "ARCHIVE Python 28388-XXX 5.45" type 1 removable SCSI 2 > I could force fixed blocks by hand in st.c but I'd prefer a genuine fix. Do you really wanna say that an Archive Python doesn't grok variable blocks at all??? This would be very surprising, though the fix is rather simple (if it's really this). I can't really believe it, but just as an experiment, try this: Index: sys_scsi/scsiconf.c =================================================================== RCS file: /home/ncvs/src/sys/scsi/scsiconf.c,v retrieving revision 1.57 diff -u -u -r1.57 scsiconf.c --- scsiconf.c 1996/03/10 07:13:10 1.57 +++ scsiconf.c 1996/03/19 08:10:26 @@ -228,6 +228,13 @@ {1024, ST_Q_FORCE_FIXED_MODE, DDS}, /* minor 8,9,10,11 */ {0, ST_Q_FORCE_VAR_MODE, DDS} /* minor 12,13,14,15 */ }; +static st_modes mode_python28388 = + { + {512, ST_Q_FORCE_FIXED_MODE, DDS}, /* minor 0,1,2,3 */ + {512, ST_Q_FORCE_FIXED_MODE, DDS}, /* minor 4,5,6,7 */ + {1024, ST_Q_FORCE_FIXED_MODE, DDS}, /* minor 8,9,10,11 */ + {0, ST_Q_FORCE_VAR_MODE, DDS} /* minor 12,13,14,15 */ + }; static st_modes mode_unktape = { {0, 0, 0}, /* minor 0,1,2,3 */ @@ -287,6 +294,10 @@ { T_SEQUENTIAL, T_SEQUENTIAL, T_REMOV, "WangDAT", "Model 1300", "*", "st", SC_ONE_LU, 0, mode_wangdat1300 + }, + { + T_SEQUENTIAL, T_SEQUENTIAL, T_REMOV, "ARCHIVE", "Python 28388", "*", + "st", SC_ONE_LU, 0, mode_python28388 }, { T_SEQUENTIAL, T_SEQUENTIAL, T_REMOV, "*", "*", "*", -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Tue Mar 19 05:45:51 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA28576 for freebsd-scsi-outgoing; Tue, 19 Mar 1996 05:45:51 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA28547 for ; Tue, 19 Mar 1996 05:45:10 -0800 (PST) Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id FAA26907 for ; Tue, 19 Mar 1996 05:45:04 -0800 Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id IAA04250; Tue, 19 Mar 1996 08:41:45 -0500 (EST) From: "matthew c. mead" Message-Id: <199603191341.IAA04250@neon.Glock.COM> Subject: Re: a little bit more information on the jaz drive situation... To: bde@zeta.org.au (Bruce Evans) Date: Tue, 19 Mar 1996 08:41:45 -0500 (EST) Cc: bde@zeta.org.au, scsi@freebsd.org In-Reply-To: <199603190654.RAA06722@godzilla.zeta.org.au> from "Bruce Evans" at Mar 19, 96 05:54:14 pm X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans writes: > > The suggestion you made about ffs_unmount() and > >vn_close() halfway worked. I reversed the order of the calls, > >and the drives are now able to eject once they've been unmounted. > >Unfortunately, however, something is still wrong because if you > >try to reinsert the cartridge and mount it again, it ends up > >complaining that the device is busy. I'm guessing here, but does > >this have something to do with some other counter not being > >decremented properly so that the kernel thinks the device is > >still being used? > Try the fix in -current. I'll sup it and try it out tonight. For temporary use I've got the "> 2" patch installed so I can back things up normally, but I'd like to have a real fix... > The bug affects my zip drive too. It worked a week or two ago, but > not today for ufs mounted file systems. It still works for ext2fs > mounted file systems because there is no vmio stuff for ext2fs. I haven't played with ext2fs at all - might be a reason to play with caldera at some point. The bug affected my JAZ and my EZ135 drives... -matt -- Matthew C. Mead mmead@Glock.COM http://www.Glock.COM/~mmead/ From owner-freebsd-scsi Tue Mar 19 05:55:31 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA29551 for freebsd-scsi-outgoing; Tue, 19 Mar 1996 05:55:31 -0800 (PST) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA29524 for ; Tue, 19 Mar 1996 05:55:22 -0800 (PST) Received: by Sisyphos id AA19879 (5.67b/IDA-1.5 for freebsd-scsi@freebsd.org); Tue, 19 Mar 1996 14:54:21 +0100 Message-Id: <199603191354.AA19879@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Tue, 19 Mar 1996 14:54:21 +0100 X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: freebsd-scsi@freebsd.org Subject: HP DAT switches ... Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The following information regarding HP DAT drives has been posted to "Comp.periphs.scsi" on Nov. 21st, 1994. It should still apply, AFAIK ... The signature of the original poster is: ----------------------------------------------------------------- Kevin Jones. | Hewlett Packard Ltd, | Computer Peripherals Bristol, kev%hpcpbla@hplb.hpl.hp.com | Filton Road, | Stoke Gifford, | Bristol. BS12 6QZ. | ENGLAND. ----------------------------------------------------------------- This response does not represent the official position of, or statement by, the Hewlett-Packard Company. The above data is provided for informational purposes only. It is supplied without warranty of any kind. ################################################################### Here is a summary of how HP DAT drive configuration switches work. For those not familiar with SCSI, some of the descriptions will make little sense. ==================================================================== HP35470A, HP35480A, C1533A, C1553A DDS DRIVE CONFIGURATION SWITCHES ------------------------------------------------------- Note: The data supplied applies to drives containing standard distributor product code. A drive with this code will report "09" in bytes 34 and 35 of its standard SCSI Inquiry data. Even if it does not report "09", it is possible (though not certain) that its switch configurations are very similar to the description below. There are 8 configuration switches on the underside of the drive. These are numbered 1 thru 8. SWITCHES 1+2 ----------------- These control data compression on the HP35480. (The 35470 does not have data compression circuitry. These switches should be left set to "1" in the 35470). When data compression is ENABLED the drive (HP35480) will write compressed data in DDS-DC format. When compression is disabled, the drive will write DDS format data. Note that the drive will read and de-compress DDS-DC written tapes irrespective of whether compression is ENABLED or DISABLED, ie. switching compression on/off only applies to WRITES. SWITCH1 = 1 means the drive defaults to writing DDS-DC format data. = 0 means the drive defaults to writing DDS format data. HP35470A drives cannot de-compress data from DDS-DC format tapes. The 35470A can return the compressed data via SCSI for a host to de-compress. The level of support for decompressing DAT data in host drivers is currently NIL, so for practical purposes, it is reasonable to say that you can't read a DDS-DC tape with a non compressing drive. (Note: Default compression may also be controlled via a pin on the rear of the drive. This enables some boxed drives to have a compression on/off selector switch). SWITCH2 = 1 means the host has the ability to turn compression on/off via the SCSI Mode Select command (data compression mode page). Thus the drive powers up with compression determined by switch1, but the host may subsequently use a Mode Select command to ENABLE/DISABLE compression. (Note: some UNIX systems, eg HP-UX have drivers which select compression using Mode Select depending on minor numbers in the device file.) = 0 means that the drive ignores host requests to change compression. Furthermore, a 35480 drive with this switch "0" will report that it is a 35470 drive in its Inquiry data. It is reccomended that both switches 1 and 2 be set "ON". SWITCHES 3 TO 8 --------------------- These switches configure various SCSI "features". Note that there is no 1-1 mapping of features to switches. A specific pattern of switches will enable a SET OF FEATURES. There are 2 tables below which map switch settings to feature sets. The Left hand column of these tables specifies "host", and a 3rd table shows additional features that are configured depending on the host. eg. If you want "EWEOM on read error", "Switch Buffered" and "Caution Hard Error" features only, then switch setting 111100 (for both tables) will do this. (111100 enables hosts of type "Other" which results in the "EWEOM on read error" feature being enabled). ------------------------------------------------------------------------------ | Host | Switch | Perfor | Caution | Default | Parity | No Data || Switches| | | Buffered | mance | hard | Fixed | off | phase || | | | | | error | Mode | | discon || 345678 | |-----------------------------------------------------------------------------| | HP | 1 | | 1 | | | || 111111 | | HP | 1 | | | | | || 110111 | | HP | 1 | 1 | 1 | | | || 111011 | | DEC | 1 | | 1 | | | || 111110 | | DEC | 1 | 1 | 1 | | | || 111010 | | DEC | 1 | 1 | | | | || 110010 | | Other | 1 | | 1 | | | || 111100 | | Other | 1 | | 1 | | | 1 || 011100 | | Other | 1 | | 1 | | 1 | || 101100 | | Other | 1 | | 1 | | 1 | 1 || 001100 | | Other | 1 | | 1 | 1 | | || 110100 | | Other | 1 | | 1 | 1 | | 1 || 010100 | | Other | 1 | | 1 | 1 | 1 | || 100100 | | Other | 1 | | 1 | 1 | 1 | 1 || 000100 | | Other | 1 | 1 | 1 | | | || 111000 | | Other | 1 | 1 | | | | || 110001 | | Other | 1 | 1 | 1 | | | 1 || 011000 | | Other | 1 | 1 | | | | 1 || 010001 | | Other | 1 | 1 | 1 | | 1 | || 101000 | | Other | 1 | 1 | | | 1 | || 100001 | | Other | 1 | 1 | 1 | | 1 | 1 || 001000 | | Other | 1 | 1 | 1 | 1 | | || 110000 | | Other | 1 | 1 | 1 | 1 | | 1 || 010000 | | Other | 1 | 1 | 1 | 1 | 1 | || 100000 | | Other | 1 | 1 | 1 | 1 | 1 | 1 || 000000 | | Other | | | 1 | | | || 111101 | | Other | | 1 | 1 | | | || 111001 | ------------------------------------------------------------------------------ Distributor Switch Selections -- until 35470A version 9.47 until 35480A version 9.49 (inclusive) ------------------------------------------------------------------------------------||--------- | Host | MRS | Perfor | Caution | Def | Parity | No Data | Inq | Fix | DC_ctrl || Switches| | | ON | mance | hard | Fixed | off | phase | 35480 | 512 | _by_ || | | | | | error | Mode | | discon | | | density || 345678 | |-----------------------------------------------------------------------------------||---------| | HP | | | 1 | | | | | | || 111111 | | HP | 1 | | 1 | | | | | | || 011111 | | HP | | | | | | | | | || 110111 | | HP | 1 | | | | | | | | || 010111 | | HP | | 1 | 1 | | | | | | || 111011 | | HP | 1 | 1 | 1 | | | | | | || 011011 | | HP | | | 1 | | | | 1 | | || 100011 | | DEC | | | 1 | | | | | | || 111110 | | DEC | 1 | | 1 | | | | | | || 011110 | | DEC | | 1 | 1 | | | | | | || 111010 | | DEC | 1 | 1 | 1 | | | | | | || 011010 | | DEC | | 1 | 1 | | | 1 | | | || 101010 | | DEC | 1 | 1 | 1 | | | 1 | | | || 001010 | | Other | 1 | | 1 | 1 | | | | | || 110101 | | Other | 1 | 1 | 1 | | | | | | || 111001 | | Other | 1 | 1 | 1 | | | 1 | | | || 011001 | | Other | 1 | 1 | 1 | | 1 | | | | || 101001 | | Other | 1 | 1 | 1 | | 1 | 1 | | | || 001001 | | Other | 1 | 1 | 1 | 1 | | 1 | | | || 010001 | | Other | 1 | 1 | 1 | 1 | 1 | 1 | | | || 000001 | | Other | | | 1 | | | | | | || 111100 | | Other | | 1 | 1 | | | | | | 1 || 001100 | | Other | | | 1 | 1 | | | | | || 110100 | | Other | | 1 | 1 | | | | | | || 111000 | | Other | | 1 | 1 | | | 1 | | | || 011000 | | Other | | 1 | 1 | | 1 | | | | || 101000 | | Other | | 1 | 1 | | 1 | 1 | | | || 001000 | | Other | | 1 | 1 | | | | | 1 | || 110000 | | Other | | 1 | 1 | 1 | | 1 | | | || 010000 | | Other | | 1 | 1 | 1 | 1 | 1 | | | || 000000 | ------------------------------------------------------------------------------------||---------| Distributor Switch Selections -- after 35470A version 9.47 after 35480A version 9.49 (inclusive) The reason for the 2 tables is that the mappings changed for newer firmware revs. This was not a good idea (IMHO), but life's like that. You can find out "partly" what rev of firmware you have by looking at bytes 32 and 33 of the standard inquiry data. This will tell you the major number of the revision. If its rev8 or less then use the "old" table, if its rev10 or higher, use the newer table. If its rev9 then you would have to recover the 0xC0 Inquiry vital product data page which contains (in ASCII) full details of the firmware rev. If you can't figure out what rev of firmware you have then you'll just have to "experiment" with settings from both tables. Rev's 9.47/9.49 shipped until approx Feb 1993. The following table describes "extra" features enabled for hosts of type "HP" "DEC" and "Other".... ------------------------------------------------------------------------------ | Host | Async | EWEOM | Write | No | Attn | Full | Signed | Trunc | | | Sense | on read | Zero | EWEOM | After | Reset | Residue | Inquiry | | | error | FM | residue | Load | | 76543 | by 3 | |----------------------------------------------------------------------------| | HP | 1 | 1 | 1 | 1 | 1 | | | | | DEC | | | | | | 1 | 1 | 1 | | Other| | 1 | | | | | | | ------------------------------------------------------------------------------ Asyncronous sense ---------------------- TRUE: The mark bit may be set on asynchronous request sense. FALSE: The mark bit will never be set on asynchronous request sense. Comments: This feature is used on some HP-UX systems whose drivers "forget" if they're at a filemark and send a SCSI "request sense" command (in the absence of a pre-ceding check condition) to find out where they are. The effect of this feature being enabled for systems which do not want asynchronous sense should be benign. Attn after load -------------------- TRUE: "Unit Attention" and "Not ready to transition" posted for command subsequent to any load, including those that just rewind or do nothing. Comments: Another HP driver'ism. SOme HP-UX (or it might have been MPE) driver's expect to see SCSI Unit Attention sense after a tape is loaded despite the fact that it was the host that issued the load command. Caution for Hard Error ------------------------ TRUE: If a hard read or write error occurs, resulting in additional sense being set to 1100h (unrecovered read error) or 0C00h (Write error) then display caution on front panel. This indicates that the drive should be cleaned. FALSE: No special LED display for hard read or write errors. DC ctrl by density (Nov 17 1994 and later) --------------------------------------------- TRUE: Enables DC on writes to be enabled by mode select density code 3 and disabled by mode select density code 0. FALSE: Mode select density code has no effect on DC. Mode sense density code indicates drive/tape density. Comments: SUN drivers, Exabyte drives and Exabyte drivers control data compression via the density code. eg. based on device file name or device file minor numbers the driver sends a density code of 0 or 3 on device open. If you want device-file based control of DC on your SUN/whatever system then this is the option for you! EW-EOM on read error ----------------------------- TRUE: EOM bit set for read errors on hitting mark. FALSE: EOM bit only set if at Physical end of partition or media. fixed mode ------------------- TRUE: Default block size is set to 1024 bytes. FALSE: Default block size is set to 0 bytes. Comments: Sme applications (esp. PC based) which are used to talking to QIC drives expect a SCSI fixed block length of 1K. SCSI states that they should configure this with a mode select command, but some packages just assume the drive is pre-configured for 1K fixed size blocks. fix 512 (November 1994 and later) -------------------------------------------- TRUE: Default block size is set to 512 bytes. FALSE: Default block size depends on "fixed mode" Comments: Sme applications (esp. PC based) which are used to talking to QIC drives expect a SCSI fixed block length of 512 bytes. SCSI states that they should configure this with a mode select command, but some packages just assume the drive is pre-configured for 512 byte fixed size blocks. Full reset --------------- TRUE: ``DEC'' defined reset. Tape is rewound. FALSE: Soft reset, drive takes very little action for SCSI reset, logical position unchanged but current command aborted. Comments: You have to be brain dead to want a "full reset". This means you loose logical tape position after a bus reset. immediate ----------------- TRUE: The immediate bit is overridden and assumed to be ``1'' on every command that supports it. ``switch buffered''= FALSE mode is also enforced (see definition below). FALSE: The Immed flags are used. ``switch buffered'' mode is left as-is. Comments: SCSI commands affected include: Load, Rewind, Erase, Write Filemark. Assuming immediate mode for filemarks can drastically improove the performance of systems which fail to set this bit when sending write filemark commands. The downside is that you don't flush data to tape in response to a filemark command, and for some applications this compromises data-integrity checkpointing. infinite flush ------------------ TRUE: Infinite buffer flush timeout (ie write delay time=0). For mode select, write delay time is silently ignored. FALSE: Default write delay time is used. Mode select may be used to re-specify timeout. Comments: Infinite flush means data is left lying around in the buffer for long periods of time (and is subject to LOSS if power fails). The plus side of this is that VERY SLOW applications don't continually stop/start the mechanism (it will flush every 5 seconds by default). ANother plus point of this feature is that you won't loose capacity if the drive flushes partially written groups. Inquiry 35480 ---------------- TRUE: The product ID in the Inquiry data will be HP35480 (even if the drive is a bit more up to date (eg. C1533A or C1553A). This enables some drivers with hard coded product ID's to work with newer drivers (HP-UX S800 9.0 for C1553A, BackupExec on Windows NT for C1533A and C1553A). MRS on ------------ TRUE: MRS (Media recognition system) is implemented. Tapes have to be of DDS grade, otherwise they are treated as write protected and write commands will be rejected with sense key=7, additional sense =3000h. FALSE: MRS is not implemented. You can write any tape you like. no data disconnect ----------------------- TRUE: No disconnect during data phase. NB: save data pointers may still be sent. FALSE: Disconnects may occur during data phase. Comments: Useful for hosts which cannot disconnect on ODD BYTE boundaries. Some SGI hosts can't disconnect on ODD WORD (32 bit) boundaries so this feature should be enabled for SGI connect. Downside = DOn't do SCSI operations exceeding 64Kbytes otherwise the bus could hang-up waiting for device-side I/O. The drive can normally guarantee to have at least 64K of data/space before it starts data phase. no EW-EOM residue ----------------------- TRUE: if check condition reported for EW-EOM then sense data will not have valid flag set. FALSE: check condition reported for EW-EOM then sense data will have valid flag set. no parity --------------- TRUE: The drive is configured not to check for parity on the SCSI bus. FALSE: The drive is configured to check for parity on the SCSI bus. COmments: The drive always generates SCSI parity. Not checking SCSI parity, especially when operating a synchronous bus, is a bad idea. performance ----------------- TRUE: ``immediate'' and ``inifinite flush'' are selected (TRUE) (see definitions) FALSE: ``immediate'' and ``inifinite flush'' are not selected (FALSE) (see definitions) Comments: This can dramatically improove performance when applications "do silly things", like try and disable buffering or write lots of non-immediate filemarks. If they do silly things and this feature is not enabled then the drive will spend most of its life stream-failing. signed residue ----------------- TRUE: Residue is negative on back space. FALSE: Residue is absolute, positive, for all spacing. Comments: This is a DEC'ism. switch buffered ------------------ TRUE: Default buffered mode is used. Buffered mode may be switched using mode select. FALSE: Buffered mode = 1 is enforced. Mode select buffered mode field is silently ignored. This mode is enforced if ``immediate'' is TRUE. This is ``TRUE'' by default. trunc inquiry by 3 ----------------------- TRUE: Standard inquiry page is truncated by 3 bytes to 40h bytes. FALSE: Inquiry page remains 43h bytes long. Comments: This is a DEC'ism. I think DECstation 4000/5000's will hang during BOOT if they see "too much" inquiry command data. write zero fm --------------- TRUE: Allow write zero filemarks on write protected tape, and also if no tape is loaded. FALSE: Write zero filemarks is treated as any other write command with respect to write protected tapes and no tape present. Comments: AN HP'ism. Writing zero filemarks is the SCSI reccomended method of flushing the data buffer to tape. Some HP drivers do this before closing, even if the tape is write protected! From owner-freebsd-scsi Tue Mar 19 09:08:22 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA15787 for freebsd-scsi-outgoing; Tue, 19 Mar 1996 09:08:22 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA15782 Tue, 19 Mar 1996 09:08:20 -0800 (PST) Message-Id: <199603191708.JAA15782@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-scsi@freebsd.org, mrl@teleport.com (Mostyn/Annabella) Subject: Re: SCSI death in -current with DAT In-reply-to: Your message of "Tue, 19 Mar 1996 09:11:26 +0100." <199603190811.JAA02121@uriah.heep.sax.de> Date: Tue, 19 Mar 1996 09:08:20 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Its an aic7xxx driver problem related to parity checking which I recently enabled. It seems that you get harmless parity errors when you have both a wide and narrow bus attached to the controller at one time. I'm still investigating, but people seeing this problem should just disable parity checking in SCSI-Select. >-- >cheers, J"org > >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE >Never trust an operating system you don't have sources for. ;-) -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Tue Mar 19 10:17:09 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA19989 for freebsd-scsi-outgoing; Tue, 19 Mar 1996 10:17:09 -0800 (PST) Received: from chain.iafrica.com ([196.7.74.174]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA19972 for ; Tue, 19 Mar 1996 10:16:29 -0800 (PST) Received: (from root@localhost) by localhost.iafrica.com (8.6.12/8.6.12) id VAA00291; Mon, 18 Mar 1996 21:46:07 +0200 Date: Mon, 18 Mar 1996 21:46:07 +0200 (SAT) From: Root To: scsi@freebsd.org Subject: Zip drives Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. Is there support for Iomega Zip drives in FreeBSD 2.1 ? --- Root root@chain.iafrica.com From owner-freebsd-scsi Tue Mar 19 10:37:04 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA21280 for freebsd-scsi-outgoing; Tue, 19 Mar 1996 10:37:04 -0800 (PST) Received: from innocence.interface-business.de (innocence.interface-business.de [193.101.57.101]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA21275 for ; Tue, 19 Mar 1996 10:36:51 -0800 (PST) Received: from ida.interface-business.de (ida.interface-business.de [193.101.57.203]) by innocence.interface-business.de (8.6.11/8.6.9) with SMTP id TAA11949 for ; Tue, 19 Mar 1996 19:38:33 +0100 Received: (from j@localhost) by ida.interface-business.de (8.7.3/8.7.3) id TAA24268; Tue, 19 Mar 1996 19:38:28 +0100 (MET) Date: Tue, 19 Mar 1996 19:38:28 +0100 (MET) Message-Id: <199603191838.TAA24268@ida.interface-business.de> X-Newsreader: knews 0.9.3 Reply-To: joerg_wunsch@interface-business.de (Joerg Wunsch) Organization: interface business GmbH, Dresden From: j@ida.interface-business.de (J Wunsch) Subject: Re: multiple pci cards [shared IRQs] (fwd) To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is from the BSDi newsgroup, just out of curiosity, does anybody know whether this has already been fixed by now? ----- Forwarded Message ----- Newsgroups: comp.unix.bsd.bsdi.misc From: sms@wlv.iipo.gtegsc.com (Steven M. Schultz) Subject: Re: multiple pci cards [shared IRQs] Organization: GTE Government Systems, Thousand Oaks CA USA Message-ID: Date: Wed, 13 Mar 1996 23:00:50 GMT Terry Kennedy, Operations Mgr. wrote: [...] > Steve Schultz has an identical configuration which also works fine on >BSD/OS 2.x, although he's had horrible problems using other free Unix- >like systems. He may want to comment... [...] FreeBSD 2.1R (the CD from Nov/Dec) didn't support/recognize the 946C as a PCI device - thus interrupt sharing didn't work. I did try building using the updates available via FTP for the next 'stable' version. That didn't work either. The first SCSI chain was useable though. The problem has been fixed I am told but I kinda lost interest after BSD/OS 2.1 shipped. ... bha0 at isa0 iobase 0x330 irq 11: Buslogic EISA/PCI/VLB rev 42 (32-bit) WARNING: conflict at irq 11 ... bha1 at isa0 iobase 0x334 irq 11: Buslogic EISA/PCI/VLB rev 42 (32-bit) From owner-freebsd-scsi Tue Mar 19 13:08:54 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA01405 for freebsd-scsi-outgoing; Tue, 19 Mar 1996 13:08:54 -0800 (PST) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA01400 Tue, 19 Mar 1996 13:08:48 -0800 (PST) Received: (from mrcpu@localhost) by schizo.cdsnet.net (8.6.12/8.6.12) id NAA27476; Tue, 19 Mar 1996 13:12:19 -0800 Date: Tue, 19 Mar 1996 13:12:19 -0800 (PST) From: Jaye Mathisen To: "Justin T. Gibbs" cc: Joerg Wunsch , freebsd-scsi@Freebsd.Org, Mostyn/Annabella Subject: Re: SCSI death in -current with DAT In-Reply-To: <199603191708.JAA15782@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@Freebsd.Org X-Loop: FreeBSD.org Precedence: bulk Hmmm, I only have wide drives attached to mine and I still had to disable it. On Tue, 19 Mar 1996, Justin T. Gibbs wrote: > Its an aic7xxx driver problem related to parity checking which I > recently enabled. It seems that you get harmless parity errors > when you have both a wide and narrow bus attached to the controller > at one time. I'm still investigating, but people seeing this problem > should just disable parity checking in SCSI-Select. > > >-- > >cheers, J"org > > > >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > >Never trust an operating system you don't have sources for. ;-) > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== > From owner-freebsd-scsi Tue Mar 19 13:21:53 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA02200 for freebsd-scsi-outgoing; Tue, 19 Mar 1996 13:21:53 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA02174 for ; Tue, 19 Mar 1996 13:21:40 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA18681; Tue, 19 Mar 1996 22:20:16 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA02906; Tue, 19 Mar 1996 22:20:16 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id VAA04122; Tue, 19 Mar 1996 21:54:36 +0100 (MET) From: J Wunsch Message-Id: <199603192054.VAA04122@uriah.heep.sax.de> Subject: Re: Zip drives To: freebsd-scsi@freebsd.org Date: Tue, 19 Mar 1996 21:54:36 +0100 (MET) Cc: root@chain.iafrica.com (Root) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Root" at Mar 18, 96 09:46:07 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Root wrote: > Is there support for Iomega Zip drives in FreeBSD 2.1 ? As a "generic" disk drive. This is not ideal, but should get you going. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Tue Mar 19 13:24:56 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA02454 for freebsd-scsi-outgoing; Tue, 19 Mar 1996 13:24:56 -0800 (PST) Received: from chain.iafrica.com (chain.iafrica.com [196.7.74.174]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA02305 for ; Tue, 19 Mar 1996 13:22:55 -0800 (PST) Received: (from root@localhost) by chain.iafrica.com (8.6.12/8.6.12) id XAA00479; Tue, 19 Mar 1996 23:17:55 +0200 Date: Tue, 19 Mar 1996 23:17:47 +0200 (SAT) From: Root To: Joerg Wunsch cc: freebsd-scsi@freebsd.org Subject: Re: Zip drives In-Reply-To: <199603192054.VAA04122@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 19 Mar 1996, J Wunsch wrote: > As a "generic" disk drive. This is not ideal, but should get you > going. How do I start using it ? --- Root root@chain.iafrica.com From owner-freebsd-scsi Tue Mar 19 23:13:54 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA09221 for freebsd-scsi-outgoing; Tue, 19 Mar 1996 23:13:54 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA09215 Tue, 19 Mar 1996 23:13:46 -0800 (PST) Message-Id: <199603200713.XAA09215@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Jaye Mathisen cc: Joerg Wunsch , freebsd-scsi@Freebsd.Org, Mostyn/Annabella Subject: Re: SCSI death in -current with DAT In-reply-to: Your message of "Tue, 19 Mar 1996 13:12:19 PST." Date: Tue, 19 Mar 1996 23:13:46 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@Freebsd.Org X-Loop: FreeBSD.org Precedence: bulk > >Hmmm, I only have wide drives attached to mine and I still had to disable it. Thanks for the data point. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Tue Mar 19 23:20:27 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA09686 for freebsd-scsi-outgoing; Tue, 19 Mar 1996 23:20:27 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA09681 Tue, 19 Mar 1996 23:20:24 -0800 (PST) Message-Id: <199603200720.XAA09681@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: joerg_wunsch@interface-business.de (Joerg Wunsch) cc: freebsd-scsi@freebsd.org Subject: Re: multiple pci cards [shared IRQs] (fwd) In-reply-to: Your message of "Tue, 19 Mar 1996 19:38:28 +0100." <199603191838.TAA24268@ida.interface-business.de> Date: Tue, 19 Mar 1996 23:20:23 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >This is from the BSDi newsgroup, just out of curiosity, does anybody >know whether this has already been fixed by now? I believe the 946 works and perhaps the 948 too since it seems to give the same PCI ID. I still don't knowwhat the ID of the 956 is. The buslogic driver still needs to be brought up to speed to do tagged-queuing since it is availible. It also doesn't probe more higher than id 7 for wide controllers since I don't know how to generically tell that a controller has a wide bus. The Linux driver is supposedly fairly sophisticated and may be worth a quick look. I don't have any of the Buslogic PCI adapters to test with though and I'm not sure if the feature set for the 74X card that I have is the same. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Wed Mar 20 01:21:33 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA16229 for freebsd-scsi-outgoing; Wed, 20 Mar 1996 01:21:33 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA16208 for ; Wed, 20 Mar 1996 01:21:03 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA03056 for ; Wed, 20 Mar 1996 10:20:51 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA08089 for freebsd-scsi@FreeBSD.ORG; Wed, 20 Mar 1996 10:20:51 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id KAA07780 for freebsd-scsi@FreeBSD.ORG; Wed, 20 Mar 1996 10:19:29 +0100 (MET) From: J Wunsch Message-Id: <199603200919.KAA07780@uriah.heep.sax.de> Subject: Re: multiple pci cards [shared IRQs] (fwd) To: freebsd-scsi@FreeBSD.ORG Date: Wed, 20 Mar 1996 10:19:28 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603200720.XAA09681@freefall.freebsd.org> from "Justin T. Gibbs" at Mar 19, 96 11:20:23 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Justin T. Gibbs wrote: > > >This is from the BSDi newsgroup, just out of curiosity, does anybody > >know whether this has already been fixed by now? > > I believe the 946 works and perhaps the 948 too since it seems to > give the same PCI ID. Aha. Would two 946's with the same (shared) IRQ also work? (That's been the original question in the BSDi group.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Wed Mar 20 03:13:09 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA24628 for freebsd-scsi-outgoing; Wed, 20 Mar 1996 03:13:09 -0800 (PST) Received: from mail.rwth-aachen.de (mail.RWTH-Aachen.DE [137.226.144.9]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA24588 for ; Wed, 20 Mar 1996 03:12:30 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de) by mail.rwth-aachen.de (PMDF V5.0-4 #13110) id <01I2K7T1J7GG001N3J@mail.rwth-aachen.de>; Wed, 20 Mar 1996 12:15:01 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id MAA20693; Wed, 20 Mar 1996 12:17:54 +0100 Date: Wed, 20 Mar 1996 12:17:53 +0100 (MET) From: "Christoph P. Kukulies" Subject: Re: Zip drives In-reply-to: from To: root@chain.iafrica.com (Root) Cc: scsi@FreeBSD.ORG Reply-to: Christoph Kukulies Message-id: <199603201117.MAA20693@gilberto.physik.rwth-aachen.de> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL25 ME8b] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hi. > > Is there support for Iomega Zip drives in FreeBSD 2.1 ? Yes, there is. Just connect the drive and boot up. Ignore an eventually upcoming warning message. If you get the newer (-current) disklabel program you can easily disklabel -r -w sdx foo and then newfs /dev/rsdxx. > > > --- > Root > root@chain.iafrica.com > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-scsi Wed Mar 20 07:18:27 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA08030 for freebsd-scsi-outgoing; Wed, 20 Mar 1996 07:18:27 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA08024 Wed, 20 Mar 1996 07:18:23 -0800 (PST) Message-Id: <199603201518.HAA08024@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-scsi@FreeBSD.org Subject: Re: multiple pci cards [shared IRQs] (fwd) In-reply-to: Your message of "Wed, 20 Mar 1996 10:19:28 +0100." <199603200919.KAA07780@uriah.heep.sax.de> Date: Wed, 20 Mar 1996 07:18:23 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >As Justin T. Gibbs wrote: >> >> >This is from the BSDi newsgroup, just out of curiosity, does anybody >> >know whether this has already been fixed by now? >> >> I believe the 946 works and perhaps the 948 too since it seems to >> give the same PCI ID. > >Aha. Would two 946's with the same (shared) IRQ also work? (That's >been the original question in the BSDi group.) As long as your motherboard does level PCI interrupts, yes. >-- >cheers, J"org > >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE >Never trust an operating system you don't have sources for. ;-) -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Wed Mar 20 10:51:29 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA24489 for freebsd-scsi-outgoing; Wed, 20 Mar 1996 10:51:29 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA24410 for ; Wed, 20 Mar 1996 10:51:01 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA22779; Wed, 20 Mar 1996 19:50:48 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id TAA13858; Wed, 20 Mar 1996 19:50:47 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id TAA08898; Wed, 20 Mar 1996 19:08:48 +0100 (MET) From: J Wunsch Message-Id: <199603201808.TAA08898@uriah.heep.sax.de> Subject: Re: Zip drives To: scsi@freebsd.org Date: Wed, 20 Mar 1996 19:08:48 +0100 (MET) Cc: root@chain.iafrica.com In-Reply-To: <199603201117.MAA20693@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at Mar 20, 96 12:17:53 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Christoph P. Kukulies wrote: > If you get the newer (-current) disklabel program you can easily > disklabel -r -w sdx foo and then newfs /dev/rsdxx. You don't mean perchance ``auto'' instead of ``foo''? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Wed Mar 20 22:28:37 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA27410 for freebsd-scsi-outgoing; Wed, 20 Mar 1996 22:28:37 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA27403 Wed, 20 Mar 1996 22:28:34 -0800 (PST) Message-Id: <199603210628.WAA27403@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: FreeBSD-scsi cc: Ulrich.Windl@rz.uni-regensburg.de Subject: Simple Tagged Commands and Starvation In-reply-to: Your message of "Wed, 20 Mar 1996 08:35:23 PST." <199603201635.IAA21314@dandelion.com> Date: Wed, 20 Mar 1996 22:28:34 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I would like to hear other's opinions on this subject and possible ways to avoid the problem without arbitrarily penalizing commands entered into the queue. The problem may be agravated in Linux by using a large number of tags and a short timeout (Ulrich, FreeBSD uses a 10sec timeout and the two drivers that use tagged queueing default to 4 tags max per target which seems to offer the best performance under various benchmarks -- I have no idea what Linux uses). Since we are planning to push the dictation of queue message types up into the generic SCSI layer, it may turn out that we can solve this problem solely by enforcing ordered tags for syncronous writes. I'm also wading through the SCSI spec again in the hopes of an alternate way out, but it doesn't look good. On a totally different note... is there any chance you might release your Buslogic driver under a BSD copyright, Ulrich? I've placed the BSD Buslogic driver on my TODO list (it doesn't support tagged queueing yet), but it sounds like you've already forged a great relationship with Buslogic and I'd hate to re-invent the wheel. If your uncomfortable with re-licensing the code, perhaps you can share some contact info for Buslogic? It sounds like there much easier to deal with than Adaptec, and it would be a nice change of pace for me to work on a higher level driver compared to writing the firmware for the FreeBSD/Linux aic7xxx driver. 8-) > Date: Tue, 19 Mar 1996 23:33:28 -0800 > From: "Justin T. Gibbs" > > All devices that support tagged queuing provide some method internally to > ensure that simple queued transactions aren't starved. > >Much as it would be nice, I'm afraid this statement is not correct. Back in >late december I was beta testing the BusLogic BT-948 UltraSCSI Host Adapter >and thought I'd found a firmware bug because timeouts were occurring in this >fashion. When I reproduced the problem at BusLogic with their firmware >engineer, we determined using a SCSI Bus Analyzer that there was nothing wrong >with the firmware, but the disk drive itself was leaving commands disconnected >indefinitely. Nothing I can find in the SCSI-2 specification indicates that >disks are responsible for avoiding starvation, though it would certainly make >sense. The only solutions for this problem were to either use an occasional >ordered queue tag to force commands to be executed, or to pause SCSI activity >to the drive long enough for the queue to drain. > >Furthermore, I have seen this same form of starvation occur on several >different brands of disk drives, and the fix I installed corrected timeout >problems for a number of other people as well. More recently, adding similar >code to the ncrBsd2Linux driver corrected timeout problems with bonnie. > >I agree that ideally the high level parts of the system should indicate >whatever ordering constraints they have on the queued data transfers. > > Leonard -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Thu Mar 21 00:23:22 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA07270 for freebsd-scsi-outgoing; Thu, 21 Mar 1996 00:23:22 -0800 (PST) Received: from chain.iafrica.com (chain.iafrica.com [196.7.74.174]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA07196 for ; Thu, 21 Mar 1996 00:23:01 -0800 (PST) Received: (from root@localhost) by chain.iafrica.com (8.6.12/8.6.12) id KAA01454; Thu, 21 Mar 1996 10:15:27 +0200 Date: Thu, 21 Mar 1996 10:15:25 +0200 (SAT) From: Root To: "Christoph P. Kukulies" cc: scsi@FreeBSD.ORG Subject: Re: Zip drives In-Reply-To: <199603201117.MAA20693@gilberto.physik.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 20 Mar 1996, Christoph P. Kukulies wrote: > If you get the newer (-current) disklabel program you can easily > disklabel -r -w sdx foo and then newfs /dev/rsdxx. Sorry, it's a parallel version. Don't think its supported yet..... --- Root root@chain.iafrica.com From owner-freebsd-scsi Thu Mar 21 05:28:14 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA25926 for freebsd-scsi-outgoing; Thu, 21 Mar 1996 05:28:14 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA25515 for ; Thu, 21 Mar 1996 05:22:02 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA22771; Thu, 21 Mar 1996 14:21:02 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id OAA22722; Thu, 21 Mar 1996 14:21:01 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id OAA13251; Thu, 21 Mar 1996 14:04:42 +0100 (MET) From: J Wunsch Message-Id: <199603211304.OAA13251@uriah.heep.sax.de> Subject: Re: Zip drives To: freebsd-scsi@freebsd.org Date: Thu, 21 Mar 1996 14:04:42 +0100 (MET) Cc: root@chain.iafrica.com (Root) In-Reply-To: from "Root" at Mar 21, 96 10:15:25 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Root wrote: > > If you get the newer (-current) disklabel program you can easily > > disklabel -r -w sdx foo and then newfs /dev/rsdxx. > > Sorry, it's a parallel version. Don't think its supported yet..... Uaaaah. So you should have directed the question to ``freebsd-parallel@freebsd.org'', right? :-) It's doubtfull that anybody will ever volunteerily write drivers for {floppy tapes | ethernet adapters | zip drives | ...} hanging off a parallel port. It's too dreadful to do this. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Thu Mar 21 07:17:11 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA01484 for freebsd-scsi-outgoing; Thu, 21 Mar 1996 07:17:11 -0800 (PST) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA01476 Thu, 21 Mar 1996 07:17:06 -0800 (PST) Received: by Sisyphos id AA19099 (5.67b/IDA-1.5); Thu, 21 Mar 1996 16:16:22 +0100 Message-Id: <199603211516.AA19099@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 21 Mar 1996 16:16:21 +0100 In-Reply-To: "Justin T. Gibbs" "Simple Tagged Commands and Starvation" (Mar 20, 22:28) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: "Justin T. Gibbs" Subject: Re: Simple Tagged Commands and Starvation Cc: FreeBSD-scsi@freefall.freebsd.org, Ulrich.Windl@rz.uni-regensburg.de Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mar 20, 22:28, "Justin T. Gibbs" wrote: } Subject: Simple Tagged Commands and Starvation } I would like to hear other's opinions on this subject and possible ways to } avoid the problem without arbitrarily penalizing commands entered into the } queue. The problem may be agravated in Linux by using a large number of } tags and a short timeout (Ulrich, FreeBSD uses a 10sec timeout and the two } drivers that use tagged queueing default to 4 tags max per target which } seems to offer the best performance under various benchmarks -- I have no } idea what Linux uses). Since we are planning to push the dictation of } queue message types up into the generic SCSI layer, it may turn out that we } can solve this problem solely by enforcing ordered tags for syncronous } writes. I'm also wading through the SCSI spec again in the hopes of an } alternate way out, but it doesn't look good. I've received mail from Gerard Roudier (who ported the FreeBSD NCR driver to Linux) on this topic, a few weeks ago, and he suggested a fix. Linux has a 5 second timeout on read and write commands, and he found that on every Bonnie run, he got a few (soft) timeouts from the driver, i.e. the drive did delay execution of a tagged command for more than 5 seconds. Since the NCR driver polls the list of currently executing commands once a second anyway, he suggested using an ORDERED TAG for the next command sent to that target, if any command is not completed, two seconds before its timer expires. This would place a barrier in the SCSI command stream. I.e. the next command issued would not execute before all previously issued commands are complete. And two seconds should be sufficient to complete far more than 4 outstanding commands (it should suffice for 100, in fact :) I had been thinking about a simpler algorithm: Have a bit mask, and reset it to all zeroes, once a second. When a tag message is required, and there is a 0 at the position corresponding to that target, then use an ORDERED TAG and set the bit to one. (In fact, this bit should be set to one, when ever a ordered tag message is sent :) (The ORDERED TAG applies to a I_T_L_Q nexus, i.e. apllies to LUNs, not targets, but I've yet to see a single multi-LUN device that supports tagged commands). This would make the driver use at most one ordered tag per second, for a negligable loss of performance, and this (or some variation of the theme) apppears to be a solution that could be implemented in the GENERIC SCSI code ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-scsi Thu Mar 21 07:53:20 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA09618 for freebsd-scsi-outgoing; Thu, 21 Mar 1996 07:53:20 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA09602 Thu, 21 Mar 1996 07:53:15 -0800 (PST) Message-Id: <199603211553.HAA09602@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: se@zpr.uni-koeln.de (Stefan Esser) cc: FreeBSD-scsi@freefall.freebsd.org, Ulrich.Windl@rz.uni-regensburg.de Subject: Re: Simple Tagged Commands and Starvation In-reply-to: Your message of "Thu, 21 Mar 1996 16:16:21 +0100." <199603211516.AA19099@Sisyphos> Date: Thu, 21 Mar 1996 07:53:14 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >On Mar 20, 22:28, "Justin T. Gibbs" wrote: >} Subject: Simple Tagged Commands and Starvation >} I would like to hear other's opinions on this subject and possible ways to >} avoid the problem without arbitrarily penalizing commands entered into the >} queue. The problem may be agravated in Linux by using a large number of >} tags and a short timeout (Ulrich, FreeBSD uses a 10sec timeout and the two >} drivers that use tagged queueing default to 4 tags max per target which >} seems to offer the best performance under various benchmarks -- I have no >} idea what Linux uses). Since we are planning to push the dictation of >} queue message types up into the generic SCSI layer, it may turn out that we >} can solve this problem solely by enforcing ordered tags for syncronous >} writes. I'm also wading through the SCSI spec again in the hopes of an >} alternate way out, but it doesn't look good. > >I've received mail from Gerard Roudier >(who ported the FreeBSD NCR driver to >Linux) on this topic, a few weeks ago, >and he suggested a fix. This is the same "fix" the Linux Buslogic driver uses and I really don't like it since it's extra overhead and may be totally unecessary for everything but bonnie test runs with a large number of tags (probably larger than the four we're using). Perhaps a "soft" timeout at 5 seconds that causes the next queued command to that target to use an ordered tag would be better. >Regards, STefan >-- > Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 > Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 > ============================================================================= >= > http://www.zpr.uni-koeln.de/~se -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Thu Mar 21 09:10:12 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA29835 for freebsd-scsi-outgoing; Thu, 21 Mar 1996 09:10:12 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA29791 Thu, 21 Mar 1996 09:10:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id JAA05798; Thu, 21 Mar 1996 09:09:57 -0800 Message-Id: <199603211709.JAA05798@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: "Justin T. Gibbs" cc: se@ZPR.Uni-Koeln.DE (Stefan Esser), FreeBSD-scsi@freefall.freebsd.org, Ulrich.Windl@rz.uni-regensburg.de Subject: Re: Simple Tagged Commands and Starvation In-reply-to: Your message of "Thu, 21 Mar 1996 07:53:14 PST." <199603211553.HAA09602@freefall.freebsd.org> From: David Greenman Reply-To: davidg@Root.COM Date: Thu, 21 Mar 1996 09:09:57 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >(probably larger than the four we're using). Perhaps a "soft" timeout >at 5 seconds that causes the next queued command to that target to >use an ordered tag would be better. Yes, I like this solution better. This won't penalize disk drives that work correctly. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-scsi Fri Mar 22 05:12:40 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA05034 for freebsd-scsi-outgoing; Fri, 22 Mar 1996 05:12:40 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA05028 for ; Fri, 22 Mar 1996 05:12:36 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id AAA06530; Sat, 23 Mar 1996 00:06:35 +1100 Date: Sat, 23 Mar 1996 00:06:35 +1100 From: Bruce Evans Message-Id: <199603221306.AAA06530@godzilla.zeta.org.au> To: freebsd-scsi@freebsd.org, j@uriah.heep.sax.de Subject: Re: Zip drives Cc: root@chain.iafrica.com Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >It's doubtfull that anybody will ever volunteerily write drivers >for {floppy tapes | ethernet adapters | zip drives | ...} >hanging off a parallel port. It's too dreadful to do this. Well, they've already written drivers for parallel port TCP/IP and qcams. I wonder if these run better on Enhanced Parallel Ports. Bruce From owner-freebsd-scsi Fri Mar 22 19:12:35 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA24111 for freebsd-scsi-outgoing; Fri, 22 Mar 1996 19:12:35 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA24092 Fri, 22 Mar 1996 19:12:25 -0800 (PST) Received: by sequent.kiae.su id AA18236 (5.65.kiae-2 ); Sat, 23 Mar 1996 06:08:26 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Sat, 23 Mar 96 06:08:26 +0300 Received: (from ache@localhost) by astral.msk.su (8.7.5/8.7.3) id GAA00996; Sat, 23 Mar 1996 06:07:36 +0300 (MSK) Message-Id: <199603230307.GAA00996@astral.msk.su> Subject: aic7870 recognized only after second reboot To: scsi@freebsd.org, current@freebsd.org (FreeBSD-current) Date: Sat, 23 Mar 1996 06:07:36 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL13 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk First boot didn't find it aic7870. Second one (Ctrl-Alt-Del) find it, but very strange: (all this messages not appearse at the first boot) Mar 22 15:04:50 test /kernel: Probing for devices on the PCI bus: Mar 22 15:04:50 test /kernel: pci0:0: vendor=0x10b9, device=0x1451, class=bridge (host) [no driver assigned] Mar 22 15:04:50 test /kernel: chip0 rev 4 on pci0:6 Mar 22 15:04:50 test /kernel: ahc0 rev 0 int a irq 10 on pci0:10 Mar 22 15:04:50 test /kernel: checksum error Mar 22 15:04:50 test /kernel: ahc0: SEEPROM read failed, using leftover BIOS values Mar 22 15:04:50 test /kernel: ahc0: aic7870 Single Channel, SCSI Id=7, aic7870, 16 SCBs Mar 22 15:04:50 test /kernel: ahc0 waiting for scsi devices to settle Mar 22 15:04:51 test /kernel: (ahc0:0:0): "IBM DPES-31080 S31Q" type 0 fixed SCSI 2 Mar 22 15:04:51 test /kernel: sd0(ahc0:0:0): Direct-Access 1034MB (2118144 512 byte sectors) Controller BIOS comes first correctly in both cases and assign C: to disk. Next hard reboot did not find it again. It happens on both 2.1 and -current with equal messages. Any ideas? -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-scsi Sat Mar 23 13:57:49 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA14632 for freebsd-scsi-outgoing; Sat, 23 Mar 1996 13:57:49 -0800 (PST) Received: from chain.iafrica.com (chain.iafrica.com [196.7.74.174]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA14619 for ; Sat, 23 Mar 1996 13:57:33 -0800 (PST) Received: (from khetan@localhost) by chain.iafrica.com (8.6.12/8.6.12) id XAA00525; Sat, 23 Mar 1996 23:53:01 +0200 Date: Sat, 23 Mar 1996 23:53:00 +0200 (SAT) From: Khetan Gajjar To: freebsd-scsi@freebsd.org Subject: SCSI refresh Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello. How do I refresh the SCSI bus ? I need to know because I boot my machine often without the CD-ROM/DAT drive on, and want to use it afterwards, and don't feel like re-booting the machine with the device on. I read the man pages for SCSI, but don't know the /dev name :( --- Thanx, Khetan Gajjar Visit at http://www.iafrica.com/~khetan/index.html Pipex-Internet Africa Operations help@iafrica.com or 0800-030-002 From owner-freebsd-scsi Sat Mar 23 15:21:30 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA18668 for freebsd-scsi-outgoing; Sat, 23 Mar 1996 15:21:30 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA18652 for ; Sat, 23 Mar 1996 15:21:25 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA02125; Sun, 24 Mar 1996 00:20:41 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id AAA20383; Sun, 24 Mar 1996 00:20:41 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id AAA26231; Sun, 24 Mar 1996 00:19:41 +0100 (MET) From: J Wunsch Message-Id: <199603232319.AAA26231@uriah.heep.sax.de> Subject: Re: SCSI refresh To: freebsd-scsi@freebsd.org Date: Sun, 24 Mar 1996 00:19:41 +0100 (MET) Cc: khetan@chain.iafrica.com (Khetan Gajjar) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Khetan Gajjar" at Mar 23, 96 11:53:00 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Khetan Gajjar wrote: > How do I refresh the SCSI bus ? > > I need to know because I boot my machine often without the CD-ROM/DAT > drive on, and want to use it afterwards, and don't feel like re-booting > the machine with the device on. > > I read the man pages for SCSI, but don't know the /dev name :( scsi -f /dev/rsd0.ctl -r ^^^^^^^^^^^^^_____ This must be a device that has been successfully probed at boot time. Otherwise, you've got a chicken-and-egg problem. Alas, it doesn't work on all controllers. Some of them consistently hang the entire system. :-( -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)