From owner-freebsd-scsi Sun Jul 27 05:25:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA01069 for freebsd-scsi-outgoing; Sun, 27 Jul 1997 05:25:10 -0700 (PDT) Received: from bsd.fs.bauing.th-darmstadt.de (bsd.fs.bauing.th-darmstadt.de [130.83.63.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA01064 for ; Sun, 27 Jul 1997 05:25:07 -0700 (PDT) Received: from localhost (petzi@localhost) by bsd.fs.bauing.th-darmstadt.de (8.8.6/8.8.5) with SMTP id OAA00950 for ; Sun, 27 Jul 1997 14:25:06 +0200 (MET DST) Date: Sun, 27 Jul 1997 14:25:05 +0200 (MET DST) From: Michael Beckmann X-Sender: petzi@bsd.fs.bauing.th-darmstadt.de To: scsi@freebsd.org Subject: Tagged Command Queuing on ncr Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, how do I turn off tagged command queuing on the ncr driver ? I have two disks that don't seem to like it. I do not want to turn it off on the entire system, which also has an ahc driven controller in it, with tagged command queuing turned on via AHC_TAGENABLE. Can SCSI_NCR_DFLT_TAGS do this ? Thanks, Michael From owner-freebsd-scsi Sun Jul 27 11:11:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA15320 for freebsd-scsi-outgoing; Sun, 27 Jul 1997 11:11:47 -0700 (PDT) Received: from aage.priv.no (birk04.studby.uio.no [129.240.214.13]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA15314 for ; Sun, 27 Jul 1997 11:11:43 -0700 (PDT) Received: (from aagero@localhost) by aage.priv.no (8.8.6/sendmail95) id UAA01564; Sun, 27 Jul 1997 20:11:38 +0200 (CEST) Message-ID: <19970727201137.28093@aage.priv.no> Date: Sun, 27 Jul 1997 20:11:37 +0200 From: =?iso-8859-1?Q?=C5ge_R=F8bekk?= To: freebsd-scsi@freebsd.org Subject: support for sony std-4000 in scsiconf.c Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79e X-OS: FreeBSD 3.0-CURRENT Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone been able to successfully configure a SONY SDT-4000 DAT drive in freebsd? I've edited scsiconf.c over and over to no avail, an mt -t /dev/rst0 status just hangs for 2-3 minutes and then returns with Present Mode: Density = 0x00 Blocksize variable ---------available modes--------- Mode 0: Density = 0x00 Blocksize variable Mode 1: Density = X3B5/88-185A Blocksize variable Mode 2: Density = X3B5/88-185A Blocksize variable Mode 3: Density = X3B5/88-185A Blocksize variable along with a scsi bus reset and lots of timeout errors in the log files. The device probing tells me st0(ahc0:5:0): Sequential-Access density code 0x13, drive empty even if a tape is loaded. Any ideas? -aage From owner-freebsd-scsi Sun Jul 27 11:16:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA15495 for freebsd-scsi-outgoing; Sun, 27 Jul 1997 11:16:24 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA15488 for ; Sun, 27 Jul 1997 11:16:21 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA14369 (5.67b/IDA-1.5 for scsi@FreeBSD.ORG); Sun, 27 Jul 1997 20:16:26 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id QAA01057; Sun, 27 Jul 1997 16:17:19 +0200 (MET DST) From: Wilko Bulte Message-Id: <199707271417.QAA01057@yedi.iaf.nl> Subject: Re: Tagged Command Queuing on ncr To: petzi@apfel.de (Michael Beckmann) Date: Sun, 27 Jul 1997 16:17:19 +0200 (MET DST) Cc: scsi@FreeBSD.ORG In-Reply-To: from "Michael Beckmann" at Jul 27, 97 02:25:05 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Michael Beckmann wrote... > Hello, > > how do I turn off tagged command queuing on the ncr driver ? I have two > disks that don't seem to like it. I do not want to turn it off on the > entire system, which also has an ahc driven controller in it, with > tagged command queuing turned on via AHC_TAGENABLE. Can SCSI_NCR_DFLT_TAGS > do this ? Checkout 'man ncrcontrol' Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-scsi Sun Jul 27 14:38:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA22937 for freebsd-scsi-outgoing; Sun, 27 Jul 1997 14:38:40 -0700 (PDT) Received: from dfw-ix6.ix.netcom.com (dfw-ix6.ix.netcom.com [206.214.98.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA22931; Sun, 27 Jul 1997 14:38:36 -0700 (PDT) Received: (from smap@localhost) by dfw-ix6.ix.netcom.com (8.8.4/8.8.4) id QAA20874; Sun, 27 Jul 1997 16:38:04 -0500 (CDT) Received: from sjx-ca50-19.ix.netcom.com(206.214.103.147) by dfw-ix6.ix.netcom.com via smap (V1.3) id sma020861; Sun Jul 27 16:37:53 1997 Received: (from asami@localhost) by blimp.mimi.com (8.8.6/8.6.9) id OAA02054; Sun, 27 Jul 1997 14:37:51 -0700 (PDT) Date: Sun, 27 Jul 1997 14:37:51 -0700 (PDT) Message-Id: <199707272137.OAA02054@blimp.mimi.com> To: gibbs@freebsd.org CC: scsi@freebsd.org Subject: NOT READY From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Justin (and the rest of the SCSI world), I seem to be getting a lot of the following kind of messages. === sd41(ahc2:9:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Ordered Tag queued sd1(ahc0:1:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Ordered Tag queued sd41(ahc2:9:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd41(ahc2:9:0): Queueing an Abort SCB sd41(ahc2:9:0): Abort Message Sent sd41(ahc2:9:0): SCB 3 - Abort Tag Completed. sd41(ahc2:9:0): no longer in timeout Ordered Tag sent sd41(ahc2:9:0): NOT READY asc:4,2 sd41(ahc2:9:0): Logical unit not ready, initializing command required , retries:3 === The last three lines are repeated as long as the disks are accessed. They don't go away until the machine is rebooted. I remember mentioning this to you a while ago, and you said it's a bad disk -- but we seem to be getting way too many of these to blame individual disks. In the past week, it has happened on 8 out of 112 disks. These are IBM 9GB (DCHS09Y) Ultra-Wide disks connected to 3940UW (20MHz mode disabled, 7 disks per string.) Also, it seems odd to me that a warm boot (i.e., no power cycling of disks) seems to always clear the problem, at least for the time being. Do you think issuing a SCSI bus reset may help? (I think the old ahc driver did this, right?) Another odd thing is that 3 out of the 8 are in the same position (ahc0:2:0). I'm not sure if this means the enclosures are to blame. (Those are on the third position (out of 7) from the left on the top enclosure...not at the edge or anything....) There are a couple of "repeat offenders", but other than those, the problem seems to completely go away after rebooting. Satoshi From owner-freebsd-scsi Mon Jul 28 10:54:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA20906 for freebsd-scsi-outgoing; Mon, 28 Jul 1997 10:54:08 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA20897; Mon, 28 Jul 1997 10:54:01 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-5.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA22209 (5.67b/IDA-1.5); Mon, 28 Jul 1997 19:53:51 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id TAA11232; Mon, 28 Jul 1997 19:53:40 +0200 (CEST) X-Face: " Date: Mon, 28 Jul 1997 19:53:40 +0200 From: Stefan Esser To: Michael Beckmann Cc: scsi@FreeBSD.ORG, Stefan Esser Subject: Re: Tagged Command Queuing on ncr References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Michael Beckmann on Sun, Jul 27, 1997 at 02:25:05PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 27, Michael Beckmann wrote: > Hello, > > how do I turn off tagged command queuing on the ncr driver ? I have two Which version of FreeBSD are you using ? > disks that don't seem to like it. I do not want to turn it off on the > entire system, which also has an ahc driven controller in it, with > tagged command queuing turned on via AHC_TAGENABLE. Can SCSI_NCR_DFLT_TAGS > do this ? You can turn off tags for single drives. This is done differently under 2.x and -current. Look at the example for the HP C3274 and C3275 in /sys/scsi/scsiconf.c in -current, if you use that: { T_DIRECT, T_DIRECT, T_FIXED, "HP", "C372*", "*", "sd", SC_ONE_LU, SD_Q_NO_TAGS }, In 2.x look for a line reading: ncr_setmaxtags (tp, SCSI_NCR_DFLT_TAGS); and change the second parameter to 0. You can then set the number of tags from a startup file for all drives that support tagged commands. Assuming that target 1 and 2 don't support tags, but the rest of your targets does, you want to execute the following command: # ncrcontrol -t0 -t3 -t4 -t5 -t6 -s tags=4 for the default of 4 tags per drive. (This assumes disk drives on all targets, and 7 as the host adapter ID.) Regards, STefan From owner-freebsd-scsi Mon Jul 28 13:13:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA29408 for freebsd-scsi-outgoing; Mon, 28 Jul 1997 13:13:14 -0700 (PDT) Received: from mail.nacamar.de (mail.nacamar.de [194.162.162.200]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA29396; Mon, 28 Jul 1997 13:13:04 -0700 (PDT) Received: from [195.52.251.6] (apfel.nacamar.de [195.52.251.6]) by mail.nacamar.de (8.8.6/8.8.6) with ESMTP id WAA26411; Mon, 28 Jul 1997 22:12:54 +0200 (CEST) X-Sender: petzi@mail.apfel.de Message-Id: In-Reply-To: <19970728195340.09850@mi.uni-koeln.de> References: ; from Michael Beckmann on Sun, Jul 27, 1997 at 02:25:05PM +0200 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 28 Jul 1997 22:13:23 +0200 To: Stefan Esser From: Michael Beckmann Subject: Re: Tagged Command Queuing on ncr Cc: scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 19:53 Uhr +0200 28.07.1997, Stefan Esser wrote: >> how do I turn off tagged command queuing on the ncr driver ? I have two > >Which version of FreeBSD are you using ? 2.2-RELENG ># ncrcontrol -t0 -t3 -t4 -t5 -t6 -s tags=4 Thanks. I have five disks in the machine; the two evil disks on one ncr controller (Asus SC-200), and three other disks on an Adaptec 2940, which I use because my Tyan Tomcat III mainboard didn't have an NCR BIOS and I didn't find an NCR controller with BIOS in the stores at that time :-% Michael From owner-freebsd-scsi Mon Jul 28 13:27:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA00336 for freebsd-scsi-outgoing; Mon, 28 Jul 1997 13:27:21 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA00328; Mon, 28 Jul 1997 13:27:12 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-5.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA15519 (5.67b/IDA-1.5); Mon, 28 Jul 1997 22:27:01 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id WAA11866; Mon, 28 Jul 1997 22:26:50 +0200 (CEST) X-Face: " Date: Mon, 28 Jul 1997 22:26:49 +0200 From: Stefan Esser To: Michael Beckmann Cc: scsi@FreeBSD.ORG, Stefan Esser Subject: Re: Tagged Command Queuing on ncr References: ; Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Michael Beckmann on Mon, Jul 28, 1997 at 10:13:23PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 28, Michael Beckmann wrote: > I have five disks in the machine; the two evil disks on one ncr controller > (Asus SC-200), and three other disks on an Adaptec 2940, which I use > because my Tyan Tomcat III mainboard didn't have an NCR BIOS and I didn't > find an NCR controller with BIOS in the stores at that time :-% Could you please send me a boot message log and explain, what happens with tags enabled ? I could take precautions in -current, then ... Regards, STefan From owner-freebsd-scsi Mon Jul 28 14:19:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA03700 for freebsd-scsi-outgoing; Mon, 28 Jul 1997 14:19:15 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA03695 for ; Mon, 28 Jul 1997 14:19:13 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id OAA09118 for ; Mon, 28 Jul 1997 14:18:37 -0700 (PDT) Date: Mon, 28 Jul 1997 14:18:37 -0700 (PDT) From: Jaye Mathisen To: scsi@freebsd.org Subject: DPT crashes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just died with 2.2.2 with DPT: Undocumented error" during a CVSUP of the world from my local cvsup mirror. From owner-freebsd-scsi Tue Jul 29 02:21:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA27353 for freebsd-scsi-outgoing; Tue, 29 Jul 1997 02:21:36 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA27348 for ; Tue, 29 Jul 1997 02:21:31 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA09703; Tue, 29 Jul 1997 11:21:29 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id LAA04712; Tue, 29 Jul 1997 11:13:28 +0200 (MET DST) Message-ID: <19970729111328.HZ47422@uriah.heep.sax.de> Date: Tue, 29 Jul 1997 11:13:28 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Cc: jaykuri@oneway.com (Jay Kuri) Subject: Re: help: wiring down scsi devices doesn't work References: <199707221118.HAA06466@hda.hda.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Jay Kuri on Jul 24, 1997 09:13:27 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jay Kuri wrote: > Gotcha... I was under the impression that the scanner was reporting > itself as a processor (and this is what the docs for the driver said it > would do) but it was really reporting itself as a type 6 (scanner... > imagine that :) Btw., if you want to override the assignment of some particular device, invent a new entry in /sys/scsi/scsiconf.c. Normally, the first couple of fields in each record there is identical, meaning a device of a particular `type' gets assigned to the `type driver' that it is intended for. However, you can assign it to a different driver as well; see the SONY SMO drive for one example that comes to mind (it is so old that it only reports itself as being `direct access', while it is actually `optical'). > I thought that processor target and unknown target had some different > functionality... It appears that I am wrong in that. ISTR that processor targets support read and write syscalls, while uk(4) don't. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Tue Jul 29 06:58:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA14360 for freebsd-scsi-outgoing; Tue, 29 Jul 1997 06:58:00 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA14354 for ; Tue, 29 Jul 1997 06:57:54 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.8.6/8.8.6) id IAA09998; Tue, 29 Jul 1997 08:57:31 -0500 (CDT) Message-ID: <19970729085731.33825@pmr.com> Date: Tue, 29 Jul 1997 08:57:31 -0500 From: Bob Willcox To: Tom Samplonius Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: DPT driver integration? Reply-To: Bob Willcox References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79 In-Reply-To: ; from Tom Samplonius on Sun, Jul 20, 1997 at 11:38:10PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Jul 20, 1997 at 11:38:10PM -0700, Tom Samplonius wrote: > > When is the DPT driver likely to be integrated into current, and later > into 2.2.2? > > I wish I could try it, but my 3334UW doesn't seem to be able to save its > array configuration (every time I run dptmgr, it says I have to do an > initial setup, even though I've done it a dozen times). DPT claims it is > probably a cabling problem, which sounds phony to me, as isn't the array > configuration stored in NVRAM on the card? No, the array configuration is stored on the disks (all of them that participate in the array, as I recall). The card reads this info from the disks to determine the configuration. -- Bob Willcox Deliberation, n.: The act of examining one's bread bob@luke.pmr.com to determine which side it is buttered on. Austin, TX -- Ambrose Bierce, "The Devil's Dictionary" From owner-freebsd-scsi Tue Jul 29 07:57:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA18879 for freebsd-scsi-outgoing; Tue, 29 Jul 1997 07:57:25 -0700 (PDT) Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA18870 for ; Tue, 29 Jul 1997 07:57:21 -0700 (PDT) Received: from mail.kcwc.com by relay1.UU.NET with SMTP (peer crosschecked as: h1.kcwc.com [206.139.252.2]) id QQdahn13568; Tue, 29 Jul 1997 10:56:24 -0400 (EDT) Received: by mail.kcwc.com (NX5.67c/NeXT-2.0-KCWC-1.0) id AA02698; Tue, 29 Jul 97 10:56:24 -0400 Date: Tue, 29 Jul 97 10:56:24 -0400 From: curt@kcwc.com (Curt Welch) Message-Id: <9707291456.AA02698@mail.kcwc.com> To: freebsd-scsi@FreeBSD.ORG Subject: Re: DPT driver integration? Cc: curt@kcwc.com Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Jul 20, 1997 at 11:38:10PM -0700, Tom Samplonius wrote: > > When is the DPT driver likely to be integrated into current, and later > into 2.2.2? > > I wish I could try it, but my 3334UW doesn't seem to be able to save its > array configuration (every time I run dptmgr, it says I have to do an > initial setup, even though I've done it a dozen times). Are you perhaps using the save option instead of the set option? I haven't tried the save option but it looks like something that would save the config to a file on a local system instead of saving it to the drives. Just a guess. Curt From owner-freebsd-scsi Tue Jul 29 09:22:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA26228 for freebsd-scsi-outgoing; Tue, 29 Jul 1997 09:22:56 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA26223 for ; Tue, 29 Jul 1997 09:22:50 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtF2s-0007ID-00; Tue, 29 Jul 1997 09:22:46 -0700 Date: Tue, 29 Jul 1997 09:22:46 -0700 (PDT) From: Tom Samplonius To: Bob Willcox cc: freebsd-scsi@freebsd.org Subject: Re: DPT driver integration? In-Reply-To: <19970729085731.33825@pmr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 29 Jul 1997, Bob Willcox wrote: > On Sun, Jul 20, 1997 at 11:38:10PM -0700, Tom Samplonius wrote: > > > > When is the DPT driver likely to be integrated into current, and later > > into 2.2.2? > > > > I wish I could try it, but my 3334UW doesn't seem to be able to save its > > array configuration (every time I run dptmgr, it says I have to do an > > initial setup, even though I've done it a dozen times). DPT claims it is > > probably a cabling problem, which sounds phony to me, as isn't the array > > configuration stored in NVRAM on the card? > > No, the array configuration is stored on the disks (all of them > that participate in the array, as I recall). The card reads this > info from the disks to determine the configuration. It turns out my DPT 3334UW was DOA. I sent it back, and got a new one. It works perfectly, so far. > -- > Bob Willcox Deliberation, n.: The act of examining one's bread > bob@luke.pmr.com to determine which side it is buttered on. > Austin, TX -- Ambrose Bierce, "The Devil's Dictionary" > > Tom From owner-freebsd-scsi Tue Jul 29 09:28:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA26601 for freebsd-scsi-outgoing; Tue, 29 Jul 1997 09:28:22 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA26596 for ; Tue, 29 Jul 1997 09:28:18 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtF85-0007Ie-00; Tue, 29 Jul 1997 09:28:09 -0700 Date: Tue, 29 Jul 1997 09:28:08 -0700 (PDT) From: Tom Samplonius To: Curt Welch cc: freebsd-scsi@freebsd.org Subject: Re: DPT driver integration? In-Reply-To: <9707291456.AA02698@mail.kcwc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 29 Jul 1997, Curt Welch wrote: > On Sun, Jul 20, 1997 at 11:38:10PM -0700, Tom Samplonius wrote: > > > > When is the DPT driver likely to be integrated into current, and later > > into 2.2.2? > > > > I wish I could try it, but my 3334UW doesn't seem to be able to save its > > array configuration (every time I run dptmgr, it says I have to do an > > initial setup, even though I've done it a dozen times). > > Are you perhaps using the save option instead of the set option? > > I haven't tried the save option but it looks like something that would > save the config to a file on a local system instead of saving it > to the drives. > > Just a guess. > > Curt No, the card was DOA. It wouldn't save the config, ever. DPT RMAed it, and shipped us a new card. Tom From owner-freebsd-scsi Tue Jul 29 13:57:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA12626 for freebsd-scsi-outgoing; Tue, 29 Jul 1997 13:57:33 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA12617 for ; Tue, 29 Jul 1997 13:57:21 -0700 (PDT) Received: (qmail 7775 invoked by uid 1000); 29 Jul 1997 20:57:29 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 29 Jul 1997 13:57:29 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Jaye Mathisen Subject: RE: DPT crashes Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Jaye Mathisen; On 28-Jul-97 you wrote: > > > Just died with 2.2.2 with DPT: Undocumented error" during a CVSUP > of the world from my local cvsup mirror. Nurse: Dr. The patient is sick. Dr.: Give him two aspirins and call me in the morning. Lawyer: Good! Undocumented error is exactly that. An error which i do not know what it is. i could guess all day long but would prefer more data :-) Simon From owner-freebsd-scsi Tue Jul 29 16:50:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22283 for freebsd-scsi-outgoing; Tue, 29 Jul 1997 16:50:56 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22277 for ; Tue, 29 Jul 1997 16:50:53 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id QAA11930; Tue, 29 Jul 1997 16:50:49 -0700 (PDT) Date: Tue, 29 Jul 1997 16:50:49 -0700 (PDT) From: Jaye Mathisen To: Simon Shapiro cc: scsi@FreeBSD.ORG Subject: RE: DPT crashes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk So tell me what you need? Not much I can tell you. The system was idle, except for a CVSup of -current. In the middle of the cvsup, it just stopped, with that error message, and was sitting in ddb>. I tried panic for grins, and it said "syncing disks", but never saw any disk activity. Waited several minutes, rebooted, and it came up. BTW, the -current patch in /crash doesn't seem to apply to a real -current, or at least, it won't on mine, while the 2.2.2 patch applies fine. On Tue, 29 Jul 1997, Simon Shapiro wrote: > > Hi Jaye Mathisen; On 28-Jul-97 you wrote: > > > > > > Just died with 2.2.2 with DPT: Undocumented error" during a CVSUP > > of the world from my local cvsup mirror. > > Nurse: Dr. The patient is sick. > Dr.: Give him two aspirins and call me in the morning. > Lawyer: Good! > > Undocumented error is exactly that. An error which i do not know what it > is. i could guess all day long but would prefer more data :-) > > Simon > From owner-freebsd-scsi Tue Jul 29 17:09:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA23340 for freebsd-scsi-outgoing; Tue, 29 Jul 1997 17:09:56 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA23335 for ; Tue, 29 Jul 1997 17:09:53 -0700 (PDT) Received: (qmail 5502 invoked by uid 1000); 30 Jul 1997 00:09:58 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 29 Jul 1997 17:09:58 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Jaye Mathisen Subject: RE: DPT crashes Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Jaye Mathisen; On 29-Jul-97 you wrote: > > So tell me what you need? Not much I can tell you. The system was idle, > except for a CVSup of -current. > > In the middle of the cvsup, it just stopped, with that error message, and > was sitting in ddb>. > > I tried panic for grins, and it said "syncing disks", but never saw any > disk activity. I need to see things like the DPT options you configured the kernel with, firmware level, controller model, RAID configuration, motherboard type, slot number in the machine, did you manage to re-boot the machine? did it happen again? Versipon of the driver, etc. The error message you report is a catchall at the end of the case statement. IOW, something we really know nothing about. If it happens regularly, you may want to activate few options in the kernel, to see if we can catch the error in a better defined light. > Waited several minutes, rebooted, and it came up. > > > BTW, the -current patch in /crash doesn't seem to apply to a real > -current, or at least, it won't on mine, while the 2.2.2 patch applies > fine. By definition, -current is a moving target. We make no particular effort here to track it with patches. Once we put the driver in the kernel, we will be obliged to update it. The mechanisms to do so are in place. 2.2 is a ``stable'' release and API's are not supposed to change. Another reason for the -current ``neglect'' is that we anticipate a major re-write of the SCSI layer in 3.0, and with it a major work on the DPT driver. We simply do not have time to track all three threads. > > On Tue, 29 Jul 1997, Simon Shapiro wrote: > > > > > Hi Jaye Mathisen; On 28-Jul-97 you wrote: > > > > > > > > > Just died with 2.2.2 with DPT: Undocumented error" during a CVSUP > > > of the world from my local cvsup mirror. > > > > Nurse: Dr. The patient is sick. > > Dr.: Give him two aspirins and call me in the morning. > > Lawyer: Good! > > > > Undocumented error is exactly that. An error which i do not know what > it > > is. i could guess all day long but would prefer more data :-) > > > > Simon > > > From owner-freebsd-scsi Tue Jul 29 17:26:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA24270 for freebsd-scsi-outgoing; Tue, 29 Jul 1997 17:26:29 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA24264 for ; Tue, 29 Jul 1997 17:26:27 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id RAA18411; Tue, 29 Jul 1997 17:26:21 -0700 (PDT) Date: Tue, 29 Jul 1997 17:26:21 -0700 (PDT) From: Jaye Mathisen To: Simon Shapiro cc: scsi@FreeBSD.ORG Subject: RE: DPT crashes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 29 Jul 1997, Simon Shapiro wrote: > > I need to see things like the DPT options you configured the kernel with, > firmware level, controller model, RAID configuration, motherboard type, > slot number in the machine, did you manage to re-boot the machine? > did it happen again? Versipon of the driver, etc. I'm using the DPT kernel config file that came with the patch. Controller is a PM3334UW, connected to 3 4GB Barracuda's, running RAID-5. Motherboard is a Digital Prioris HX6000 (intel if I recall), it's in slot 1 of the primary PCI bus. The firmware is dated March 1997, I think it's 07L0. The system reboots fine. I'm using 2.2.2 with the 1.10 patch. It just happened again, which is interesting, because I can sup -current just fine, but it crashes so far each time I cvsup 2.2.2... Can't imagine there's a correlation, but it's interesting. > > The error message you report is a catchall at the end of the case statement. > IOW, something we really know nothing about. > > If it happens regularly, you may want to activate few options in the > kernel, to see if we can catch the error in a better defined light. > > > Waited several minutes, rebooted, and it came up. > > > > > > BTW, the -current patch in /crash doesn't seem to apply to a real > > -current, or at least, it won't on mine, while the 2.2.2 patch applies > > fine. > > By definition, -current is a moving target. We make no particular effort > here to track it with patches. Once we put the driver in the kernel, we > will be obliged to update it. The mechanisms to do so are in place. > 2.2 is a ``stable'' release and API's are not supposed to change. > Another reason for the -current ``neglect'' is that we anticipate a major > re-write of the SCSI layer in 3.0, and with it a major work on the DPT > driver. We simply do not have time to track all three threads. > > > > > On Tue, 29 Jul 1997, Simon Shapiro wrote: > > > > > > > > Hi Jaye Mathisen; On 28-Jul-97 you wrote: > > > > > > > > > > > > Just died with 2.2.2 with DPT: Undocumented error" during a CVSUP > > > > of the world from my local cvsup mirror. > > > > > > Nurse: Dr. The patient is sick. > > > Dr.: Give him two aspirins and call me in the morning. > > > Lawyer: Good! > > > > > > Undocumented error is exactly that. An error which i do not know what > > it > > > is. i could guess all day long but would prefer more data :-) > > > > > > Simon > > > > > > From owner-freebsd-scsi Tue Jul 29 21:10:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA05707 for freebsd-scsi-outgoing; Tue, 29 Jul 1997 21:10:00 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA05696 for ; Tue, 29 Jul 1997 21:09:55 -0700 (PDT) Received: (qmail 7753 invoked by uid 1000); 30 Jul 1997 04:10:09 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 29 Jul 1997 21:10:09 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Jaye Mathisen Subject: RE: DPT crashes Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Jaye Mathisen; On 30-Jul-97 you wrote: ... > I'm using the DPT kernel config file that came with the patch. > Controller > is a PM3334UW, connected to 3 4GB Barracuda's, running RAID-5. > > Motherboard is a Digital Prioris HX6000 (intel if I recall), it's in slot > 1 of the primary PCI bus. The firmware is dated March 1997, I think it's > 07L0. The system reboots fine. I'm using 2.2.2 with the 1.10 patch. Thanx! Sounds normal to me... > > It just happened again, which is interesting, because I can sup -current > just fine, but it crashes so far each time I cvsup 2.2.2... Can't > imagine > there's a correlation, but it's interesting. CVSup is doing networking while disking... i use the same arrangement here, without ever seing this error message. This is not trivial then... ... Enable (#define) DPT_DEBUG_COMPLETION_ERRORS in sys/dev/dpt.h. It will spit lots of messages, especially at boot time, but next time it happens, you should have something along the lines of "dpt%d: Undocumented Error %x...". Let me see the whole thing. BTW, the driver should drop into the debugger if you get this error. Just type ``c'' to ``continue'' and it should continue. In the next release, I will make it actually abort the SCSI command and re-try it, without the debugger (which is bad news if you are in X11). Simon From owner-freebsd-scsi Tue Jul 29 23:56:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA14011 for freebsd-scsi-outgoing; Tue, 29 Jul 1997 23:56:25 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA13986; Tue, 29 Jul 1997 23:55:59 -0700 (PDT) Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id QAA00650; Wed, 30 Jul 1997 16:25:50 +0930 (CST) From: grog@FreeBSD.ORG Message-Id: <199707300655.QAA00650@freebie.lemis.com> Subject: Re: SCSI 1542 error In-Reply-To: from Tom Samplonius at "Jul 29, 97 11:15:30 pm" To: tom@sdf.com (Tom Samplonius) Date: Wed, 30 Jul 1997 16:25:50 +0930 (CST) Cc: nate@mt.sri.com, nelson@pangeia.com.br, hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Follow-up-to: scsi@freebsd.org Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius writes: > > On Tue, 29 Jul 1997, Nate Williams wrote: > >>> I'm have a problem with maybe more well know board. >>> >>> One hour after install FreeBSD 2.2.2 on 486, with 32Mb and SCSI 1542C, >>> my console say: >> >> You're not the first. It appears to me from watching the mailing list >> that the 1542 boards are not supported in 2.2. *Many* people have >> reported problems with them, which unfortunately means that I can no >> longer do 2.2 development at home. :( > > It just appears that bounce buffers are broken. I think I'd go along with that. I recently upgraded from a version of 3.0-current just before Christmas last year to the latest version. Since then, without changing the configuration file, I'm getting lots of these messages: Jul 30 13:36:31 freebie /kernel: aha0: DMA beyond end Of ISA: 0x3183d14 Jul 30 13:36:32 freebie /kernel: aha0: DMA beyond end Of ISA: 0x3354d14 Jul 30 13:47:48 freebie /kernel: aha0: DMA beyond end Of ISA: 0x3394d14 Jul 30 13:47:50 freebie /kernel: aha0: DMA beyond end Of ISA: 0x31bfd14 Of course I have BOUNCE_BUFFERS set in the config file. In addition, lots of spurious error messages are caused by my Archive DDS changer. It got so bad (for some reason the driver wasn't able to read or write the tape) that I had to hang it on the 2940 which I usually reserve for disks (where it works perfectly). I'm copying this to -scsi, since it really beloings there. Greg From owner-freebsd-scsi Wed Jul 30 00:00:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA14303 for freebsd-scsi-outgoing; Wed, 30 Jul 1997 00:00:12 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA14272; Wed, 30 Jul 1997 00:00:03 -0700 (PDT) Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id QAA00658; Wed, 30 Jul 1997 16:29:31 +0930 (CST) From: grog@FreeBSD.ORG Message-Id: <199707300659.QAA00658@freebie.lemis.com> Subject: Re: can't get panic dump In-Reply-To: <5rmm46$1b5@twwells.com> from "T. William Wells" at "Jul 30, 97 02:15:31 am" To: bill@twwells.com (T. William Wells) Date: Wed, 30 Jul 1997 16:29:31 +0930 (CST) Cc: questions@FreeBSD.ORG (FreeBSD Questions), scsi@FreeBSD.ORG Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk T. William Wells writes: > I'm running 2.2.2-RELEASE. I have 32M of RAM. I have bounce > buffers in my config. The SCSI controller is an Adaptec 1540. It > dumps 16M and then at the 16M boundary complains about DMA beyond > end of ISA and stops dumping. Any ideas? I think you've hit a bug. > Config and boot messages appended (from a run with 16M, where I > can get a complete dump). > > machine "i386" > cpu "I486_CPU" > ident TWWELLS > maxusers 16 > config kernel root on sd0 > > options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] > options BOUNCE_BUFFERS This is the option that *should* prevent the "DMA beyond end of ISA" message. But I'm getting it too. One minor nit: obviously you are running beyond the 16 MB boundary. But your dmesg output shows only 16 MB. I'm guessing that you've disabled the other half in order to get the machine to run. Is there anything else in the dmesg output which is less obvious? I'm forwarding this to the SCSI mailing list, where I just sent a similar message describing my own problems. If there's anybody else out there on -questions who are having this problem, please let us know. Greg > options UCONSOLE #Allow users to grab the console > options SYSVSHM > options SYSVSEM > options SYSVMSG > > options INET #InterNETworking > options IPFIREWALL #firewall > options IPDIVERT #divert sockets > > options FFS #Fast filesystem > options "CD9660" #ISO 9660 filesystem > options PROCFS #Process filesystem > > options DDB > options DDB_UNATTENDED > options KTRACE #kernel tracing > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > options MAXCONS=16 # number of virtual consoles > options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device > options CHILD_MAX=128 > > controller isa0 > device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr > device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr > device pca0 at isa? port IO_TIMER1 tty > > device lpt0 at isa? port? tty irq 7 vector lptintr > device sio0 at isa? port 0x3F8 tty irq 4 vector siointr > device sio1 at isa? port 0x2F8 tty irq 3 vector siointr > device sio2 at isa? port 0x3E8 tty irq 9 vector siointr > device sio3 at isa? port 0x2E8 tty irq 5 vector siointr > device ed0 at isa? port 0x220 net irq 15 iomem 0xd8000 vector edintr > device mcd0 at isa? port 0x300 bio irq 10 drq 6 vector mcdintr > > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr > disk fd0 at fdc0 drive 0 > disk fd1 at fdc0 drive 1 > > controller scbus0 #base SCSI code > device sd0 #SCSI disks > device st0 #SCSI tapes > > controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr > > pseudo-device ether #Generic Ethernet > pseudo-device loop #Network loopback device > pseudo-device bpfilter 4 #Berkeley packet filter > pseudo-device disc #Discard device > pseudo-device tun 4 #Tunnel driver (user process ppp) > > pseudo-device pty 64 #Pseudo ttys - can go as high as 256 > pseudo-device speaker #Play IBM BASIC-style noises out your speaker > pseudo-device log #Kernel syslog interface (/dev/klog) > pseudo-device gzip #Exec gzipped a.out's > pseudo-device vn #Vnode driver (turns a file into a device) > pseudo-device snp 4 #Snoop device - to look at pty/vty/etc.. > > FreeBSD 2.2.2-RELEASE #0: Fri Jun 27 13:29:01 EDT 1997 > root@twwells.com:/usr/src/sys/compile/TWWELLS > CPU: i486DX (486-class CPU) > real memory = 16777216 (16384K bytes) > avail memory = 14819328 (14472K bytes) > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > ed0 at 0x220-0x23f irq 15 on isa > ed0: address 00:50:4e:03:9d:8f, type NE2000 (16 bit) > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16450 > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16450 > sio2 at 0x3e8-0x3ef irq 9 on isa > sio2: type 16550A > sio3 at 0x2e8-0x2ef irq 5 on isa > sio3: type 16550A > pca0 on motherboard > pca0: PC speaker audio driver > mcd0: type Mitsumi FX001D, version info: D 2 > mcd0 at 0x300-0x303 irq 10 drq 6 on isa > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: NEC 765 > fd0: 1.44MB 3.5in > fd1: 1.2MB 5.25in > aha0 at 0x330-0x333 irq 11 drq 5 on isa > aha0 waiting for scsi devices to settle > (aha0:0:0): "QUANTUM FIREBALL_TM2110S 300X" type 0 fixed SCSI 2 > sd0(aha0:0:0): Direct-Access 2014MB (4124736 512 byte sectors) > (aha0:1:0): "CONNER CP30540 545MB3.5 B0BD" type 0 fixed SCSI 2 > sd1(aha0:1:0): Direct-Access 520MB (1065912 512 byte sectors) > npx0 on motherboard > npx0: INT 16 interface > IP packet filtering initialized, divert enabled, logging disabled From owner-freebsd-scsi Wed Jul 30 00:15:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA15139 for freebsd-scsi-outgoing; Wed, 30 Jul 1997 00:15:48 -0700 (PDT) Received: from admin.cyberenet.net (mail@admin.cyberenet.net [204.213.252.6]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA15118; Wed, 30 Jul 1997 00:15:38 -0700 (PDT) Received: from twwells.com [199.79.159.1] (mail) by admin.cyberenet.net with smtp (Exim 1.62 #4) id 0wtSyu-0007I8-00; Wed, 30 Jul 1997 03:15:37 -0400 Received: from bill by twwells.com with local (Exim 1.62 #3) id 0wtSyr-0000wd-00; Wed, 30 Jul 1997 03:15:33 -0400 Subject: Re: can't get panic dump To: grog@freebsd.org Date: Wed, 30 Jul 1997 03:15:33 -0400 (EDT) Cc: questions@freebsd.org, scsi@freebsd.org In-Reply-To: <199707300659.QAA00658@freebie.lemis.com> from "grog@FreeBSD.ORG" at Jul 30, 97 04:29:31 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Message-Id: From: "T. William Wells" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Config and boot messages appended (from a run with 16M, where I ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > can get a complete dump). ^^^^^^^^^^^^^^^^^^^^^^^^ > One minor nit: obviously you are running beyond the 16 MB boundary. > But your dmesg output shows only 16 MB. I'm guessing that you've > disabled the other half in order to get the machine to run. Is there > anything else in the dmesg output which is less obvious? No. BTW, I *need* to run with more than 16M if I'm going to have debugging symbols in my kernel.... From owner-freebsd-scsi Wed Jul 30 05:02:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA26469 for freebsd-scsi-outgoing; Wed, 30 Jul 1997 05:02:53 -0700 (PDT) Received: from shell.monmouth.com (root@shell.monmouth.com [205.164.220.9]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA26460; Wed, 30 Jul 1997 05:02:47 -0700 (PDT) Received: from i4got.lakewood.com (fh-ppp12.monmouth.com [205.164.221.44]) by shell.monmouth.com (8.8.5/8.7.3) with ESMTP id IAA26213; Wed, 30 Jul 1997 08:00:31 -0400 (EDT) Received: (from pechter@localhost) by i4got.lakewood.com id IAA15575 (8.8.5/IDA-1.6); Wed, 30 Jul 1997 08:02:41 -0400 (EDT) From: Bill Pechter Message-ID: <199707301202.IAA15575@i4got.lakewood.com> Subject: Re: SCSI 1542 error To: grog@FreeBSD.ORG Date: Wed, 30 Jul 1997 08:02:41 -0400 (EDT) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707300655.QAA00650@freebie.lemis.com> from "grog@FreeBSD.ORG" at "Jul 30, 97 04:25:50 pm" Reply-to: pechter@lakewood.com X-Phone-Number: 908-389-3592 X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Tom Samplonius writes: > > > > On Tue, 29 Jul 1997, Nate Williams wrote: > > > Jul 30 13:47:50 freebie /kernel: aha0: DMA beyond end Of ISA: 0x31bfd14 > > Of course I have BOUNCE_BUFFERS set in the config file. > > In addition, lots of spurious error messages are caused by my Archive > DDS changer. It got so bad (for some reason the driver wasn't able to > read or write the tape) that I had to hang it on the 2940 which I > usually reserve for disks (where it works perfectly). > > I'm copying this to -scsi, since it really beloings there. > > Greg > BTW -- the ch device doesn't use bounce buffers at all (unfortunately)... I've got the same problem with 2.2.2... I don't see any bounce problems in 2.2.2 except with the archive changer. Bill ------------------------------------------------------------------------------ Bill Pechter | 17 Meredith Drive Tinton Falls, NJ 07724 | 908-389-3592 pechter@lakewood.com | Save computing history, give an old geek old hardware. This msg brought to you by the letters PDP and the number 11. From owner-freebsd-scsi Wed Jul 30 11:28:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA22439 for freebsd-scsi-outgoing; Wed, 30 Jul 1997 11:28:35 -0700 (PDT) Received: from pluto.plutotech.com (root@[206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA22417; Wed, 30 Jul 1997 11:28:15 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id MAA17071; Wed, 30 Jul 1997 12:27:04 -0600 (MDT) Message-Id: <199707301827.MAA17071@pluto.plutotech.com> To: asami@cs.berkeley.edu (Satoshi Asami) cc: gibbs@freebsd.org, scsi@freebsd.org Subject: Re: NOT READY In-reply-to: Your message of "Sun, 27 Jul 1997 14:37:51 PDT." <199707272137.OAA02054@blimp.mimi.com> Date: Wed, 30 Jul 1997 12:27:04 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >sd41(ahc2:9:0): NOT READY asc:4,2 >sd41(ahc2:9:0): Logical unit not ready, initializing command required >, retries:3 >=== The drive has spun down and wants you to send it a start unit before it will play nice again. The current SCSI code doesn't snoop this asc,ascq pair and attempt to start the drive up again which is the problem with the recovery attempt. I twould not be easy for me to do anythine at the aic7xxx driver level to address this cleanly unless you can provide a trace that shows what the aic7xxx driver might be doing to cause the drive to spin down. You could try adding in a start unit in the sense handler for the sd driver and see if it clears up your problem. >Also, it seems odd to me that a warm boot (i.e., no power cycling of >disks) seems to always clear the problem, at least for the time being. >Do you think issuing a SCSI bus reset may help? (I think the old ahc >driver did this, right?) The sd driver will perform a start unit (unconditionally) when the device is opened. This will cause the drive to spin up and everything will go back to normal. >Another odd thing is that 3 out of the 8 are in the same position >(ahc0:2:0). I'm not sure if this means the enclosures are to blame. >(Those are on the third position (out of 7) from the left on the top >enclosure...not at the edge or anything....) There are a couple of >"repeat offenders", but other than those, the problem seems to >completely go away after rebooting. It wouldn't surprise me at all if this were a thermal problem. Stick a temperature sensor in the enclosure (on the drive itself) and rule this out. >Satoshi -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Wed Jul 30 18:32:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA20760 for freebsd-scsi-outgoing; Wed, 30 Jul 1997 18:32:31 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA20754 for ; Wed, 30 Jul 1997 18:32:24 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id LAA24944; Thu, 31 Jul 1997 11:02:13 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id LAA18397; Thu, 31 Jul 1997 11:02:00 +0930 (CST) Message-Id: <199707310132.LAA18397@freebie.lemis.com> Subject: Re: SCSI 1542 error In-Reply-To: <199707301202.IAA15575@i4got.lakewood.com> from Bill Pechter at "Jul 30, 97 08:02:41 am" To: pechter@lakewood.com Date: Thu, 31 Jul 1997 11:02:00 +0930 (CST) Cc: freebsd-scsi@freebsd.org (FreeBSD SCSI Mailing List) Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bill Pechter writes: >> Tom Samplonius writes: >>> >>> On Tue, 29 Jul 1997, Nate Williams wrote: >>> >> Jul 30 13:47:50 freebie /kernel: aha0: DMA beyond end Of ISA: 0x31bfd14 >> >> Of course I have BOUNCE_BUFFERS set in the config file. >> >> In addition, lots of spurious error messages are caused by my Archive >> DDS changer. It got so bad (for some reason the driver wasn't able to >> read or write the tape) that I had to hang it on the 2940 which I >> usually reserve for disks (where it works perfectly). > > BTW -- the ch device doesn't use bounce buffers at all (unfortunately)... > I've got the same problem with 2.2.2... I'm not using the ch device here. Or at least, I don't think I am. I'm treating the changer as a normal DDS drive. > I don't see any bounce problems in 2.2.2 except with the archive > changer. Since I moved it to the 2940, I haven't been seeing any problems either. But I have seen others. I'll try to report when I can get all the info together. Greg From owner-freebsd-scsi Wed Jul 30 22:11:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA03838 for freebsd-scsi-outgoing; Wed, 30 Jul 1997 22:11:12 -0700 (PDT) Received: from daemonweed.reanimators.org (fmc@daemonweed.reanimators.org [198.137.202.50]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA03833; Wed, 30 Jul 1997 22:11:03 -0700 (PDT) Received: (from fmc@localhost) by daemonweed.reanimators.org (8.8.5/8.8.5) id WAA15704; Wed, 30 Jul 1997 22:10:56 -0700 (PDT) Message-Id: <199707310510.WAA15704@daemonweed.reanimators.org> To: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI 1542 error References: <199707301202.IAA15575@i4got.lakewood.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Frank McConnell Date: 30 Jul 1997 22:10:55 -0700 In-Reply-To: Bill Pechter's message of Wed, 30 Jul 1997 08:02:41 -0400 (EDT) Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bill Pechter writes: > BTW -- the ch device doesn't use bounce buffers at all (unfortunately)... > I've got the same problem with 2.2.2... I noticed this the other day (similar config, 2.2.1, ISA bus, 1542CP? with Archive changer) and have come up with what I think is a fix. Diffs below. But first, some notes: (a) I am running FreeBSD 2.2.1-RELEASE, not 2.2.2. I have no idea how much the ch driver has changed in that span. (b) This corrects the malloc()s of data buffers in ch_usergetelemstatus() so that bounce buffers may be used instead. (c) Still questionable to me is the use of a stack temporary (sense_data) in ch_get_params() as a data buffer. It seems to work but I don't understand why, probably because I don't quite understand how what happens down below happens. Should it be changed too? (d) From (c), I probably have no business monkeying with this sort of thing, and someone who knows more ought to look this over. It lets me do chio status in addition to chio move, but that's as far as I've tested it. Criticism is welcome. -Frank McConnell, maybe-wannabe-freebsd-hacker --- cut here --- *** ch.c.2.2.1-RELEASE Fri Mar 7 01:34:26 1997 --- ch.c Tue Jul 29 21:30:42 1997 *************** *** 36,41 **** --- 36,42 ---- * $Id: ch.c,v 1.34.2.1 1997/03/07 09:34:26 joerg Exp $ */ + #include "opt_bounce.h" #include "opt_scsi.h" #include *************** *** 511,517 **** struct read_element_status_page_header *pg_hdr; struct read_element_status_descriptor *desc; caddr_t data = NULL; ! size_t size, desclen; int avail, i, error = 0; u_int8_t *user_data = NULL; --- 512,518 ---- struct read_element_status_page_header *pg_hdr; struct read_element_status_descriptor *desc; caddr_t data = NULL; ! size_t size, desclen, datalen; int avail, i, error = 0; u_int8_t *user_data = NULL; *************** *** 528,534 **** * we can allocate enough storage for all of them. We assume * that the first one can fit into 1k. */ ! data = (caddr_t)malloc(1024, M_DEVBUF, M_WAITOK); if (error = ch_getelemstatus(sc, sc->sc_firsts[chet], 1, data, 1024)) goto done; --- 529,540 ---- * we can allocate enough storage for all of them. We assume * that the first one can fit into 1k. */ ! datalen = 1024; ! #ifdef BOUNCE_BUFFERS ! data = (caddr_t)vm_bounce_kva_alloc(btoc(datalen)); ! #else ! data = (caddr_t)malloc(datalen, M_DEVBUF, M_WAITOK); ! #endif if (error = ch_getelemstatus(sc, sc->sc_firsts[chet], 1, data, 1024)) goto done; *************** *** 545,554 **** * Reallocate storage for descriptors and get them from the * device. */ free(data, M_DEVBUF); data = (caddr_t)malloc(size, M_DEVBUF, M_WAITOK); if (error = ch_getelemstatus(sc, sc->sc_firsts[chet], ! sc->sc_counts[chet], data, size)) goto done; /* --- 551,566 ---- * Reallocate storage for descriptors and get them from the * device. */ + #ifdef BOUNCE_BUFFERS + vm_bounce_kva_alloc_free((vm_offset_t)data, btoc(datalen)); + data = (caddr_t)vm_bounce_kva_alloc(btoc(size)); + #else free(data, M_DEVBUF); data = (caddr_t)malloc(size, M_DEVBUF, M_WAITOK); + #endif + datalen = size; if (error = ch_getelemstatus(sc, sc->sc_firsts[chet], ! sc->sc_counts[chet], data, size)) goto done; /* *************** *** 575,581 **** --- 587,597 ---- done: if (data != NULL) + #ifdef BOUNCE_BUFFERS + vm_bounce_kva_alloc_free((vm_offset_t)data, btoc(datalen)); + #else free(data, M_DEVBUF); + #endif if (user_data != NULL) free(user_data, M_DEVBUF); return (error); From owner-freebsd-scsi Wed Jul 30 22:48:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA05623 for freebsd-scsi-outgoing; Wed, 30 Jul 1997 22:48:22 -0700 (PDT) Received: from dahan.metonymy.com (max1-242.aip.realtime.net [205.238.168.242]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA05607; Wed, 30 Jul 1997 22:48:11 -0700 (PDT) Received: from localhost ([[UNIX: localhost]]) by dahan.metonymy.com (8.8.6/8.8.3) with SMTP id AAA00302; Thu, 31 Jul 1997 00:47:40 -0500 (CDT) X-Authentication-Warning: dahan.metonymy.com: khym owned process doing -bs Date: Thu, 31 Jul 1997 00:47:39 -0500 (CDT) From: Dave Huang X-Sender: khym@dahan.metonymy.com Reply-To: Dave Huang To: Stefan Esser cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Disk activity light on Asus SC875 doesn't work In-Reply-To: <19970721222749.48037@mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 21 Jul 1997, Stefan Esser wrote: > So, if you wait for a few more days, you may find that > your status LED will suddenly start to blink :) Well, I ported the changes in version 1.100 of ncr.c into the NetBSD driver, enabled SCSI_NCR_SYMBIOS_COMPAT, and my LED is working now! Thanks! :) Now I guess I need to work on the patch from 100 to 101... wow, that's a pretty big diff :) What's the benefit of loading the microcode into the on-chip RAM, anyways? -- Name: Dave Huang | Mammal, mammal / their names are called / INet: khym@bga.com | they raise a paw / the bat, the cat / FurryMUCK: Dahan | dolphin and dog / koala bear and hog -- TMBG Dahan: Hani G Y+C 21 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++ From owner-freebsd-scsi Thu Jul 31 01:36:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA18241 for freebsd-scsi-outgoing; Thu, 31 Jul 1997 01:36:53 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA18200; Thu, 31 Jul 1997 01:36:39 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id SAA27390; Thu, 31 Jul 1997 18:06:31 +0930 (CST) From: Michael Smith Message-Id: <199707310836.SAA27390@genesis.atrad.adelaide.edu.au> Subject: Re: SCSI 1542 error In-Reply-To: <199707310510.WAA15704@daemonweed.reanimators.org> from Frank McConnell at "Jul 30, 97 10:10:55 pm" To: fmc@reanimators.org (Frank McConnell) Date: Thu, 31 Jul 1997 18:06:31 +0930 (CST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Frank McConnell stands accused of saying: > > I noticed this the other day (similar config, 2.2.1, ISA bus, 1542CP? > with Archive changer) and have come up with what I think is a fix. > Diffs below. As a non-SCSI-god, I can't actually commit to this one. I would ask that if it's not done in the next day or two that you file a PR with this patch so that it's not lost 8) > (d) From (c), I probably have no business monkeying with this > sort of thing, and someone who knows more ought to look this over. > It lets me do chio status in addition to chio move, but that's as > far as I've tested it. Criticism is welcome. Well, this deserves some criticism; there's no other way to learn than to muck around with it, and nobody has more "business" to be monkeying with it that someone who cares about it. 8) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-scsi Thu Jul 31 08:28:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA15467 for freebsd-scsi-outgoing; Thu, 31 Jul 1997 08:28:40 -0700 (PDT) Received: from smtp-relay-1.Adobe.COM (smtp-relay-1.adobe.com [192.150.11.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA15458 for ; Thu, 31 Jul 1997 08:28:33 -0700 (PDT) Received: by smtp-relay-1.Adobe.COM (8.8.5) with ESMTP id IAA12170; Thu, 31 Jul 1997 08:25:49 -0700 (PDT) Received: by inner-relay-1.Adobe.COM (8.8.5) with ESMTP id IAA29761; Thu, 31 Jul 1997 08:27:01 -0700 (PDT) Received: by mail-345.corp.Adobe.COM (8.7.5) with SMTP id IAA01907; Thu, 31 Jul 1997 08:27:22 -0700 (PDT) Message-Id: <3.0.1.32.19970731082636.006952b8@mail-345> X-Sender: jylee@mail-345 X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Thu, 31 Jul 1997 08:26:36 -0700 To: freebsd-scsi@freebsd.org From: Jyehoon Lee Subject: unsubscribe Cc: jlee@cs.umd.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe jlee@cs.umd.edu From owner-freebsd-scsi Fri Aug 1 04:06:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA14358 for freebsd-scsi-outgoing; Fri, 1 Aug 1997 04:06:38 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA14353; Fri, 1 Aug 1997 04:06:28 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id EAA27735; Fri, 1 Aug 1997 04:06:17 -0700 (PDT) Date: Fri, 1 Aug 1997 04:06:17 -0700 (PDT) Message-Id: <199708011106.EAA27735@silvia.HIP.Berkeley.EDU> To: gibbs@plutotech.com CC: gibbs@freebsd.org, scsi@freebsd.org In-reply-to: <199707301827.MAA17071@pluto.plutotech.com> (gibbs@plutotech.com) Subject: Re: NOT READY From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for your reply, Justin. * be doing to cause the drive to spin down. You could try adding in a start * unit in the sense handler for the sd driver and see if it clears up your * problem. Something like this? === Index: sd.c =================================================================== RCS file: /usr/cvs/src/sys/scsi/sd.c,v retrieving revision 1.95.2.2 diff -u -r1.95.2.2 sd.c --- sd.c 1997/02/05 19:02:22 1.95.2.2 +++ sd.c 1997/08/01 08:54:18 @@ -853,6 +853,13 @@ if (inqbuf->dev_qual2 & SID_REMOVABLE) return SCSIRET_CONTINUE; + /* Restart if drive says not ready. + */ + if ((sense->error_code & SSD_ERRCODE_VALID) == 0x2) { + scsi_start_unit(sc_link, SCSI_ERR_OK | SCSI_SILENT); + return SCSIRET_CONTINUE; + } + /* Retry all disk errors. */ scsi_sense_print(xs); === (I haven't tried it yet...it's kinda scary. ;) * The sd driver will perform a start unit (unconditionally) when the * device is opened. This will cause the drive to spin up and everything * will go back to normal. I see. * It wouldn't surprise me at all if this were a thermal problem. * Stick a temperature sensor in the enclosure (on the drive itself) * and rule this out. I'll see how I can do that. Satoshi From owner-freebsd-scsi Fri Aug 1 05:14:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA16827 for freebsd-scsi-outgoing; Fri, 1 Aug 1997 05:14:51 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA16822 for ; Fri, 1 Aug 1997 05:14:48 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA06673; Fri, 1 Aug 1997 06:56:52 -0400 (EDT) From: Peter Dufault Message-Id: <199708011056.GAA06673@hda.hda.com> Subject: Re: NOT READY In-Reply-To: <199708011106.EAA27735@silvia.HIP.Berkeley.EDU> from Satoshi Asami at "Aug 1, 97 04:06:17 am" To: asami@cs.berkeley.edu (Satoshi Asami) Date: Fri, 1 Aug 1997 06:56:52 -0400 (EDT) Cc: scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Something like this? > > === > Index: sd.c > =================================================================== > RCS file: /usr/cvs/src/sys/scsi/sd.c,v > retrieving revision 1.95.2.2 > diff -u -r1.95.2.2 sd.c > --- sd.c 1997/02/05 19:02:22 1.95.2.2 > +++ sd.c 1997/08/01 08:54:18 > @@ -853,6 +853,13 @@ > if (inqbuf->dev_qual2 & SID_REMOVABLE) > return SCSIRET_CONTINUE; > > + /* Restart if drive says not ready. > + */ > + if ((sense->error_code & SSD_ERRCODE_VALID) == 0x2) { > + scsi_start_unit(sc_link, SCSI_ERR_OK | SCSI_SILENT); > + return SCSIRET_CONTINUE; > + } > + > /* Retry all disk errors. > */ > scsi_sense_print(xs); > === > > (I haven't tried it yet...it's kinda scary. ;) Something like that - I think you want to return SCSIRET_DO_RETRY and not SCSIRET_CONTINUE, and you may need to delay in there somehow because it is going to take a while to spin up. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval From owner-freebsd-scsi Fri Aug 1 11:49:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA05326 for freebsd-scsi-outgoing; Fri, 1 Aug 1997 11:49:32 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA05313 for ; Fri, 1 Aug 1997 11:49:17 -0700 (PDT) Received: (qmail 5040 invoked by uid 1000); 1 Aug 1997 18:49:26 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 01 Aug 1997 11:49:25 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Jon E. Mitchiner" , freebsd-scsi@freebsd.org Subject: Re: DPT Raid Controller Drivers (fwd) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi "Jon E. Mitchiner"; On 01-Aug-97 you wrote: > > It is all in working order. the server was down for this weekend. > Sorry. > > try patch 1.1.10 in sendero-ppp.i-connect.net/crash. > > A boot floppy will be there shortly. > > Just wanted to clarify the raid configuration process -- I have 6 drives, > the first 2 drives will be mirrored and used as the boot drive, and the > other 4 drives will be used for mirroring, or perhaps striping 1/2 drive, > and then using software to mirror it onto the 3rd/4th drive. Io need. If you have two or more busses, split the disks evenly across two busses. If not, just put them on bus zero. See a previous posting on how to set them up. There is really little point in splitting the boot disks from the rest, except for easier partitioning. > Do I need to configure the drives outside of FreeBSD or does the boot.flp > give options to configure the RAID options/configs? You have to use dptmgr. The boot floppy does not (yet) give you this option. > If you could make some steps on how I should go about setting up the > system, let me know and I'll probably be doing a total conversion > tomorrow > and see how it goes. It's going into a production machine so hopefully > it'll work smoothly. :) I already posted a step by step, but here are the essential steps: * Install everything * Boot M$-Dog * Put DPT floppy #1 in A: * Run DPTMGR/fw0 * Initialize to ``other O/S'' * Create the RAID arrays you want * Remember to alternate busses whenever possible (bus-0 disk 0, bus 1 disk 0, bus 0 disk 1, bus 1 disk 1, etc.) * Re-boot DOS * fdisk to leave a small/large DOS partition on the ``first disk'' * Install FreeBSD Simon P.S. I am forwarding a copy to FreeBSD-SCSI. Others may find this useful. From owner-freebsd-scsi Fri Aug 1 16:04:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA17329 for freebsd-scsi-outgoing; Fri, 1 Aug 1997 16:04:28 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA17317; Fri, 1 Aug 1997 16:04:18 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-8.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA04696 (5.67b/IDA-1.5); Sat, 2 Aug 1997 01:04:13 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id AAA00478; Sat, 2 Aug 1997 00:07:57 +0200 (CEST) X-Face: " Date: Sat, 2 Aug 1997 00:06:35 +0200 From: Stefan Esser To: Dave Huang Cc: freebsd-scsi@FreeBSD.ORG, Stefan Esser Subject: Re: Disk activity light on Asus SC875 doesn't work References: <19970721222749.48037@mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Dave Huang on Thu, Jul 31, 1997 at 12:47:39AM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 31, Dave Huang wrote: > On Mon, 21 Jul 1997, Stefan Esser wrote: > > So, if you wait for a few more days, you may find that > > your status LED will suddenly start to blink :) > > Well, I ported the changes in version 1.100 of ncr.c into the NetBSD > driver, enabled SCSI_NCR_SYMBIOS_COMPAT, and my LED is working now! > Thanks! :) Now I guess I need to work on the patch from 100 to 101... wow, > that's a pretty big diff :) Well, it *looks* big, but I think it should apply with very little problems, since most lines that change are in the SCRIPTS code and the loader, which should not be any different in NetBSD. (BTW: I want to have the NCR driver found in the FreeBSD-current sources compatible to NetBSD as well, but don't have any NetBSD system to test it on. I'd really qppreciate, if you could send back the changes you had to apply. Else the code in NetBSD will diverge it will become ever harder to apply changes made to the FreeBSD code ...) > What's the benefit of loading the microcode into the on-chip RAM, anyways? The NCR chips traditionally fetched instructions from system DRAM. The 53c810 only supported single cycle accesses (which required two to three single DWORD PCI bus transfers per instruction), later chips offered burst op-code fetch and read-ahead for better PCI bus efficiency and higher execution rates. The 4KB SRAM found in 53c825A and 53c875 chips is big enough to hold most of the code required for normal SCSI command execution. Only the scatter/gather tables and some exception handling code doesn't fit in, but since this is only a small fraction of all accesses, the PCI bus load can be significantly reduced. Since the CPU in the NCR chip will stall if it can fetch instructions fast enough, use of the SRAM can reduce SCSI command overhead and the associated latencies, which will be most obvious in a system with many disk drives and possibly several NCR SCSI controllers. Regards, STefan From owner-freebsd-scsi Sat Aug 2 09:28:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA00165 for freebsd-scsi-outgoing; Sat, 2 Aug 1997 09:28:49 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA00159 for ; Sat, 2 Aug 1997 09:28:43 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id LAA10894; Sat, 2 Aug 1997 11:42:33 -0400 (EDT) From: Peter Dufault Message-Id: <199708021542.LAA10894@hda.hda.com> Subject: Re: Need help on writing SCSI scanner driver In-Reply-To: from "Andreas S. Wetzel" at "Aug 2, 97 12:31:42 pm" To: root@deadline.snafu.de (Andreas S. Wetzel) Date: Sat, 2 Aug 1997 11:42:33 -0400 (EDT) Cc: scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Follow up to -scsi, so I'll include the whole mail. > Some time ago I started to write a high level SCSI driver for my > AGFA Studio Star scanner. Now I'm facing some minor problems in > the overall design of the driver code. My imagination of a scanner > driver has been to have a device that is opened by the application > software by a open(2) call and than configured to the correct scan > parameters using ioctls before the scan data is retrieved via one > or more read(2) calls. The problem in this context seems to be > that the scanner is in fact able to deliver all the scan data > at once, but the I/O subsystem seems to split a big read call into > several 64k segments. Another problem is that the scanner expects > the READ_SCANNED_DATA SCSI command to have a number of scanlines > (not bytes) attached, so I will have to convert the number of > bytes from a read(2) call to a number of scan lines internally > in the driver code. My question is, if it is possible to read > in all the scan data at once from the scanner (wheter or not > it is handed to the user process in 64k segments). In other words, > I do want to only issue a READ_SCANNED_DATA SCSI command to the > scanner once, but not everytime a 64k segment is read by the user > process. I need to know more about the scanner before I can be intelligent. I assume Agfa makes everything from top end 4k pixel/inch scanners to desktop systems, and what you do depends on what the device is. Also, how the device behaves is important. If you send down a window size, start scan, and then start reading back data and as long as you keep the device FIFO empty it will continue to scan at peak performance there is little reason to try to buffer the image in memory or transfer the image in a single SCSI call. After all, for most run of the mill scanners the mechanical motion will not saturate the SCSI bus (I know this is not true for high end devices such as this may be). Post a little more info about what kind of scanner this is, peak performance, whether it will disconnect/reconnect properly, and how it appears to want to be driven based on the documentation and I'll try again. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval From owner-freebsd-scsi Sat Aug 2 10:22:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA02272 for freebsd-scsi-outgoing; Sat, 2 Aug 1997 10:22:14 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA02262 for ; Sat, 2 Aug 1997 10:22:10 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA17642; Sat, 2 Aug 1997 19:22:08 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id SAA26304; Sat, 2 Aug 1997 18:54:04 +0200 (MET DST) Message-ID: <19970802185404.JN62579@uriah.heep.sax.de> Date: Sat, 2 Aug 1997 18:54:04 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Cc: root@deadline.snafu.de (Andreas S. Wetzel) Subject: Re: Need help on writing SCSI scanner driver References: <199708021542.LAA10894@hda.hda.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199708021542.LAA10894@hda.hda.com>; from Peter Dufault on Aug 2, 1997 11:42:33 -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Peter Dufault wrote: > > Some time ago I started to write a high level SCSI driver for my > > AGFA Studio Star scanner. Now I'm facing some minor problems in > > the overall design of the driver code. > I need to know more about the scanner before I can be intelligent. > I assume Agfa makes everything from top end 4k pixel/inch scanners > to desktop systems, and what you do depends on what the device is. I would suggest to investigate NetBSD's scanner code (or maybe it was OpenBSD, i eventually forgot). IIRC, the author of PINT wrote this part, Kenneth Stailey (sp?). I've only seen the feature list so far, but it looked like a generic scanner solution. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sat Aug 2 11:35:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA05523 for freebsd-scsi-outgoing; Sat, 2 Aug 1997 11:35:33 -0700 (PDT) Received: from cenotaph.snafu.de (gw-deadnet.snafu.de [194.121.229.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA05517 for ; Sat, 2 Aug 1997 11:35:28 -0700 (PDT) Received: by cenotaph.snafu.de from deadline.snafu.de using smtp id m0wuj18-000KChC; Sat, 2 Aug 1997 20:35:06 +0200 (CEST) (Smail-3.2 1996-Jul-4 #1) Received: by deadline.snafu.de id m0wuj18-0004jwC; Sat, 2 Aug 1997 20:35:06 +0200 (CEST) (Smail-3.2 1996-Jul-4 #1) Message-Id: From: root@deadline.snafu.de (Andreas S. Wetzel) Subject: Re: Need help on writing SCSI scanner driver To: dufault@hda.com (Peter Dufault) Date: Sat, 2 Aug 1997 20:35:05 +0200 (CEST) Cc: scsi@freebsd.org In-Reply-To: <199708021542.LAA10894@hda.hda.com> from Peter Dufault at "Aug 2, 97 11:42:33 am" Organization: A world stranger than you have ever imagined. X-Mailer: ELM [version 2.4ME+ PL13] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! --- Peter Dufault writes: ] Follow up to -scsi, so I'll include the whole mail. ] ] > Some time ago I started to write a high level SCSI driver for my ] > AGFA Studio Star scanner... ] > [...] ] ] I need to know more about the scanner before I can be intelligent. ] I assume Agfa makes everything from top end 4k pixel/inch scanners ] to desktop systems, and what you do depends on what the device is. ] ] [...] ] ] Post a little more info about what kind of scanner this is, peak ] performance, whether it will disconnect/reconnect properly, and ] how it appears to want to be driven based on the documentation and ] I'll try again. I have the complete SCSI interface description of the Scanner online at ftp://cenotaph.snafu.de/pub/doc/studiostar.doc (Microsoft Word document - that's what AGFA sent me upon email request). Regards, Mickey -- (__) (@@) Andreas S. Wetzel Mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://cenotaph.snafu.de/ / | || 13347 Berlin Fon: <+4930> 456 066 90 * ||----|| Germany Fax: <+4930> 456 066 91/92 ~~ ~~ From owner-freebsd-scsi Sat Aug 2 13:04:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA10890 for freebsd-scsi-outgoing; Sat, 2 Aug 1997 13:04:53 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA10879 for ; Sat, 2 Aug 1997 13:04:44 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id PAA11268; Sat, 2 Aug 1997 15:18:17 -0400 (EDT) From: Peter Dufault Message-Id: <199708021918.PAA11268@hda.hda.com> Subject: Re: Need help on writing SCSI scanner driver In-Reply-To: from "Andreas S. Wetzel" at "Aug 2, 97 08:35:05 pm" To: root@deadline.snafu.de (Andreas S. Wetzel) Date: Sat, 2 Aug 1997 15:18:16 -0400 (EDT) Cc: scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have the complete SCSI interface description of the Scanner online > at ftp://cenotaph.snafu.de/pub/doc/studiostar.doc (Microsoft Word > document - that's what AGFA sent me upon email request). I'm not keen on looking at a word document SCSI spec - I'm interested in what kind of scanner it is. If it is a run of the mill desktop scanner I recommend you follow Joerg's suggestion and look at an existing scanning utility and see how to plug it in. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval From owner-freebsd-scsi Sat Aug 2 13:33:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA12435 for freebsd-scsi-outgoing; Sat, 2 Aug 1997 13:33:13 -0700 (PDT) Received: from cenotaph.snafu.de (gw-deadnet.snafu.de [194.121.229.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA12430 for ; Sat, 2 Aug 1997 13:33:09 -0700 (PDT) Received: by cenotaph.snafu.de from deadline.snafu.de using smtp id m0wukrK-000K9WC; Sat, 2 Aug 1997 22:33:06 +0200 (CEST) (Smail-3.2 1996-Jul-4 #1) Received: by deadline.snafu.de id m0wukrK-0004jwC; Sat, 2 Aug 1997 22:33:06 +0200 (CEST) (Smail-3.2 1996-Jul-4 #1) Message-Id: From: root@deadline.snafu.de (Andreas S. Wetzel) Subject: Re: Need help on writing SCSI scanner driver To: dufault@hda.com (Peter Dufault) Date: Sat, 2 Aug 1997 22:33:06 +0200 (CEST) Cc: scsi@freebsd.org In-Reply-To: <199708021918.PAA11268@hda.hda.com> from Peter Dufault at "Aug 2, 97 03:18:16 pm" Organization: A world stranger than you have ever imagined. X-Mailer: ELM [version 2.4ME+ PL13] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! --- Peter Dufault writes: ] > I have the complete SCSI interface description of the Scanner online ] > at ftp://cenotaph.snafu.de/pub/doc/studiostar.doc (Microsoft Word ] > document - that's what AGFA sent me upon email request). ] ] I'm not keen on looking at a word document SCSI spec - I'm interested ] in what kind of scanner it is. If it is a run of the mill desktop ] scanner I recommend you follow Joerg's suggestion and look at an ] existing scanning utility and see how to plug it in. The Studio Star is a 8 1/2" x 14" flatbed type one-pass scanner with an optical resolution of 600x1200 ppi. It supports up to 10 bit gray or 30 bit color scanning. The specified scanning speed is 5ms per line in gray scanning mode and 6.5ms in color mode. The transmission speed is rated at 2 Mb/sec. So tell me is this a "run of the mill" scanner ??? Regards, Mickey -- (__) (@@) Andreas S. Wetzel Mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://cenotaph.snafu.de/ / | || 13347 Berlin Fon: <+4930> 456 066 90 * ||----|| Germany Fax: <+4930> 456 066 91/92 ~~ ~~ From owner-freebsd-scsi Sat Aug 2 13:47:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA13166 for freebsd-scsi-outgoing; Sat, 2 Aug 1997 13:47:38 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA13156 for ; Sat, 2 Aug 1997 13:47:33 -0700 (PDT) Received: (qmail 8388 invoked by uid 1000); 2 Aug 1997 20:47:48 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 02 Aug 1997 13:47:48 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: FreeBSD-SCSI@FreeBSD.ORG Subject: DPT Perfromance with Patch 1.1.10 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Some of you have asked or wondered about what performance to expect out of this release. Aside from RDBMS testing (which is meaningless for most of us, here are numbers reported and noted casually on sendero: * Sendero is a SuperMicro P6-200 motherboard with 128MB RAM * DPT is PM3334UW with 64MB of ECC memory. * Two internal disks arranged as RAID-1 are used for /, /usr, etc. Both disks are on Bus 0 * /usr/src and other active filesystems are on a 2wide RAID-0 in a DPT 9W tower using 4GB Baracuda disks. * Archives, CVS, etc. are on a 4x RAID-5, in the same cabinet, same type disks. * All striping values are DPT defaults. However, the 9W tower is split into two busses, and the raid arrays are symetrically balanced across the busses. * This is a less-than-optimal arrangement for optimal performance, but reasonable, considering the resources. * A typical job mix is Kernel PPP on a 64K ISDN channel, make world on the 2.2 tree, building of two kernels simultanously and a large NFS update of copper (the next sendero). All this with email, X11 and other such nonsense. If it makes a difference, the X11 display is on a #9 S3 card, running 1600x1200@75Hz. Yes the type is small on a 17" monitor. System responsiveness is excellent, no delays in the X11 response, no crashes in the last 2 weeks or so. Xprefmon++ reports: * 780 or more Disk Transfers per second. * 700 or more NFS Srver Calls/Sec * 1700 Interrupts/Sec. We have seen, repeatedly peaks of: * 1,500 disk i/o per sec * 900 NFS service calls per sec * 5,600 (no typo) interrupts/sec. The high interrupt rate happens when we run the ISDN line at 128Kbps. The high I/O rate happens when we add stress testing to the mix. Where we see slow numbers is on the SMP -current kernel. We are still working on that one. The only DPT options in the configuration are: options DPT_USE_SINTR=1 options DPT_MEASURE_PERFORMANCE options DPT_COMMAND_SPLHIGH # Experimental, briefly locks eata ports Hope this answers some questions. Simon From owner-freebsd-scsi Sat Aug 2 17:00:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA23009 for freebsd-scsi-outgoing; Sat, 2 Aug 1997 17:00:38 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA23000 for ; Sat, 2 Aug 1997 17:00:35 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.6/8.8.5) id RAA13564 for FreeBSD-SCSI@FreeBSD.ORG; Sat, 2 Aug 1997 17:00:49 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 02 Aug 1997 17:00:49 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: FreeBSD-SCSI@FreeBSD.ORG Subject: Phoenix... SCSI Devices Minor Mapping Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am sure this subject came up before, more than once. I have a reason to raise it out of the ashes... I am dealing with systems with very large databases, some systems will have up to 8 DPT controllers, 4 busses per controller, 15 SCSI hubs per bus, 7 devices per hub. This gives us well over 3,000 drives. We need some certain and predictable mapping between minor so that system operators can relate /dev name to controller/bus/target. and to hardware cabinetry. What I propose is a voluntary standard for wiring down devices, so any large scale system can be predictable. The first question to be answered is: How do we want to relate to FCAL (Fiber Channel Arbitrated Loop)? We can: a. Ignore it b. Acomodate it c. Force it into a conventional mapping. Of immediate interest is the fact that up to 256 devices can share a single loop. BTW, performance on these is pretty amazing sight. Proposal A: Divide the minor number as follows: f e d c b a 9 8 7 6 5 4 3 2 1 0 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | c | c | c | c | b | b | b | b | l | l | l | l | t | t | t | t | +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ Where t = Target ID l = Logigal Unit number b = Bus number c = Controller number As you have noticed, the LUN is in a higher bit position than the Target. Although this breaks down to logical order, it makes most small systems, using LUN-0-only devices, have something almost identical to the existing situation. FCAL can be acomodated by concatenating the LUn and Target fields and insisting that FCAL devices have no LUNs other than ZERO. Naming convention: printf("c%1xb%1xt%1xu%1x", controller, bus, target, lun); If you noticed, i am avoiding using ``l'' for LUN's as it is too confusing with ``1''. Also, the order is logically correct. The kernel's ``unit'' is mapped to the controller in this note. The channel is determined by: ((xs->sc_link->adapter_bus) % (((unit) + 1) * 8)) The target by: xs->sc_link->target and the LUN by: xs->sc_link->lun This will allow us up to 16 controllers, 8 busses each, with either 256 bus ID's or 16 Id's with 16 LUNs on each. Should be enough for a release or two. Proposal B: Similar to Proposal A but with complete renaming and the following bitmap: f e d c b a 9 8 7 6 5 4 3 2 1 0 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | b | b | b | b | t | t | t | t | t | t | t | t | l | l | l | l | +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 1f 1e 1d 1c 1b 1a 19 18 17 16 15 14 13 12 11 10 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | - | - | - | - | - | - | - | - | - | - | - | - | c | c | c | c | +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ Where t = Target ID l = Logigal Unit number b = Bus number c = Controller number - = Reserved And a naming mask of "c%1x"b%1xt%02xl%1x" Any input will be greatly apreciated. Simon From owner-freebsd-scsi Sat Aug 2 20:57:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA02693 for freebsd-scsi-outgoing; Sat, 2 Aug 1997 20:57:01 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA02657; Sat, 2 Aug 1997 20:56:52 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.6/8.8.5) id UAA14882; Sat, 2 Aug 1997 20:57:07 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 02 Aug 1997 20:57:07 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: FreeBSD-SCSI@FreeBSD.ORG, FreeBSD-Current@FreeBSD.ORG Subject: Kernel Build Fails - AHC Error Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, I know justin is on vacation, but did any of you encounter: cd ../../dev/aic7xxx; make obj; make BINDIR=/usr/src/3.0/src/sys/compile/SENDERO-smp all install yacc -d /usr/src/3.0/src/sys/dev/aic7xxx/gram.y /usr/obj/usr/src/3.0/src/sys/dev/aic7xxx created for /usr/src/3.0/src/sys/dev/aic7xxx yacc -d /usr/src/3.0/src/sys/dev/aic7xxx/gram.y mv y.tab.c gram.c mv y.tab.c gram.c cd ../../dev/aic7xxx; make obj; make BINDIR=/usr/src/3.0/src/sys/compile/SENDERO all install cc -O -I. -c gram.c mv: y.tab.c: No such file or directory *** Error code 1 This is in current as of today. Simon