From owner-freebsd-scsi Sun Nov 28 14: 2:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (castles501.castles.com [208.214.165.65]) by hub.freebsd.org (Postfix) with ESMTP id 04993153BB for ; Sun, 28 Nov 1999 14:02:24 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA00739; Sun, 28 Nov 1999 14:02:57 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911282202.OAA00739@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Gallatin Cc: freebsd-scsi@freebsd.org Subject: Re: IDE<-->SCSI Hardware RAID In-reply-to: Your message of "Wed, 17 Nov 1999 21:23:21 EST." <14387.24943.678538.385637@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Nov 1999 14:02:57 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Does anybody have any experiences, good or bad, with a ZeroD ZD-AV400 > RAID box? This is a cabinet that does hardware RAID 0, 0+1, 1, 3 or > 5 across 6 EIDE drives & presents an UltraWide SCSI interface to the > host. See http://www.zero-d.com/zd400.html Never seen one before. If you do get one, can you tell us who actually makes the controller in the box? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 28 23:44:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id A53B414DE8 for ; Sun, 28 Nov 1999 23:44:24 -0800 (PST) (envelope-from timclark@ams-ltd.demon.co.uk) Received: from ams-ltd.demon.co.uk ([212.229.113.50]) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 11sLTz-000Gf3-0A for freebsd-scsi@FreeBSD.ORG; Mon, 29 Nov 1999 07:44:23 +0000 Message-ID: <38422E86.3AF5AAFE@ams-ltd.demon.co.uk> Date: Mon, 29 Nov 1999 07:43:02 +0000 From: Tim Clark X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Trouble installing on SCSI-only system Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am failing to install 2.1.6 on a PC with just a SCSI disk. At the point where the install is committed, it tries for a long time to write the partition table (at least that's what the message says) then gives up with an IO error. The hardware is as follows. Compaq Deskpro EN (500MHz Pentium III) 128 MByte memory IDE CDROM (on secondary IDE interface - FreeBSD 2.1.6 distribution is on this) Adaptec 2940AU interface card (PCI) IBM UltraStar 9ES (4.5GB) hard disk (on SCSI ID=0) no IDE hard disks Intel Ethernet card I know that the hardware is OK, because I have installed two other OSes on it (Windows95 and QNX). Any help much appreciated. [PS There are historical reasons why I am installing 2.1.6 and not a more recent version.] [PPS I posted this to freebsd-questions as well.] Regards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 29 5:31:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 3AC6F15653 for ; Mon, 29 Nov 1999 05:31:16 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id NAA22402; Mon, 29 Nov 1999 13:31:15 GMT (envelope-from geoffb) Date: Mon, 29 Nov 1999 13:31:15 +0000 From: Geoff Buckingham To: Tim Clark Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Trouble installing on SCSI-only system Message-ID: <19991129133115.C15067@chuggalug.clues.com> References: <38422E86.3AF5AAFE@ams-ltd.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38422E86.3AF5AAFE@ams-ltd.demon.co.uk>; from Tim Clark on Mon, Nov 29, 1999 at 07:43:02AM +0000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 29, 1999 at 07:43:02AM +0000, Tim Clark wrote: > I am failing to install 2.1.6 on a PC with just a SCSI disk. At the > point where the install is committed, it tries for a long time to write > the partition table (at least that's what the message says) then gives > up with an IO error. The hardware is as follows. > Compaq Deskpro EN (500MHz Pentium III) > 128 MByte memory > IDE CDROM (on secondary IDE interface - FreeBSD 2.1.6 distribution is > on this) > Adaptec 2940AU interface card (PCI) It is just a thought but it may be worth checking the cvs repository to see if the ahc driver needed any alteration for the crippled 2940AU and if so when it happened. > IBM UltraStar 9ES (4.5GB) hard disk (on SCSI ID=0) > no IDE hard disks > Intel Ethernet card > > I know that the hardware is OK, because I have installed two other OSes > on it (Windows95 and QNX). > > Any help much appreciated. > [PS There are historical reasons why I am installing 2.1.6 and not a > more recent version.] Have you considered using the 2.2.8 install and fixit diks to manually install from the 216 CD ?? > [PPS I posted this to freebsd-questions as well.] > -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 30 8:59: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from m08.alpha-net.ne.jp (m08.alpha-net.ne.jp [210.229.64.38]) by hub.freebsd.org (Postfix) with ESMTP id 47D9F14E60; Tue, 30 Nov 1999 08:58:55 -0800 (PST) (envelope-from k5@cheerful.com) Received: from kyoto-p24.alpha-net.ne.jp (kyoto-p24.alpha-net.ne.jp [210.237.118.24]) by m08.alpha-net.ne.jp (8.9.3/3.7W) with ESMTP id BAA01813; Wed, 1 Dec 1999 01:52:43 +0900 (JST) Received: from souffle.bogus-local.net (souffle.bogus-local.net [192.168.1.1]) by kyoto-p24.alpha-net.ne.jp (Postfix) with ESMTP id 59A533D06; Wed, 1 Dec 1999 01:58:33 +0900 (JST) Date: Wed, 01 Dec 1999 01:58:32 +0900 Message-ID: <14404.568.920093.72159A@cheerful.com> From: FUJISHIMA Satsuki To: msmith@freebsd.org Cc: gallatin@cs.duke.edu, freebsd-scsi@freebsd.org Subject: Re: IDE<-->SCSI Hardware RAID In-Reply-To: In your message of "Sun, 28 Nov 1999 14:02:57 -0800" <199911282202.OAA00739@mass.cdrom.com> References: <14387.24943.678538.385637@grasshopper.cs.duke.edu> <199911282202.OAA00739@mass.cdrom.com> User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) Emacs/20.4 (i386--freebsd) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At Sun, 28 Nov 1999 14:02:57 -0800, Mike Smith wrote: > > > > > Does anybody have any experiences, good or bad, with a ZeroD ZD-AV400 > > RAID box? This is a cabinet that does hardware RAID 0, 0+1, 1, 3 or > > 5 across 6 EIDE drives & presents an UltraWide SCSI interface to the > > host. See http://www.zero-d.com/zd400.html > > Never seen one before. If you do get one, can you tell us who actually > makes the controller in the box? It is actually SCSI-SCSI RAID box. It has IDE-SCSI converter and FreeBSD may find it as a one large SCSI disk. I think it is the same product of Arena (http://www.arena.net.tw/product/spec.htm), at this page they say "O/S Independent and Transparent." Not my experience, by the way. -- FUJISHIMA Satsuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 30 9:21: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 81FDB14E66; Tue, 30 Nov 1999 09:20:58 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id MAA26202; Tue, 30 Nov 1999 12:20:55 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA59599; Tue, 30 Nov 1999 12:20:25 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 30 Nov 1999 12:20:24 -0500 (EST) To: FUJISHIMA Satsuki Cc: msmith@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: IDE<-->SCSI Hardware RAID In-Reply-To: <14404.568.920093.72159A@cheerful.com> References: <14387.24943.678538.385637@grasshopper.cs.duke.edu> <199911282202.OAA00739@mass.cdrom.com> <14404.568.920093.72159A@cheerful.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14404.1819.307170.61579@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FUJISHIMA Satsuki writes: > > I think it is the same product of Arena > (http://www.arena.net.tw/product/spec.htm), at this page they say "O/S > Independent and Transparent." > > Not my experience, by the way. Yes. It does look the same. And Arena's documentation seems to be better. Thanks! Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 30 23:56:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from koala.pulsat.com.au (koala.pulsat.com.au [202.81.128.10]) by hub.freebsd.org (Postfix) with ESMTP id CB5A614F65; Tue, 30 Nov 1999 23:56:48 -0800 (PST) (envelope-from paul@pulsat.com.au) Received: from localhost (paul@localhost) by koala.pulsat.com.au (8.9.3/8.9.3) with ESMTP id PAA03111; Wed, 1 Dec 1999 15:56:45 +0800 (WST) (envelope-from paul@pulsat.com.au) Date: Wed, 1 Dec 1999 15:56:45 +0800 (WST) From: Paul Reece To: freebsd-questions@freebsd.org Cc: freebsd-scsi@freebsd.org Subject: cam scsi and adaptec 7890/91 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. Have just installed 3.3-STABLE onto a machine here with onboard Adaptec 7890/7891 Ultra2 Controller. When booting however I get: ahc0: rev 0x00 int a irq 11 on pci0.12.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs then.. da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 11.626MB/s transfers (5.813MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) ie, 11.626MB/s @ 5.813Mhz, instead of what I'd expect (from a machine with a 7895/7896 in it): da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enable d da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) Anyone have any pointers as to why I'm getting only 11.6meg transfers reported upon boot when the drives and the SCSI BUS is capable of 80?? The devices ARE LVD/Ultra2 drives.. (same in both machines, except one set are SCA) Any replies direct would be appreciated - else I'll likely miss them :) Regards, Paul. -- paul reece - network administrator - pulsat communications limited preece@pulsat.com.au - ph +61 8 9481 6911 - fax +61 8 9481 6751 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 1 9:26:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id DE0D315B2F for ; Wed, 1 Dec 1999 09:26:09 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id JAA09343; Wed, 1 Dec 1999 09:45:43 -0700 (MST) Date: Wed, 1 Dec 1999 09:45:43 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199912011645.JAA09343@narnia.plutotech.com> To: Paul Reece Cc: scsi@FreeBSD.org Subject: Re: cam scsi and adaptec 7890/91 X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > Hi. > > Have just installed 3.3-STABLE onto a machine here with onboard Adaptec > 7890/7891 Ultra2 Controller. > > When booting however I get: > > ahc0: rev 0x00 int a irq 11 on > pci0.12.0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > > then.. > > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 11.626MB/s transfers (5.813MHz, offset 31, 16bit), Tagged Queueing > Enabled > da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) How old of a 3.3-stable are you running. There was a problem related to reading SEEPROM data that could cause this problem, but it was fixed in rev 1.5.2.6 of sys/pci/ahc_pci.c. If you are completely up to date with your sources, contact me with private email and we'll explore what is happening by enabling some diagnostics. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 1 14:33: 4 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from banana.ne.mediaone.net (banana.ne.mediaone.net [24.218.57.108]) by hub.freebsd.org (Postfix) with ESMTP id 2A39C14A03 for ; Wed, 1 Dec 1999 14:32:59 -0800 (PST) (envelope-from jmcelroy@banana.ne.mediaone.net) Received: (from jmcelroy@localhost) by banana.ne.mediaone.net (8.9.3/8.9.3) id RAA00429; Fri, 1 Dec 1995 17:42:53 -0500 (EST) (envelope-from jmcelroy) Date: Fri, 1 Dec 1995 17:42:53 -0500 (EST) Message-Id: <199512012242.RAA00429@banana.ne.mediaone.net> To: freebsd-scsi@freebsd.org From: Jon McElroy Subject: Problem with Advansys 940U Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am having trouble getting FreeBSD 3.3 to recognize my Advansys 940U scsi card. The following line was in my kernel configuration file: controller adv0 at isa? port ? cam irq ? I have built kernels with this line as it is, with everthing after the "adv0" commented out, and with the "isa" replaced with "pci", but none find the card during the boot sequence. The card is functional, it worked under a previous OS. Any help would be most appreciated, Jon McElroy jmcelroy@mega.nu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 1 17:23:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 022D6150D7 for ; Wed, 1 Dec 1999 17:23:51 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id RAA38821; Wed, 1 Dec 1999 17:22:36 -0800 (PST) Date: Wed, 1 Dec 1999 17:22:35 -0800 (PST) From: Julian Elischer To: Jon McElroy Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Problem with Advansys 940U In-Reply-To: <199512012242.RAA00429@banana.ne.mediaone.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org look at the date your mail is setting.... On Fri, 1 Dec 1995, Jon McElroy wrote: > I am having trouble getting FreeBSD 3.3 to recognize my > Advansys 940U scsi card. The following line was in my kernel > configuration file: > controller adv0 at isa? port ? cam irq ? > I have built kernels with this line as it is, with everthing > after the "adv0" commented out, and with the "isa" replaced > with "pci", but none find the card during the boot sequence. > The card is functional, it worked under a previous OS. > > Any help would be most appreciated, > Jon McElroy > jmcelroy@mega.nu > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 7:33:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id C20D414D06 for ; Thu, 2 Dec 1999 07:33:34 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id BAA24130; Fri, 3 Dec 1999 01:31:30 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd024128; Fri Dec 3 01:31:20 1999 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id BAA07654 for ; Fri, 3 Dec 1999 01:30:51 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id BAA00863 for ; Fri, 3 Dec 1999 01:30:50 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id BAA12298; Fri, 3 Dec 1999 01:30:50 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199912021530.BAA12298@nymph.detir.qld.gov.au> To: freebsd-scsi@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Tape driver problems Date: Fri, 03 Dec 1999 01:30:49 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Keen to try the improved auto density selection code, I ran some tests. Hardware is Pentium 133, 2 x aha1542B, 7 disks (of various sorts), and an Exabyte 8500. Software is -current from 2 days ago. The exabyte is detected as: sa0 at aha0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 4.032MB/s transfers (4.032MHz, offset 7) which looks fine. "mt status" with no tape loaded gives an error: mt: /dev/nrsa0: Device not configured which seems a bit harsh. Also the kernel logs error messages like: Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): LOAD UNLOAD. CDB: 1b 0 0 0 1 0 Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): NOT READY asc:3a,0 Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): Medium not present Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): REWIND. CDB: 1 0 0 0 0 0 Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): NOT READY asc:3a,0 Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): Medium not present It seems like these should be silenced, and not cause mt itself to fail. This is an "old" problem, ie more than 2 weeks, at least. :-) "mt status" with a tape loaded gives the correct values (including density), but the kernel spits out: Dec 3 00:44:36 bucket /kernel: bus_dmamap_load: Too many segs! buf_len = 0x3000 The last bit changes. I've seen 0xb000 or 0xd000 or 0xe000 or 0xf000 also. This is a new problem related to the density autodetection read. I expect that an aha1542B just can't read MAXPHYS bytes from anything. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 10:12: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1D6A714D2D for ; Thu, 2 Dec 1999 10:11:59 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA02497; Thu, 2 Dec 1999 10:10:49 -0800 Date: Thu, 2 Dec 1999 10:10:49 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Stephen McKay Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-Reply-To: <199912021530.BAA12298@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > "mt status" with no tape loaded gives an error: > > mt: /dev/nrsa0: Device not configured > > which seems a bit harsh. Also the kernel logs error messages like: Yes, let me think about the error a bit. It may be more a question of changing 'mt' to report something other than just perror. > > Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): LOAD UNLOAD. CDB: 1b 0 0 0 1 0 > Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): NOT READY asc:3a,0 > Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): Medium not present > Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): REWIND. CDB: 1 0 0 0 0 0 > Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): NOT READY asc:3a,0 > Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): Medium not present > > It seems like these should be silenced, I'll have to check what happened here. Do you have CAMDEBUG defined? >and not cause mt itself to fail. If you want mt to not 'fail', use the control device (rsa0.ctl), however this won't exercise any attempts at media detection. > This is an "old" problem, ie more than 2 weeks, at least. :-) > > "mt status" with a tape loaded gives the correct values (including density), > but the kernel spits out: > > Dec 3 00:44:36 bucket /kernel: bus_dmamap_load: Too many segs! buf_len = 0x3000 > > The last bit changes. I've seen 0xb000 or 0xd000 or 0xe000 or 0xf000 also. > This is a new problem related to the density autodetection read. I expect > that an aha1542B just can't read MAXPHYS bytes from anything. Hmm, indeed. The density determining code does indeed issue a read of MAXPHYS bytes. It seems to me that all HBA's should at least support that! The maintainer for the 1542X will have to speak to this tho... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 10:17:22 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 4C94114D09 for ; Thu, 2 Dec 1999 10:17:20 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA50614; Thu, 2 Dec 1999 11:16:26 -0700 (MST) (envelope-from ken) Message-Id: <199912021816.LAA50614@panzer.kdm.org> Subject: Re: Tape driver problems In-Reply-To: from Matthew Jacob at "Dec 2, 1999 10:10:49 am" To: mjacob@feral.com Date: Thu, 2 Dec 1999 11:16:26 -0700 (MST) Cc: syssgm@detir.qld.gov.au (Stephen McKay), freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote... > > This is an "old" problem, ie more than 2 weeks, at least. :-) > > > > "mt status" with a tape loaded gives the correct values (including density), > > but the kernel spits out: > > > > Dec 3 00:44:36 bucket /kernel: bus_dmamap_load: Too many segs! buf_len = 0x3000 > > > > The last bit changes. I've seen 0xb000 or 0xd000 or 0xe000 or 0xf000 also. > > This is a new problem related to the density autodetection read. I expect > > that an aha1542B just can't read MAXPHYS bytes from anything. > > Hmm, indeed. The density determining code does indeed issue a read of > MAXPHYS bytes. It seems to me that all HBA's should at least support that! > The maintainer for the 1542X will have to speak to this tho... I'm not the aha maintainer (Warner is), but I do know that it cannot do more than 64K at a time. So you shouldn't be using any more than that. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 10:19:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D22CD14D09 for ; Thu, 2 Dec 1999 10:19:18 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA02563; Thu, 2 Dec 1999 10:20:19 -0800 Date: Thu, 2 Dec 1999 10:20:19 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Stephen McKay , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-Reply-To: <199912021816.LAA50614@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > This is an "old" problem, ie more than 2 weeks, at least. :-) > > > > > > "mt status" with a tape loaded gives the correct values (including density), > > > but the kernel spits out: > > > > > > Dec 3 00:44:36 bucket /kernel: bus_dmamap_load: Too many segs! buf_len = 0x3000 > > > > > > The last bit changes. I've seen 0xb000 or 0xd000 or 0xe000 or 0xf000 also. > > > This is a new problem related to the density autodetection read. I expect > > > that an aha1542B just can't read MAXPHYS bytes from anything. > > > > Hmm, indeed. The density determining code does indeed issue a read of > > MAXPHYS bytes. It seems to me that all HBA's should at least support that! > > The maintainer for the 1542X will have to speak to this tho... > > I'm not the aha maintainer (Warner is), but I do know that it cannot do I didn't say you were. > more than 64K at a time. So you shouldn't be using any more than that. Nonsense. That's what bounce buffers can or *should* be used for too. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 10:35:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id A909314DA5 for ; Thu, 2 Dec 1999 10:35:14 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA50772; Thu, 2 Dec 1999 11:34:45 -0700 (MST) (envelope-from ken) Message-Id: <199912021834.LAA50772@panzer.kdm.org> Subject: Re: Tape driver problems In-Reply-To: from Matthew Jacob at "Dec 2, 1999 10:20:19 am" To: mjacob@feral.com Date: Thu, 2 Dec 1999 11:34:45 -0700 (MST) Cc: syssgm@detir.qld.gov.au (Stephen McKay), freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote... > > > > > This is an "old" problem, ie more than 2 weeks, at least. :-) > > > > > > > > "mt status" with a tape loaded gives the correct values (including density), > > > > but the kernel spits out: > > > > > > > > Dec 3 00:44:36 bucket /kernel: bus_dmamap_load: Too many segs! buf_len = 0x3000 > > > > > > > > The last bit changes. I've seen 0xb000 or 0xd000 or 0xe000 or 0xf000 also. > > > > This is a new problem related to the density autodetection read. I expect > > > > that an aha1542B just can't read MAXPHYS bytes from anything. > > > > > > Hmm, indeed. The density determining code does indeed issue a read of > > > MAXPHYS bytes. It seems to me that all HBA's should at least support that! > > > The maintainer for the 1542X will have to speak to this tho... > > > > I'm not the aha maintainer (Warner is), but I do know that it cannot do > > I didn't say you were. I know you didn't. But if I didn't make that qualification, from previous experience I can guess that I would get mail from a few people complaining about some problem they have with their aha board. I was just trying to take some preventative action. > > more than 64K at a time. So you shouldn't be using any more than that. > > Nonsense. That's what bounce buffers can or *should* be used for too. Well, talk to Warner about it. You could probably use bounce buffers to handle the problem. For now, though, I think 64K is the lowest common denominator. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 10:37:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 14D1A14DA5 for ; Thu, 2 Dec 1999 10:37:36 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA02669; Thu, 2 Dec 1999 10:38:28 -0800 Date: Thu, 2 Dec 1999 10:38:28 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Stephen McKay , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-Reply-To: <199912021834.LAA50772@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I know you didn't. But if I didn't make that qualification, from previous > experience I can guess that I would get mail from a few people complaining > about some problem they have with their aha board. I was just trying to > take some preventative action. Yes, and not sending email would have worked too! :-) > > > > more than 64K at a time. So you shouldn't be using any more than that. > > > > Nonsense. That's what bounce buffers can or *should* be used for too. > > Well, talk to Warner about it. You could probably use bounce buffers to > handle the problem. For now, though, I think 64K is the lowest common > denominator. Oh, goody! We can make FreeBSD as retarded as Solaris/SunOS then! Even better, let's make the limit 63Kbytes for compatibility with Solaris/SunOS and I can go back to automatically typing 'tar cvb 126...'..... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 14: 5:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id DD63514EE4 for ; Thu, 2 Dec 1999 14:05:17 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA00570; Thu, 2 Dec 1999 14:05:01 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912022205.OAA00570@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: "Kenneth D. Merry" , Stephen McKay , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-reply-to: Your message of "Thu, 02 Dec 1999 10:20:19 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Dec 1999 14:05:01 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > Dec 3 00:44:36 bucket /kernel: bus_dmamap_load: Too many segs! buf_len = 0x3000 > > > > > > > > The last bit changes. I've seen 0xb000 or 0xd000 or 0xe000 or 0xf000 also. > > > > This is a new problem related to the density autodetection read. I expect > > > > that an aha1542B just can't read MAXPHYS bytes from anything. > > > > > > Hmm, indeed. The density determining code does indeed issue a read of > > > MAXPHYS bytes. It seems to me that all HBA's should at least support that! > > > The maintainer for the 1542X will have to speak to this tho... > > > > I'm not the aha maintainer (Warner is), but I do know that it cannot do > > more than 64K at a time. So you shouldn't be using any more than that. > > Nonsense. That's what bounce buffers can or *should* be used for too. In this case, the problem is that the bounce buffer code has attempted to allocate space for the transfer, but it's sufficiently physically fragmented that it requires too many s/g entries to describe it. Either the aha code needs to be fixed to allow more s/g entries, or the bounce buffer code needs to be fixed to allocate things in larger chunks and thus keep fragmentation down, or we should just abandon these useless 10-year-old ISA SCSI controllers and worry about more useful things. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 18:50:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id DBD9814DAE; Thu, 2 Dec 1999 18:50:45 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id MAA03053; Fri, 3 Dec 1999 12:49:49 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpdd02979; Fri Dec 3 12:49:46 1999 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id MAA16790; Fri, 3 Dec 1999 12:39:17 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id MAA02050; Fri, 3 Dec 1999 12:39:17 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id MAA04073; Fri, 3 Dec 1999 12:39:16 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199912030239.MAA04073@nymph.detir.qld.gov.au> To: Mike Smith Cc: Stephen McKay , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape driver problems References: <199912022205.OAA00570@mass.cdrom.com> In-Reply-To: <199912022205.OAA00570@mass.cdrom.com> from Mike Smith at "Thu, 02 Dec 1999 14:05:01 -0800" Date: Fri, 03 Dec 1999 12:39:16 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thursday, 2nd December 1999, Mike Smith wrote: >Either the aha code needs to be fixed to allow more s/g entries, or the >bounce buffer code needs to be fixed to allocate things in larger chunks >and thus keep fragmentation down, or we should just abandon these useless >10-year-old ISA SCSI controllers and worry about more useful things. 8) Well, I'm for changing the buffer code or the aha code, whichever makes the most sense at the time. Unfortunately I don't know that bit of the kernel yet. But I will eventually work it out because I have too many old ISA SCSI cards to take you up on your last suggestion. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 18:51: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 2F67B14EA6 for ; Thu, 2 Dec 1999 18:50:45 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id MAA03051; Fri, 3 Dec 1999 12:49:48 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd002979; Fri Dec 3 12:49:44 1999 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id MAA16844; Fri, 3 Dec 1999 12:44:41 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id MAA02390; Fri, 3 Dec 1999 12:44:40 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id MAA04138; Fri, 3 Dec 1999 12:44:39 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199912030244.MAA04138@nymph.detir.qld.gov.au> To: mjacob@feral.com Cc: freebsd-scsi@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Tape driver problems References: In-Reply-To: from Matthew Jacob at "Thu, 02 Dec 1999 10:10:49 -0800" Date: Fri, 03 Dec 1999 12:44:38 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thursday, 2nd December 1999, Matthew Jacob wrote: >> "mt status" with no tape loaded gives an error: >> >> mt: /dev/nrsa0: Device not configured >> >> which seems a bit harsh. Also the kernel logs error messages like: > >Yes, let me think about the error a bit. It may be more a question of >changing 'mt' to report something other than just perror. I think 'Device not configured' should be reserved for when the device is truly non-existent, not just when it has no tape. >I'll have to check what happened here. Do you have CAMDEBUG defined? Hmm. That looks like the sort of thing I might do. ;-) I'll confirm tonight to see if this is my fault. >Hmm, indeed. The density determining code does indeed issue a read of >MAXPHYS bytes. It seems to me that all HBA's should at least support that! >The maintainer for the 1542X will have to speak to this tho... I'll help with fixing the 1542B devices. I have lots of them! Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 22:17: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D4E9214D21 for ; Thu, 2 Dec 1999 22:17:00 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA04752; Thu, 2 Dec 1999 22:17:05 -0800 Date: Thu, 2 Dec 1999 22:17:05 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Stephen McKay Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-Reply-To: <199912030244.MAA04138@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Thursday, 2nd December 1999, Matthew Jacob wrote: > > >> "mt status" with no tape loaded gives an error: > >> > >> mt: /dev/nrsa0: Device not configured > >> > >> which seems a bit harsh. Also the kernel logs error messages like: > > > >Yes, let me think about the error a bit. It may be more a question of > >changing 'mt' to report something other than just perror. > > I think 'Device not configured' should be reserved for when the device > is truly non-existent, not just when it has no tape. Sigh. This is a tough one. Solaris (the 'gold' standard here :-)) says: EACCES The driver is opened for write access and the tape is write-protected or the tape unit is reserved by another host. EBUSY The tape drive is in use by another process. Only one process can use the tape drive at a time. The driver will allow a grace period for the other process to finish before reporting this error. EINVAL The number of bytes read or written is not a mul- tiple of the physical record size (fixed-length tape devices only). EIO During opening, the tape device is not ready because either no tape is in the drive, or the drive is not on-line. Once open, this error is returned if the requested I/O transfer could not be completed. ENOTTY This indicates that the tape device does not sup- port the requested ioctl function. ENXIO During opening, the tape device does not exist. ENOMEM This indicates that the record size on the tape drive is more than the requested size during read operation. The sa(4) man page doesn't say what these values should be for FreeBSD. Currently saopen returns: ENXIO - if it couldn't get the periph structure (no such device). if it couldn't acquire the periph structure. if the device has been marked invalid (AC_LOST_DEVICE) EBUSY - if the drive is already open. error - if it couldn't lock the periph structure lock, which itself calls cam_periph_acquire which will return ENXIO if the periph pointer is NULL. whatever samount returns, which will pretty much be whatever the generic midlayer code decides is appropriate based upon Sense Key/ASC/ASCQ for each command that is used during the mount operation. I suspect that this is where the ENXIO is coming from. If the last statement above is true, what you're asking for samount to be beefed up so the reason that samount fails can be propagated back to saopen which can then propagate back something more sensible to the caller (mt(1) in this case). Still, when all is said and done, mt(1), or other 'aware' applications, would have to be then beefed up to understand what a particular errno on open 'means'. Well, send-pr it as an RFE. It'll be a post 4.0 thingie tho. > > >I'll have to check what happened here. Do you have CAMDEBUG defined? > > Hmm. That looks like the sort of thing I might do. ;-) I'll confirm > tonight to see if this is my fault. > > >Hmm, indeed. The density determining code does indeed issue a read of > >MAXPHYS bytes. It seems to me that all HBA's should at least support that! > >The maintainer for the 1542X will have to speak to this tho... > > I'll help with fixing the 1542B devices. I have lots of them! I may solve this a different way. It may be just too much breakage to try and read MAXPHYS, particularly when either the HBA driver is broken. I actually have a 1542CF, but I'm not going to spend time now debugging that HBA driver. Try and change the MAXPHYS sizes in samount to 8192. I've done this to see what happens (not really sure yet whether it works as well as I'd like). I think that even an overrun record is fine for the throaway read I'm doing in samount- all this is trying to accomplish is to get the tape drive to *attempt* a media access- the contents of the data or the success/failure is irrelevant. The attempt at media access should get the f/w in the tape drive to figure out what kind of media is inserted, even if the read fails to transfer any data at all (like, even if there's a BLANK CHECK the drive will know what kind of media is inserted (hopefully)). Let me know if that works better- as soon as possible would be good. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 22:17:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 159D515090; Thu, 2 Dec 1999 22:17:20 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA04756; Thu, 2 Dec 1999 22:17:51 -0800 Date: Thu, 2 Dec 1999 22:17:51 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Stephen McKay Cc: Mike Smith , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-Reply-To: <199912030239.MAA04073@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Thursday, 2nd December 1999, Mike Smith wrote: > > >Either the aha code needs to be fixed to allow more s/g entries, or the > >bounce buffer code needs to be fixed to allocate things in larger chunks > >and thus keep fragmentation down, or we should just abandon these useless > >10-year-old ISA SCSI controllers and worry about more useful things. 8) > > Well, I'm for changing the buffer code or the aha code, whichever makes > the most sense at the time. Unfortunately I don't know that bit of the > kernel yet. But I will eventually work it out because I have too many old > ISA SCSI cards to take you up on your last suggestion. See other mail. I still believe that the AHA driver should work better, but it's a low priority item now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 22:31:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 4B3D414D2A; Thu, 2 Dec 1999 22:31:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA05573; Thu, 2 Dec 1999 22:32:36 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912030632.WAA05573@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: Stephen McKay , Mike Smith , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-reply-to: Your message of "Thu, 02 Dec 1999 22:17:51 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Dec 1999 22:32:36 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > On Thursday, 2nd December 1999, Mike Smith wrote: > > > > >Either the aha code needs to be fixed to allow more s/g entries, or the > > >bounce buffer code needs to be fixed to allocate things in larger chunks > > >and thus keep fragmentation down, or we should just abandon these useless > > >10-year-old ISA SCSI controllers and worry about more useful things. 8) > > > > Well, I'm for changing the buffer code or the aha code, whichever makes > > the most sense at the time. Unfortunately I don't know that bit of the > > kernel yet. But I will eventually work it out because I have too many old > > ISA SCSI cards to take you up on your last suggestion. > > See other mail. I still believe that the AHA driver should work better, > but it's a low priority item now. This particular issue is a defect in the bounce-buffering code; the 1542 is limited to 16 or maybe 17 s/g entries. (We allow 17, the Linux driver stops at 16.) This isn't an issue for most things until you get up near 64k, where fragmentation lets you run out of page-sized entries. I'm not sure how best we could work around this without clustering pages in bounce-buffer memory. If you've got any neat ideas I'll happily file them for next time someone goes looking at that code. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 22:41: 8 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9001514D12; Thu, 2 Dec 1999 22:41:06 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA04811; Thu, 2 Dec 1999 22:42:18 -0800 Date: Thu, 2 Dec 1999 22:42:18 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: Stephen McKay , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-Reply-To: <199912030632.WAA05573@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > See other mail. I still believe that the AHA driver should work better, > > but it's a low priority item now. > > This particular issue is a defect in the bounce-buffering code; the 1542 > is limited to 16 or maybe 17 s/g entries. (We allow 17, the Linux driver > stops at 16.) This isn't an issue for most things until you get up near > 64k, where fragmentation lets you run out of page-sized entries. I'm not > sure how best we could work around this without clustering pages in > bounce-buffer memory. If you've got any neat ideas I'll happily file > them for next time someone goes looking at that code. I've hacked on the AHA1542X substantially, but it's been years. It actually had a reasonable target mode. I just don't have time and if I solve the current problem a different way, we don't have to worry about it at the moment. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 2 23:18:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6C90914D6E; Thu, 2 Dec 1999 23:18:50 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id XAA04898; Thu, 2 Dec 1999 23:19:50 -0800 Date: Thu, 2 Dec 1999 23:19:50 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: strange panic on Alpha, SCSI disk *type* related In-Reply-To: <199911251900.UAA01014@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > As Matthew Jacob wrote ... > > Hi Matt, > > Ever since the firmware is back in the driver the machine just works > like a charm. Are you still interested in digging into my ancient > isp f/w ;-) ? I'm happy with things the way they are. > > Wilko > Sorry, I wuz away and now just back. If you're happy then we'll let it go. I'm backporting the -current stuff into RELENG_3 tonite. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 3 7: 5:16 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id 3915E151AB for ; Fri, 3 Dec 1999 07:05:11 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id KAA82511 for ; Fri, 3 Dec 1999 10:05:11 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id KAA07820 for scsi@freebsd.org; Fri, 3 Dec 1999 10:05:10 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912031505.KAA07820@rtfm.newton> Subject: cdda2wav: cam_periph_mapmem: attempt to map .... To: scsi@freebsd.org Date: Fri, 3 Dec 1999 10:05:10 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Fri, 3 Dec 1999 09:41:05 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA57954; Fri, 3 Dec 1999 10:40:51 -0700 (MST) (envelope-from ken) Message-Id: <199912031740.KAA57954@panzer.kdm.org> Subject: Re: cdda2wav: cam_periph_mapmem: attempt to map .... In-Reply-To: <199912031505.KAA07820@rtfm.newton> from Mikhail Teterin at "Dec 3, 1999 10:05:10 am" To: mi@kot.ne.mediaone.net (Mikhail Teterin) Date: Fri, 3 Dec 1999 10:40:51 -0700 (MST) Cc: scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mikhail Teterin wrote... > Hello! > > I'm trying to read tracks off of this imperfect audio CD. cdda2wav seems > to run to completion (the output .wav file is exactly the promised > size), but it ends with: > > cdda2wav: Argument list too long. Cannot send SCSI cmd via ioctl > > The kernel logs the following: > > cam_periph_mapmem: attempt to map 4294910848 bytes, which is\ > greater than DFLTPHYS(65536) > > My command line is: > > cdda2wav -P 18 -D1,1,0 -t 3 -g -H -S 3 /home/mi/zemfira/mi_z3.wav > > Any comments? Thanks! What version of cdda2wav are you using, and what version of FreeBSD are you using? The amount it is trying to read is probably -1 or something close to it. Can you try using tosha and see if it works for you? I suspect this may be a bug in cdda2wav. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 3 9:45:28 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id AD63F1504A; Fri, 3 Dec 1999 09:45:21 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id KAA11671; Fri, 3 Dec 1999 10:33:26 -0700 (MST) Date: Fri, 3 Dec 1999 10:33:26 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199912031733.KAA11671@narnia.plutotech.com> To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: Tape driver problems X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <199912030632.WAA05573@mass.cdrom.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199912030632.WAA05573@mass.cdrom.com> you wrote: >> > On Thursday, 2nd December 1999, Mike Smith wrote: >> > >> > >Either the aha code needs to be fixed to allow more s/g entries, or the >> > >bounce buffer code needs to be fixed to allocate things in larger chunks >> > >and thus keep fragmentation down, or we should just abandon these useless >> > >10-year-old ISA SCSI controllers and worry about more useful things. 8) >> > >> > Well, I'm for changing the buffer code or the aha code, whichever makes >> > the most sense at the time. Unfortunately I don't know that bit of the >> > kernel yet. But I will eventually work it out because I have too many old >> > ISA SCSI cards to take you up on your last suggestion. >> >> See other mail. I still believe that the AHA driver should work better, >> but it's a low priority item now. > > This particular issue is a defect in the bounce-buffering code; the 1542 > is limited to 16 or maybe 17 s/g entries. (We allow 17, the Linux driver > stops at 16.) This isn't an issue for most things until you get up near > 64k, where fragmentation lets you run out of page-sized entries. I'm not > sure how best we could work around this without clustering pages in > bounce-buffer memory. If you've got any neat ideas I'll happily file > them for next time someone goes looking at that code. The bounce buffering code doesn't perform coalessing of data yet because I never found an algorithm I liked for it. The NetBSD approach of making the bounce buffer 64K big and copying the whole thing if any portion needs to be bounced doesn't appeal to me (it doesn't scale well and consumes much too much memory). Still, I'm surprised that this is the cause of this particular failure. A kernel malloc of 64K should return a page aligned chunk of memory. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 3 9:55: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 95F3E15200 for ; Fri, 3 Dec 1999 09:55:03 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA06538; Fri, 3 Dec 1999 09:55:52 -0800 Date: Fri, 3 Dec 1999 09:55:51 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-Reply-To: <199912031733.KAA11671@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > This particular issue is a defect in the bounce-buffering code; the 1542 > > is limited to 16 or maybe 17 s/g entries. (We allow 17, the Linux driver > > stops at 16.) This isn't an issue for most things until you get up near > > 64k, where fragmentation lets you run out of page-sized entries. I'm not > > sure how best we could work around this without clustering pages in > > bounce-buffer memory. If you've got any neat ideas I'll happily file > > them for next time someone goes looking at that code. > > The bounce buffering code doesn't perform coalessing of data yet because > I never found an algorithm I liked for it. The NetBSD approach of > making the bounce buffer 64K big and copying the whole thing if any > portion needs to be bounced doesn't appeal to me (it doesn't scale > well and consumes much too much memory). You pay for what you get. If you are really still using ISADMA mass storage, blow 128k or MAXPHYS already.. IMO... > Still, I'm surprised > that this is the cause of this particular failure. A kernel malloc > of 64K should return a page aligned chunk of memory. That's a very good point. Maybe something else is happening here. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 3 10: 3:37 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 675DA14FB9 for ; Fri, 3 Dec 1999 10:03:31 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id NAA00744; Fri, 3 Dec 1999 13:02:39 -0500 (EST) (envelope-from mi) Message-Id: <199912031802.NAA00744@misha.cisco.com> Subject: Re: cdda2wav: cam_periph_mapmem: attempt to map .... In-Reply-To: <199912031740.KAA57954@panzer.kdm.org> from "Kenneth D. Merry" at "Dec 3, 1999 10:40:51 am" To: scsi@FreeBSD.ORG Date: Fri, 3 Dec 1999 13:02:39 -0500 (EST) Cc: Mikhail Teterin , scsi@FreeBSD.ORG Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry once wrote: > > I'm trying to read tracks off of this imperfect audio CD. cdda2wav > > seems to run to completion (the output .wav file is exactly the > > promised size), but it ends with: > > > > cdda2wav: Argument list too long. Cannot send SCSI cmd via ioctl > > > > The kernel logs the following: > > > > cam_periph_mapmem: attempt to map 4294910848 bytes, which is\ > > greater than DFLTPHYS(65536) > > > > My command line is: > > > > cdda2wav -P 18 -D1,1,0 -t 3 -g -H -S 3 /home/mi/zemfira/mi_z3.wav > What version of cdda2wav are you using, and what version of FreeBSD > are you using? The one from cdrecord "Version 1.8a32_freebsd_3.3-stable_i386_i386" FreeBSD rtfm.newton 3.3-STABLE FreeBSD 3.3-STABLE #2: Mon Oct 18 17:57:51 EDT 1999 > Can you try using tosha and see if it works for you? I suspect this > may be a bug in cdda2wav. I will, I guess. cdda2wav comes with the cdrecord, and gcombust knows it too... Thanks! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 3 10:11:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 8CD1B15211 for ; Fri, 3 Dec 1999 10:11:27 -0800 (PST) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id KAA00529; Fri, 3 Dec 1999 10:12:07 -0700 (MST) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199912031712.KAA00529@caspian.plutotech.com> X-Mailer: exmh version 2.1.0 09/18/1999 To: mjacob@feral.com Cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-reply-to: Your message of "Fri, 03 Dec 1999 09:55:51 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Dec 1999 10:12:07 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> The bounce buffering code doesn't perform coalessing of data yet because >> I never found an algorithm I liked for it. The NetBSD approach of >> making the bounce buffer 64K big and copying the whole thing if any >> portion needs to be bounced doesn't appeal to me (it doesn't scale >> well and consumes much too much memory). > >You pay for what you get. If you are really still using ISADMA mass >storage, blow 128k or MAXPHYS already.. IMO... We do, but we allocate and dole it out as individual pages. NetBSD allocates MAXPHYS per possible transaction on each card which turns out to be 1MB of < 16MB memory per card. This doesn't scale. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 3 10:18: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 881761507D; Fri, 3 Dec 1999 10:17:56 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA06637; Fri, 3 Dec 1999 10:19:06 -0800 Date: Fri, 3 Dec 1999 10:19:06 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: scsi@FreeBSD.ORG Subject: bounce buffers (was Re: Tape driver problems) In-Reply-To: <199912031712.KAA00529@caspian.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> The bounce buffering code doesn't perform coalessing of data yet because > >> I never found an algorithm I liked for it. The NetBSD approach of > >> making the bounce buffer 64K big and copying the whole thing if any > >> portion needs to be bounced doesn't appeal to me (it doesn't scale > >> well and consumes much too much memory). > > > >You pay for what you get. If you are really still using ISADMA mass > >storage, blow 128k or MAXPHYS already.. IMO... > > We do, but we allocate and dole it out as individual pages. NetBSD allocates > MAXPHYS per possible transaction on each card which turns out to be 1MB of > < 16MB memory per card. This doesn't scale. It's not important that ISADMA scales. If somebody wants to put 4 1542s in a system, they can pay a lot for the privilege of not buying 2940s. Still, it needn't be per card. It can be per-system and it's not for wired down usage (or you could add a flag for wired down usage). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 3 11: 9:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id C8B681520F for ; Fri, 3 Dec 1999 11:09:32 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id LAA11735; Fri, 3 Dec 1999 11:58:29 -0700 (MST) Date: Fri, 3 Dec 1999 11:58:29 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199912031858.LAA11735@narnia.plutotech.com> To: mjacob@feral.com Cc: scsi@FreeBSD.org Subject: Re: bounce buffers (was Re: Tape driver problems) X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: >> >You pay for what you get. If you are really still using ISADMA mass >> >storage, blow 128k or MAXPHYS already.. IMO... >> >> We do, but we allocate and dole it out as individual pages. NetBSD allocates >> MAXPHYS per possible transaction on each card which turns out to be 1MB of >> < 16MB memory per card. This doesn't scale. > > It's not important that ISADMA scales. If somebody wants to put 4 1542s in > a system, they can pay a lot for the privilege of not buying 2940s. The system may not boot if you cannot find the necessary space. You're probably also guaranteed that your sound card fails to work too. > Still, it needn't be per card. It can be per-system and it's not for wired > down usage (or you could add a flag for wired down usage). Right. There are better ways to do this and at some point it will happen. I just need to decide how I want to track fragmentation and decide which fragments to coaless/align. This type of thing doesn't just happen for ISA bus stuff (other devices may have a limited supply of S/G entries), so I'd like to take a shot at making it somewhat smart. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 3 11:10:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C34191520F for ; Fri, 3 Dec 1999 11:10:31 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA06832; Fri, 3 Dec 1999 11:11:23 -0800 Date: Fri, 3 Dec 1999 11:11:22 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: bounce buffers (was Re: Tape driver problems) In-Reply-To: <199912031858.LAA11735@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In article you wrote: > >> >You pay for what you get. If you are really still using ISADMA mass > >> >storage, blow 128k or MAXPHYS already.. IMO... > >> > >> We do, but we allocate and dole it out as individual pages. NetBSD allocates > >> MAXPHYS per possible transaction on each card which turns out to be 1MB of > >> < 16MB memory per card. This doesn't scale. > > > > It's not important that ISADMA scales. If somebody wants to put 4 1542s in > > a system, they can pay a lot for the privilege of not buying 2940s. > > The system may not boot if you cannot find the necessary space. You're > probably also guaranteed that your sound card fails to work too. *cough*.... > > > Still, it needn't be per card. It can be per-system and it's not for wired > > down usage (or you could add a flag for wired down usage). > > Right. There are better ways to do this and at some point it will happen. > I just need to decide how I want to track fragmentation and decide which > fragments to coaless/align. This type of thing doesn't just happen for > ISA bus stuff (other devices may have a limited supply of S/G entries), so > I'd like to take a shot at making it somewhat smart. A shot delayed is a shot denied.... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 1:34:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 2EB3314C3B for ; Sat, 4 Dec 1999 01:34:16 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id TAA06333; Sat, 4 Dec 1999 19:33:18 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd006331; Sat Dec 4 19:33:13 1999 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id TAA14917; Sat, 4 Dec 1999 19:30:20 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id TAA21165; Sat, 4 Dec 1999 19:30:19 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id TAA02368; Sat, 4 Dec 1999 19:30:19 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199912040930.TAA02368@nymph.detir.qld.gov.au> To: mjacob@feral.com Cc: freebsd-scsi@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Tape driver problems References: In-Reply-To: from Matthew Jacob at "Thu, 02 Dec 1999 22:17:05 -0800" Date: Sat, 04 Dec 1999 19:30:19 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thursday, 2nd December 1999, Matthew Jacob wrote: >> On Thursday, 2nd December 1999, Matthew Jacob wrote: >> >> >> mt: /dev/nrsa0: Device not configured >[Extra errno values and how solaris does it] >Well, send-pr it as an RFE. It'll be a post 4.0 thingie tho. I'll put something together if not beaten to it. >> >I'll have to check what happened here. Do you have CAMDEBUG defined? >> >> Hmm. That looks like the sort of thing I might do. ;-) I'll confirm >> tonight to see if this is my fault. I have INVARIANTS and INVARIANT_SUPPORT but not CAMDEBUG. I've not tried the post-1.39 versions yet, so you've probably fixed this. >Try and change the MAXPHYS sizes in samount to 8192. I've done this to see >what happens (not really sure yet whether it works as well as I'd like). I tried using MAXPHYS, 64K and 8192. I tried a blank tape (fresh from the wrapper) and 2 tapes already written at 2GB and 5GB density with a 32KB blocksize. MAXPHYS caused the "too many segs" error. The others didn't cause any errors. Further, a kernel from mid November did not correctly determine the initial density. The intriguing thing is that all 3 gave the correct density for each tape. From this I concluded that the fake read was unnecessary. I tried with the read commented out and it still works. (I left in the rewind and other stuff.) So, for my equipment at least, some other recent change has produced the improved density detection. Also, the extra read is not free. It adds an extra 30 seconds to the startup time. It takes about 40 seconds from tape insertion to ready, then the density determining read adds 30 seconds. Before this patch, an initial read starts after about 6 seconds. Now it takes about 36 seconds. Well, I'm off to test the new changes. I let you know if I learn anything. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 8: 1:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D2F3B14F6C for ; Sat, 4 Dec 1999 08:01:54 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id IAA09989; Sat, 4 Dec 1999 08:03:06 -0800 Date: Sat, 4 Dec 1999 08:03:06 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Stephen McKay Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-Reply-To: <199912040930.TAA02368@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >Well, send-pr it as an RFE. It'll be a post 4.0 thingie tho. > > I'll put something together if not beaten to it. You're still on the hook.. > > >> >I'll have to check what happened here. Do you have CAMDEBUG defined? > >> > >> Hmm. That looks like the sort of thing I might do. ;-) I'll confirm > >> tonight to see if this is my fault. > > I have INVARIANTS and INVARIANT_SUPPORT but not CAMDEBUG. I've not tried > the post-1.39 versions yet, so you've probably fixed this. Check and see. > > >Try and change the MAXPHYS sizes in samount to 8192. I've done this to see > >what happens (not really sure yet whether it works as well as I'd like). > > I tried using MAXPHYS, 64K and 8192. I tried a blank tape (fresh from > the wrapper) and 2 tapes already written at 2GB and 5GB density with a > 32KB blocksize. MAXPHYS caused the "too many segs" error. The others > didn't cause any errors. Further, a kernel from mid November did not > correctly determine the initial density. Yup. What I expect. I already did change the read size to 8K. > > The intriguing thing is that all 3 gave the correct density for each tape. > >From this I concluded that the fake read was unnecessary. I tried with > the read commented out and it still works. (I left in the rewind and > other stuff.) So, for my equipment at least, some other recent change > has produced the improved density detection. Well, there was breakage at one point where the latched up values never got updated. > > Also, the extra read is not free. It adds an extra 30 seconds to the > startup time. It takes about 40 seconds from tape insertion to ready, > then the density determining read adds 30 seconds. Before this patch, an > initial read starts after about 6 seconds. Now it takes about 36 seconds. Yes. I've thought about this. The only way to get around this is to go back to the FBSD 2.X version of quirking tapes (which I don't want to do) that need this detection, or have *another* state of MOUNTED_BUT_NOT_READ so that the test read only occurs if an ioctl to get current density happens *before* a read or a write. Each quirk type added becomes a sure set of questions and misapplication. I avoid them whenever I can. The extra state stuff above is doable, but I didn't want to add this complexity in a hurry. Send-pr it. > > Well, I'm off to test the new changes. I let you know if I learn anything. > > Stephen. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 8:38:55 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 3FDDC14BDD for ; Sat, 4 Dec 1999 08:38:50 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id CAA14194; Sun, 5 Dec 1999 02:38:52 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd014192; Sun Dec 5 02:38:44 1999 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id CAA17204 for ; Sun, 5 Dec 1999 02:37:59 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id CAA29245 for ; Sun, 5 Dec 1999 02:37:59 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id CAA03403; Sun, 5 Dec 1999 02:37:58 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199912041637.CAA03403@nymph.detir.qld.gov.au> To: freebsd-scsi@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Administrivia: charter clarification question Date: Sun, 05 Dec 1999 02:37:58 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In response to my recent thread "Tape driver problems" I was advised twice by a respectable FreeBSD citizen that my posting was misfiled and should have gone to -current. Quote: "If it's -CURRENT, talk about it on -CURRENT. That overrides anything else." It is my belief that scsi stuff should be discussed on -scsi no matter whether it is -current, -stable, or some older release. Am I wrong? The charter as it stands is rather thin: >>>> info freebsd-scsi FREEBSD-SCSI SCSI subsystem This is the mailing list for people working on the scsi subsystem for FreeBSD. Please note that this is not a whinge, I am not after ammunition for an "I told you so", and I'm not going to say who contacted me. I just want the system to work smoothly. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 8:52:16 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id ACE3F14C9C for ; Sat, 4 Dec 1999 08:52:14 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id IAA10062; Sat, 4 Dec 1999 08:53:10 -0800 Date: Sat, 4 Dec 1999 08:53:10 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Stephen McKay Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Administrivia: charter clarification question In-Reply-To: <199912041637.CAA03403@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Really? Well, perhaps it's *my* fault... but I would have thought -scsi issues should be in -scsi. The tape driver issues were specific to -scsi. I suppose -current would have been okay, but due to volume I probably would have missed it. So, if my feedback is important in the discussion, it's better to have this in -scsi where I pay more attention. :-) On Sun, 5 Dec 1999, Stephen McKay wrote: > In response to my recent thread "Tape driver problems" I was advised twice > by a respectable FreeBSD citizen that my posting was misfiled and should > have gone to -current. Quote: > > "If it's -CURRENT, talk about it on -CURRENT. That overrides anything else." > > It is my belief that scsi stuff should be discussed on -scsi no matter > whether it is -current, -stable, or some older release. Am I wrong? > The charter as it stands is rather thin: > > >>>> info freebsd-scsi > FREEBSD-SCSI SCSI subsystem > This is the mailing list for people working on the scsi subsystem > for FreeBSD. > > Please note that this is not a whinge, I am not after ammunition for an > "I told you so", and I'm not going to say who contacted me. I just want > the system to work smoothly. > > Stephen. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 8:56:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2C75E14C9C for ; Sat, 4 Dec 1999 08:56:07 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id JAA69209; Sat, 4 Dec 1999 09:55:57 -0700 (MST) (envelope-from ken) Message-Id: <199912041655.JAA69209@panzer.kdm.org> Subject: Re: Administrivia: charter clarification question In-Reply-To: <199912041637.CAA03403@nymph.detir.qld.gov.au> from Stephen McKay at "Dec 5, 1999 02:37:58 am" To: syssgm@detir.qld.gov.au (Stephen McKay) Date: Sat, 4 Dec 1999 09:55:57 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Stephen McKay wrote... > In response to my recent thread "Tape driver problems" I was advised twice > by a respectable FreeBSD citizen that my posting was misfiled and should > have gone to -current. Quote: > > "If it's -CURRENT, talk about it on -CURRENT. That overrides anything else." > > It is my belief that scsi stuff should be discussed on -scsi no matter > whether it is -current, -stable, or some older release. Am I wrong? > The charter as it stands is rather thin: > > >>>> info freebsd-scsi > FREEBSD-SCSI SCSI subsystem > This is the mailing list for people working on the scsi subsystem > for FreeBSD. You are correct. Any SCSI problem should be discussed here first, instead of in -current or -stable. I certainly read this list before any other FreeBSD list, and I suspect the same is true for Justin and Matt as well. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 11:43:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 68A5814F71; Sat, 4 Dec 1999 11:43:36 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA10561; Sat, 4 Dec 1999 11:43:39 -0800 Date: Sat, 4 Dec 1999 11:43:39 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: ISP firmware compiled in as a default.... In-Reply-To: <199911251900.UAA01014@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm now wondering whether or not this would be a good idea or not. Right now, the default is *not* to compile in the firmware. However, I had a bit of a hard time with the SRM loaded f/w (and this is the latest) when I had both an internal drive and 2 external tape drives. This problem went away when I went back to compiling in the f/w which then downloaded. Jason (bless his heart) Thorpe kept on claiming that NetBSD-alpha was completely broken without the f/w- I never saw such breakage at all and real active details were not provided, and in fact *you* (Wilko) are the only one who I know was completely blocked w/o the f/w. So, I'm in a bit of a quandary now as to what the right thing to do is. There is the open PR about putting the f/w into kld's- that'd probably be mostly the right thing to do. Before that happens, though, should the default be to have the f/w compiled in? It adds ~200K to kernel bloat (although this could be cut down by only compiling in 1040 f/w instead of including 1080, 2100 and 2200 f/w as well). Opinions? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 14: 9:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 53E1914D29; Sat, 4 Dec 1999 14:08:47 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA01901; Sat, 4 Dec 1999 22:57:10 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA88557; Sat, 4 Dec 1999 22:42:58 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912042142.WAA88557@yedi.iaf.nl> Subject: Re: ISP firmware compiled in as a default.... In-Reply-To: from Matthew Jacob at "Dec 4, 1999 11:43:39 am" To: mjacob@feral.com Date: Sat, 4 Dec 1999 22:42:57 +0100 (CET) Cc: gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Matthew Jacob wrote ... > I'm now wondering whether or not this would be a good idea or not. Right > now, the default is *not* to compile in the firmware. OK, you told me that before. > However, I had a bit of a hard time with the SRM loaded f/w (and this is > the latest) when I had both an internal drive and 2 external tape drives. > This problem went away when I went back to compiling in the f/w which then > downloaded. Did you have both internal AND external devices on the same KZPBA card? FYI: we (== Compaq) don't support this. Obviously this decision is based on the f/w that is in the SRM code. Tests have shown it really does not work well when both internal and external devices are present on the same card. YMMV of course and I obviously don't know what was biting you. > Jason (bless his heart) Thorpe kept on claiming that NetBSD-alpha was > completely broken without the f/w- I never saw such breakage at all and > real active details were not provided, and in fact *you* (Wilko) are the > only one who I know was completely blocked w/o the f/w. I'm apparantly the only one with a machine I cannot load SRM onto with more or less recent Qlogic f/w inside. An exception to the rule obviously. People running older Eval Board alpha's will likely suffer from the same problem. But considering the rumors around former ARC-only systems this might change. Wild guess... > So, I'm in a bit of a quandary now as to what the right thing to do is. Don't shoot me: the right thing to do is to make it possible to boot FreeBSD/alpha from a CDROM. With or without Qlogic firmware FreeBSD/alpha is quickly getting too big to be really practical as far as floppy booting goes. NetBSD can do CDROM booting, but I don't really understand the issues around CDROM bootability. Having fixed the size problem the extra 200Kb bloat becomes somewhat academic I think. People not willing to build a custom kernel for their particular hardware.. well, they should invest a bit of time to work out kernel building in the first place. Added bonus of bootable CDROMs: you can do 'fixit' like work. Might come in handy (considering some recent postings ;-) ;-) > There is the open PR about putting the f/w into kld's- that'd probably be > mostly the right thing to do. Before that happens, though, should the > default be to have the f/w compiled in? It adds ~200K to kernel bloat I'd say the issue is seperated into an installation kernel and a kernel built from source once the system is installed. In the latter case I think we can live without compiled-in f/w, making compiling-in optional for those who really need it (people like me ;-) > (although this could be cut down by only compiling in 1040 f/w instead of > including 1080, 2100 and 2200 f/w as well). Hm. The DEC-sanctioned cards (as far as SRM booting goes, so for system disks) only use 1040's if I'm not mistaken. So this might be the most practical short-term solution. How much would 1040-only f/w add to the installation kernel ? > Opinions? Well, some thought. Hope they are somewhat helpful. > -matt Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 14:10:12 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (castles545.castles.com [208.214.165.109]) by hub.freebsd.org (Postfix) with ESMTP id 807AF14C2E; Sat, 4 Dec 1999 14:10:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA04921; Sat, 4 Dec 1999 14:09:12 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912042209.OAA04921@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: Wilko Bulte , gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: ISP firmware compiled in as a default.... In-reply-to: Your message of "Sat, 04 Dec 1999 11:43:39 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Dec 1999 14:09:12 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > So, I'm in a bit of a quandary now as to what the right thing to do is. > There is the open PR about putting the f/w into kld's- that'd probably be > mostly the right thing to do. Before that happens, though, should the > default be to have the f/w compiled in? It adds ~200K to kernel bloat > (although this could be cut down by only compiling in 1040 f/w instead of > including 1080, 2100 and 2200 f/w as well). > > Opinions? If you build GENERIC with all the firmware compiled in, then gzip the resulting kernel binary, how big is the file? If it'll fit on a 1.44MB floppy with room for the loader as well, then put it in. If not, then don't put it in. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 14:11:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3640B153F1; Sat, 4 Dec 1999 14:11:01 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA11061; Sat, 4 Dec 1999 14:10:13 -0800 Date: Sat, 4 Dec 1999 14:10:13 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: Wilko Bulte , gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: ISP firmware compiled in as a default.... In-Reply-To: <199912042209.OAA04921@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org How big is the loader? On Sat, 4 Dec 1999, Mike Smith wrote: > > So, I'm in a bit of a quandary now as to what the right thing to do is. > > There is the open PR about putting the f/w into kld's- that'd probably be > > mostly the right thing to do. Before that happens, though, should the > > default be to have the f/w compiled in? It adds ~200K to kernel bloat > > (although this could be cut down by only compiling in 1040 f/w instead of > > including 1080, 2100 and 2200 f/w as well). > > > > Opinions? > > If you build GENERIC with all the firmware compiled in, then gzip the > resulting kernel binary, how big is the file? If it'll fit on a 1.44MB > floppy with room for the loader as well, then put it in. If not, then > don't put it in. 8) > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 15:53:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id E2DAA15451 for ; Sat, 4 Dec 1999 15:53:14 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA06295 for freebsd-scsi@freebsd.org; Sun, 5 Dec 1999 00:42:05 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA29971 for freebsd-scsi@freebsd.org; Sat, 4 Dec 1999 23:45:56 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912042245.XAA29971@yedi.iaf.nl> Subject: not so fast Fast SCSI? To: freebsd-scsi@freebsd.org (FreeBSD SCSI hackers) Date: Sat, 4 Dec 1999 23:45:56 +0100 (CET) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Any clue why da0 is not negotiating for Fast SCSI speeds? A Barracuda 15150W is fast SCSI after all. Wilko --- pci1: on pcib1 isp0: irq 12 at device 8.0 on pci1 isp0: interrupting at CIA irq 12 ... da0 at isp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) cd0 at isp0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present ... bash# uname -a FreeBSD miata.iaf.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Sep 16 22:27:40 CEST 1999 root@miata.iaf.nl:/usr/src/sys/compile/MIATA alpha -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 16: 2:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1A178153A7 for ; Sat, 4 Dec 1999 16:02:49 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id QAA11457; Sat, 4 Dec 1999 16:03:21 -0800 Date: Sat, 4 Dec 1999 16:03:21 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: FreeBSD SCSI hackers Subject: Re: not so fast Fast SCSI? In-Reply-To: <199912042245.XAA29971@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is not correctly negotiating out of async mode. I cannot deal with this for several days. I would suspect that NVRAM settings are pooched- try disabling them by doing set isp_nonvram=1 at the loader prompt and see what happens. On Sat, 4 Dec 1999, Wilko Bulte wrote: > Any clue why da0 is not negotiating for Fast SCSI speeds? A Barracuda 15150W > is fast SCSI after all. > > Wilko > --- > > > pci1: on pcib1 > isp0: irq 12 at device 8.0 on pci1 > isp0: interrupting at CIA irq 12 > > ... > > da0 at isp0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 3.300MB/s transfers > da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) > cd0 at isp0 bus 0 target 6 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 10.000MB/s transfers (10.000MHz, offset 8) > cd0: Attempt to query device size failed: NOT READY, Medium not present > > ... > > bash# uname -a > FreeBSD miata.iaf.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Sep 16 22:27:40 > CEST 1999 root@miata.iaf.nl:/usr/src/sys/compile/MIATA alpha > > -- > | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - > |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 18: 4: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 8709C151CB; Sat, 4 Dec 1999 18:04:05 -0800 (PST) From: "Jonathan M. Bresler" To: syssgm@detir.qld.gov.au Cc: freebsd-scsi@freebsd.org, syssgm@detir.qld.gov.au In-reply-to: <199912041637.CAA03403@nymph.detir.qld.gov.au> (message from Stephen McKay on Sun, 05 Dec 1999 02:37:58 +1000) Subject: Re: Administrivia: charter clarification question Message-Id: <19991205020405.8709C151CB@hub.freebsd.org> Date: Sat, 4 Dec 1999 18:04:05 -0800 (PST) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Stephen, Hmmm....whether on item gets dicussed on scsi or current, is as you note, not the most important item. much more important that the item get discussed and resolved. my personal take on it is that it should be discussed on scsi. a courtesy email ot current noting that its being discussed on scsi would be a good thing. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 19:33: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id 6EEAE1508F; Sat, 4 Dec 1999 19:32:47 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id TAA16773; Sat, 4 Dec 1999 19:32:35 -0800 (PST) Message-Id: <199912050332.TAA16773@lestat.nas.nasa.gov> To: mjacob@feral.com Cc: Wilko Bulte , gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: ISP firmware compiled in as a default.... Reply-To: Jason Thorpe From: Jason Thorpe Date: Sat, 04 Dec 1999 19:32:34 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 4 Dec 1999 11:43:39 -0800 (PST) Matthew Jacob wrote: > Jason (bless his heart) Thorpe kept on claiming that NetBSD-alpha was > completely broken without the f/w- I never saw such breakage at all and > real active details were not provided, and in fact *you* (Wilko) are the > only one who I know was completely blocked w/o the f/w. Oh, c'mon. The whole reason you started always downloading the firmware into the ISP is because cgd reported to you that the SRM's ISP firmware on his AlphaStation 500 didn't play nice with the NetBSD driver. I'm pretty sure I have an archive of the e-mail conversation (which was all CC'd to me). And, I'm pretty sure there's actually a PR in the database about a PC164 user having to back-rev his machine to before the firmware was yanked because his ISP no longer worked after a *power-cycle* (i.e. the RAM on the card lost power, and the SRM-loaded firmware was not functional with the NetBSD driver). Not only that, but users of CATS boards (arm32) were completely left out in the cold; the firmware on those machines doesn't run the ISP BIOS, and thus had no way of loading in the firmware into the card. The portmaster went as far as to yank the "isp" driver out of the example kernel config files in that port. ...or don't you read the `source-changes' mailing list? Anyhow, the arm32 case will happen on *ANY* platform who's firmware doesn't natively understand the ISP. So, not loading the firmware by default screws over anyone who tries to put it in an arm32, macppc, Atari Hades, etc. Now, you could do something like have #ifdefs for each firmware, i.e. #ifdef ISP_1020_FIRMWARE ... #ifdef ISP_1080_FIRMWARE ... #ifdef ISP_2100_FIRMWARE ...actually, I just noticed... there's already ISP_DISABLE_..._SUPPORT #ifdefs in there. Why not key on those? -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 19:46:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BE70B1508F; Sat, 4 Dec 1999 19:46:13 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id TAA11983; Sat, 4 Dec 1999 19:47:18 -0800 Date: Sat, 4 Dec 1999 19:47:18 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jason Thorpe Cc: Wilko Bulte , gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: ISP firmware compiled in as a default.... In-Reply-To: <199912050332.TAA16773@lestat.nas.nasa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 4 Dec 1999, Jason Thorpe wrote: > On Sat, 4 Dec 1999 11:43:39 -0800 (PST) > Matthew Jacob wrote: > > > Jason (bless his heart) Thorpe kept on claiming that NetBSD-alpha was > > completely broken without the f/w- I never saw such breakage at all and > > real active details were not provided, and in fact *you* (Wilko) are the > > only one who I know was completely blocked w/o the f/w. > > Oh, c'mon. The whole reason you started always downloading the firmware > into the ISP is because cgd reported to you that the SRM's ISP firmware > on his AlphaStation 500 didn't play nice with the NetBSD driver. I'm > pretty sure I have an archive of the e-mail conversation (which was all > CC'd to me). Nope, I don't think so. I pretty much always had been downloading f/w. There was a hop skip and dance with some f/w and Chris's machine and some stupid ass bugs in 7.55 f/w where you'd tell it to renegotiate and then ask it what it had done and it lied and gave back random values. > > And, I'm pretty sure there's actually a PR in the database about a > PC164 user having to back-rev his machine to before the firmware was > yanked because his ISP no longer worked after a *power-cycle* (i.e. the > RAM on the card lost power, and the SRM-loaded firmware was not functional > with the NetBSD driver). Yep. But I've concluded that this wasn't a Digital supplied board (and closed the PR) so the SRM wasn't starting it. > > Not only that, but users of CATS boards (arm32) were completely left out > in the cold; the firmware on those machines doesn't run the ISP BIOS, and > thus had no way of loading in the firmware into the card. The portmaster > went as far as to yank the "isp" driver out of the example kernel config > files in that port. So I saw. I never claimed it was not completely broken in some cases. For example, if there was a sparc64/PCI port going, it'd be mostly broken there because only PTI PCI cards have fcode that gets the f/w started. Read what I wrote above. You claimed NetBSD-alpha was completely broken. But neglected to provide details. It wasn't completely broken, but it's been problematic in a number of cases. > ...or don't you read the `source-changes' mailing list? Nope- the netbsd changes list is too hard to read. > > Anyhow, the arm32 case will happen on *ANY* platform who's firmware > doesn't natively understand the ISP. So, not loading the firmware by > default screws over anyone who tries to put it in an arm32, macppc, > Atari Hades, etc. Yup. Such is life and too bad. It is now corrected by being able to have the f/w back in. I've also said that if I can get more information out of Qlogic I can figure out how to extract the onboard firmware in flashram down into sram on the card and get it going if the BIOS hasn't. > > Now, you could do something like have #ifdefs for each firmware, > i.e. > > #ifdef ISP_1020_FIRMWARE > > ... > > #ifdef ISP_1080_FIRMWARE > > ... > > #ifdef ISP_2100_FIRMWARE > > ...actually, I just noticed... there's already ISP_DISABLE_..._SUPPORT > #ifdefs in there. Why not key on those? I do have "compile in these" f/w selectors, and an overall "compile in all f/w" selectors. The NetBSD integration, respecting your unexplained concerns, wraps *around* this by defining ISP_COMPILE_FW in isp_netbsd.h. If I had time to blow on it, it would be a lot better. The subject under discussion *here* is whether to have freebsd follow the settings for NetBSD and compile/load it by default. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 19:57:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id 7A6CA1513C; Sat, 4 Dec 1999 19:57:40 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id TAA17391; Sat, 4 Dec 1999 19:56:44 -0800 (PST) Message-Id: <199912050356.TAA17391@lestat.nas.nasa.gov> To: Wilko Bulte Cc: mjacob@feral.com, gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: ISP firmware compiled in as a default.... Reply-To: Jason Thorpe From: Jason Thorpe Date: Sat, 04 Dec 1999 19:56:44 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 4 Dec 1999 22:42:57 +0100 (CET) Wilko Bulte wrote: > Don't shoot me: the right thing to do is to make it possible to boot > FreeBSD/alpha from a CDROM. With or without Qlogic firmware FreeBSD/alpha > is quickly getting too big to be really practical as far as floppy booting > goes. NetBSD can do CDROM booting, but I don't really understand the > issues around CDROM bootability. Having fixed the size problem the extra NetBSD can also boot a kernel split across multiple floppies. Our libsa `ustarfs' is pretty cool: nbftp:thorpej 15$ ls -l total 6256 1456 -rw-r--r-- 1 thorpej netbsd 1474560 Dec 4 19:05 disk1of2 816 -rw-r--r-- 1 thorpej netbsd 819200 Dec 4 19:05 disk2of2 ...that's a NetBSD/alpha install floppy set. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 20:56:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.netbsd.org (redmail.netbsd.org [155.53.200.193]) by hub.freebsd.org (Postfix) with SMTP id 538671538D for ; Sat, 4 Dec 1999 20:56:43 -0800 (PST) (envelope-from cgd@netbsd.org) Received: (qmail 15515 invoked by uid 1000); 5 Dec 1999 04:55:46 -0000 To: mjacob@feral.com Cc: Jason Thorpe , Wilko Bulte , gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: ISP firmware compiled in as a default.... References: From: cgd@netbsd.org (Chris G. Demetriou) Date: 04 Dec 1999 20:55:46 -0800 In-Reply-To: Matthew Jacob's message of Sat, 4 Dec 1999 19:47:18 -0800 (PST) Message-ID: <8766yeasvh.fsf@redmail.netbsd.org> Lines: 27 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > Nope, I don't think so. I pretty much always had been downloading f/w. False. see NetBSD sys/dev/ic/isp.c: revision 1.18 date: 1998/01/28 19:09:24; author: mjacob; state: Exp; lines: +9 -5 Fix for port-alpha/4903- always download f/w unless config flags say no or we have no firmware to download. and/or: http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=4903 > There was a hop skip and dance with some f/w and Chris's machine > [ ... ] yeah: before that patch, you _weren't_ always downloading the firmware, and the DEC ISP firmware didn't work with your isp driver. 8-) cgd -- Chris Demetriou - cgd@netbsd.org - http://www.netbsd.org/People/Pages/cgd.html Disclaimer: Not speaking for NetBSD, just expressing my own opinion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 4 21: 4:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id E4BE8153CF; Sat, 4 Dec 1999 21:04:28 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id VAA18543; Sat, 4 Dec 1999 21:04:17 -0800 (PST) Message-Id: <199912050504.VAA18543@lestat.nas.nasa.gov> To: mjacob@feral.com Cc: Wilko Bulte , gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: ISP firmware compiled in as a default.... Reply-To: Jason Thorpe From: Jason Thorpe Date: Sat, 04 Dec 1999 21:04:16 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 4 Dec 1999 19:47:18 -0800 (PST) Matthew Jacob wrote: > Nope, I don't think so. I pretty much always had been downloading f/w. > There was a hop skip and dance with some f/w and Chris's machine and some > stupid ass bugs in 7.55 f/w where you'd tell it to renegotiate and then > ask it what it had done and it lied and gave back random values. Actually, you used to compare "present firmware rev" with "driver firmware rev" and load the driver firmware if it was "newwer". Version numbering inconsistencies changed that policy... at least is how I remember it. > Nope- the netbsd changes list is too hard to read. Uh, okay, whatever. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message