From owner-freebsd-scsi Sun Oct 3 3:35:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front6.grolier.fr (front6.grolier.fr [194.158.96.56]) by hub.freebsd.org (Postfix) with ESMTP id 462EC1538B for ; Sun, 3 Oct 1999 03:35:14 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-162-210.villette.club-internet.fr [195.36.162.210]) by front6.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id MAA24031 for ; Sun, 3 Oct 1999 12:35:08 +0200 (MET DST) Date: Sun, 3 Oct 1999 12:56:22 +0200 (MET DST) From: Gerard Roudier X-Sender: groudier@localhost To: scsi@FreeBSD.org Subject: SYM driver 0.6.0 -> BETA Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I just made available sym driver release 0.6.0 at: ftp://ftp.tux.org/pub/roudier/drivers/freebsd/experimental/ Since I have completed successfully all the testings I had=20 planned, and based on the few number of problem reports I=20 received (all have hopefully been fixed), I have decided to=20 switch the sym driver status to BETA-RELEASE for the support=20 of SPI2 and i386 architecture. The testings of the C1010 support (Ultra-3 DT data transfer=20 support) is planned to be performed at LSILOGIC by Pamela Delaney=20 , since I haven't all needed hardware=20 resources for that testings, neither I have time enough for.=20 Pamela has added support for the C1010 to the Linux sym53c8xx=20 driver and her current sym53c8xx driver version is working=20 quite well with C1010 revision 0. I donnot have information=20 about the availibility of C1010 based controllers. Hopefully=20 this will happen at the beginning of Year 2000 or just before. The purpose of the sym_hipd driver for FreeBSD is to provide=20 the best possible support for 810A, 860, 825A, 875, 876, 885, 895,=20 895A, 896 and 1010 SYMBIOS/LSI PCI-SCSI controllers which is not=20 provided by the stock ncr driver. The old chips (810, 815, 825),=20 that are not supported by the sym_hipd driver can be reasonnably supported by the ncr driver that had been designed and implemented=20 at the time of the 810/815/825. I also have planned to propose=20 some minor enhancements and to rewrite some code related to=20 FreeBSD-CAM in the ncr driver. Performance comparisons between the ncr and the sym drivers may=20 allow to suspect bugs in a driver or to give clues about pathes =20 in the ncr driver that need to be improved. People who may want=20 to demonstrate that ncr is faster than sym are wasting their time=20 in my not so humble opinion. On the other hand, it would be interesting to have some results=20 addressing reliability and performances comparisons against=20 equivalent host adapters from other vendors (given reasonnable SIM). For now, I didn't received any result of this kind. Even if my crystal ball has told me about the reasons of this=20 lacking of reports, I would be glad to check how it has been right. ;-) Thanks in advance for the reports. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 4 1: 7:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from meloghost.melog.de (meloghost.melog.de [193.155.17.3]) by hub.freebsd.org (Postfix) with ESMTP id 0BD7714D1B for ; Mon, 4 Oct 1999 01:07:20 -0700 (PDT) (envelope-from hf@Melog.DE) Received: from janus (janus.melog.de [193.155.17.21]) by meloghost.melog.de (8.9.3/8.9.3) with ESMTP id KAA04255; Mon, 4 Oct 1999 10:06:58 +0200 Message-Id: <4.2.0.58.19991004100335.0362e370@mail.saphirsc.de> X-Sender: hf@meloghost.melog.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 04 Oct 1999 10:06:57 +0200 To: John and Jennifer Reynolds From: Hauke Fath Subject: Re: new quirk entry for my seagate tape-- this time a STT20000N Cc: mjacob@feral.com, Mike Tancsa , John and Jennifer Reynolds , freebsd-scsi@FreeBSD.ORG In-Reply-To: <14326.29994.47289.270980@localhost.primenet.com> References: <37f63490.1434693500@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 14:12 02.10.99 -0700, John and Jennifer Reynolds wrote: >[ On Saturday, October 2, Matthew Jacob wrote: ] > > > > Will do. Also am adding > > > > options SA_1FM_AT_EOD > > > > option so that you can just configure a kernel to default to the one > > filemark behaviour (quirks will still override). This will be in -current > > and -stable in an hour. > > > >Splendid idea! With all these blastid Seagate drives needing the quirk, it >makes sense. AFAICS, those are travan drives which are descendants of QIC. I never found a definite reference (can anybody help me out there?) but folklore seems to have it that marking EOD with *one* filemark is a QIC property -- and it should probably be tagged as such. hauke -- Hauke Fath Saphir Software GmbH D-69115 Heidelberg hf@SaphirSC.DE Ruf +49-6221-13866-35, Fax -21 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 4 11: 4: 6 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 29ECD1555F for ; Mon, 4 Oct 1999 11:03:56 -0700 (PDT) (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 LAA25591; Mon, 4 Oct 1999 11:03:43 -0700 Date: Mon, 4 Oct 1999 11:03:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Hauke Fath Cc: John and Jennifer Reynolds , Mike Tancsa , freebsd-scsi@FreeBSD.ORG Subject: Re: new quirk entry for my seagate tape-- this time a STT20000N In-Reply-To: <4.2.0.58.19991004100335.0362e370@mail.saphirsc.de> 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 never found a definite reference (can anybody help me out there?) but > folklore seems to have it that marking EOD with *one* filemark is a QIC > property -- and it should probably be tagged as such. It is, but it's impossible to tell a priori with some drives. It is my personal opinion that two filemarks at EOD should only be used for devices that cannot know physical EOT. Only 1/2" reel tapes come to mind on that one. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 4 12:19: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from munin.odin-corporation.com (fredriks-2.pr.mcs.net [205.164.50.242]) by hub.freebsd.org (Postfix) with ESMTP id CFC93150D0 for ; Mon, 4 Oct 1999 12:19:00 -0700 (PDT) (envelope-from lars@odin-corporation.com) Received: from odin-corporation.com (localhost [127.0.0.1]) by munin.odin-corporation.com (8.9.3/8.9.1) with ESMTP id OAA00885 for ; Mon, 4 Oct 1999 14:18:55 -0500 (CDT) (envelope-from lars@odin-corporation.com) Message-ID: <37F8FD9F.2B809681@odin-corporation.com> Date: Mon, 04 Oct 1999 14:18:55 -0500 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: scsi@freebsd.org Subject: data sheet/pinout/manual for WDC WD64C96 controller? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Anyone have information on the Western Digital WD64C96 controller that IBM uses on some of their scsi drives? I need to do a little soldering, and it would be nice to be sure that I am soldering the resistor to the right pin. Lars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 5 1:45:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from meloghost.melog.de (meloghost.melog.de [193.155.17.3]) by hub.freebsd.org (Postfix) with ESMTP id 3A02F150B0 for ; Tue, 5 Oct 1999 01:45:42 -0700 (PDT) (envelope-from hf@Melog.DE) Received: from janus (janus.melog.de [193.155.17.21]) by meloghost.melog.de (8.9.3/8.9.3) with ESMTP id KAA09349; Tue, 5 Oct 1999 10:44:44 +0200 Message-Id: <4.2.0.58.19991005104319.036414c0@mail.saphirsc.de> X-Sender: hf@meloghost.melog.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 05 Oct 1999 10:44:44 +0200 To: mjacob@feral.com From: Hauke Fath Subject: Re: new quirk entry for my seagate tape-- this time a STT20000N Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: References: <4.2.0.58.19991004100335.0362e370@mail.saphirsc.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:03 04.10.99 -0700, Matthew Jacob wrote: > > > > I never found a definite reference (can anybody help me out there?) but > > folklore seems to have it that marking EOD with *one* filemark is a QIC > > property -- and it should probably be tagged as such. > >It is, but it's impossible to tell a priori with some drives. > >It is my personal opinion that two filemarks at EOD should only be used >for devices that cannot know physical EOT. Only 1/2" reel tapes come to >mind on that one. So 2FM should be the exception and not the default (as it is in NetBSD)? Sounds reasonable. hauke -- Hauke Fath Saphir Software GmbH D-69115 Heidelberg hf@SaphirSC.DE Ruf +49-6221-13866-35, Fax -21 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 5 5:29:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id 6B3FC155EA for ; Tue, 5 Oct 1999 05:29:22 -0700 (PDT) (envelope-from voland@plab.ku.dk) Received: from eagle.plab.ku.dk (voland@eagle.plab.ku.dk [130.225.105.63]) by plab.ku.dk (8.9.3/8.9.3) with ESMTP id OAA43706 for ; Tue, 5 Oct 1999 14:30:01 +0200 (CEST) (envelope-from voland@plab.ku.dk) Received: (from voland@localhost) by eagle.plab.ku.dk (8.9.3/8.9.3) id OAA97338; Tue, 5 Oct 1999 14:29:15 +0200 (CEST) (envelope-from voland) Mime-version: 1.0 Content-type: text/plain; charset="koi8-r" Content-transfer-encoding: 8bit To: freebsd-scsi@freebsd.org Subject: 'Unexpected busfree' From: Vadim Belman Date: 05 Oct 1999 14:29:14 +0200 Message-ID: <85k8p2vvmt.fsf@eagle.plab.ku.dk> Lines: 30 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wonder if someone can tell me: what kind of error is the following? Unexpected busfree. LASTPHASE == 0x0 SEQADDR == 0x5e And what do I do with it? It appears rather often while dump'ing on a SureStore DLT40 SCSI tape connected to: ahc0: rev 0x00 int a irq 11 on pci0.15.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs The connection is not direct but thru an external SCSI drives case which contains three hard disks: da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) The tape is detected as: sa0 at ahc0 bus 0 target 1 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) -- /Voland Vadim Belman E-mail: voland@plab.ku.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 5 9:54: 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 B232414D39 for ; Tue, 5 Oct 1999 09:54:02 -0700 (PDT) (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 JAA29153; Tue, 5 Oct 1999 09:53:27 -0700 Date: Tue, 5 Oct 1999 09:53:27 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Hauke Fath Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: new quirk entry for my seagate tape-- this time a STT20000N In-Reply-To: <4.2.0.58.19991005104319.036414c0@mail.saphirsc.de> 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 Tue, 5 Oct 1999, Hauke Fath wrote: > At 11:03 04.10.99 -0700, Matthew Jacob wrote: > > > > > > I never found a definite reference (can anybody help me out there?) but > > > folklore seems to have it that marking EOD with *one* filemark is a QIC > > > property -- and it should probably be tagged as such. > > > >It is, but it's impossible to tell a priori with some drives. > > > >It is my personal opinion that two filemarks at EOD should only be used > >for devices that cannot know physical EOT. Only 1/2" reel tapes come to > >mind on that one. > > So 2FM should be the exception and not the default (as it is in NetBSD)? Yes, that's what made happen in NetBSD. > Sounds reasonable. The reason it hasn't been done until now is that there's a lot of tape utilities (tcopy amongst them) that currently depend on this behaviour. It is conceivable when 4.0 is released it might be the time to break things, but not in any of the 3.X releases. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 5 21:20:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from localhost.primenet.com (206-132-48-3.nas-1.SCF.primenet.com [206.132.48.3]) by hub.freebsd.org (Postfix) with ESMTP id 96892156EC for ; Tue, 5 Oct 1999 21:19:02 -0700 (PDT) (envelope-from jreynold@primenet.com) Received: (from jreynold@localhost) by localhost.primenet.com (8.9.3/8.9.3) id VAA86550; Tue, 5 Oct 1999 21:21:09 -0700 (MST) (envelope-from jreynold@primenet.com) From: John and Jennifer Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14330.52789.99569.326161@localhost.primenet.com> Date: Tue, 5 Oct 1999 21:21:09 -0700 (MST) To: scsi@freebsd.org Subject: questions on observed tape navigation behavior X-Mailer: VM 6.73 under Emacs 20.3.1 Cc: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello -scsi, I believe this is the correct group for this question(s). Perhaps somebody can shed some light on the following. I've been messing around with my TR4 tape drive lately (thanks to all those who helped me figure out the 1 FM@EOD thing!) but have run into some questions w.r.t. navigating files on a tape. First off, I'm in "variable" mode (mt blocksize 0) and am using 54k as my blocksize when actually writing to the tape with flexbackup (port not yet comitted, see ports/14108). The tape drive is also put into "1 file mark at EOD" mode via a quirk entry (tapestore 8000 NS hanging off a 7890). I wrote 3 files to the tape--afio "dumps" of /, /var, and /home. If I rewind the tape, I can successfully do "mt fsf 1" and seek to the next file and do a restore operation, or "mt fsf 2" and restore the last file. No problems here doing this. However, backing the tape up seems to be working non-intuitively to me. Consider the following sequence of ops that I performed on the same tape. 1) mt rewind 2) mt rdhpos : gives '0' 3) mt fsf 1 4) mt rdhpos : gives '116' 5) mt bsf 1 6) mt rdhpos : gives '115' 7) rewind again and mt fsf 2 8) mt rdhpos : gives '697' 9) mt bsf 1 10) mt rdhpos : gives '696' The following is how I picture the layout of the tape (#=filemark): 0 116 697 -----------------#--------------------#---------------------# <--- end of tape ^ ^ | | where fsf 1 put where fsf 2 put the head the head At step 5, I was expecting the tape to essentially rewind back to the beginning. I'd gone forward 1 file, I wanted to go back one file. Same goes for step 8-9. I seeked forward 2 files and then wanted to go back one file. I thought that rdhpos whould have returned 116 (which apparently is the beginning of the "2nd file" on this tape). Doing "man 4 sa" brings up the SA man page of which I've read and says: When reading a variable record/block from the tape, the head is logically considered to be immediately after the last item read, and before the next item after that. If the next item is a file mark, but it was never read, then the next process to read will immediately hit the file mark and receive an end-of-file notification. I can see that after doing an "mt fsf 1" from a rewound tape, rdhpos would return "116" and the head would be positioned to read the 1st record/block of the next file. Same goes for doing "mt fsf 2" from a rewound tape. However, I don't understand why doing "mt bsf 1" just backs up over the filemark and leaves the head there (at 115). In order to backup "a file" I have to execute "mt bsf 2" (which also takes quite a long time in comparison to the fsf ... don't know if that is "normal"). Are things working the way they're supposed to be? Is it a case of RTFM where the FM needs some extra verbage to help deconfuse tape newbies? In the case of the latter, I'd be more than happy to help extend man pages, etc., but first I need to understand the behavior I'm seeing. Thanks in advance, -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jreynold@primenet.com FreeBSD 3.3-STABLE. FreeBSD: The Power to Serve. http://www.primenet.com/~jreynold/ Come join us!!! @ 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 Tue Oct 5 22:41:58 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 714311570E for ; Tue, 5 Oct 1999 22:41:39 -0700 (PDT) (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 WAA31794; Tue, 5 Oct 1999 22:40:00 -0700 Date: Tue, 5 Oct 1999 22:40:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John and Jennifer Reynolds Cc: scsi@FreeBSD.ORG Subject: Re: questions on observed tape navigation behavior In-Reply-To: <14330.52789.99569.326161@localhost.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 5 Oct 1999, John and Jennifer Reynolds wrote: > > Hello -scsi, > > I believe this is the correct group for this question(s). > > Perhaps somebody can shed some light on the following. I've been messing around > with my TR4 tape drive lately (thanks to all those who helped me figure out the > 1 FM@EOD thing!) but have run into some questions w.r.t. navigating files on a > tape. > > First off, I'm in "variable" mode (mt blocksize 0) and am using 54k as my > blocksize when actually writing to the tape with flexbackup (port not yet > comitted, see ports/14108). The tape drive is also put into "1 file mark at > EOD" mode via a quirk entry (tapestore 8000 NS hanging off a 7890). > > I wrote 3 files to the tape--afio "dumps" of /, /var, and /home. If I > rewind the tape, I can successfully do "mt fsf 1" and seek to the next > file and do a restore operation, or "mt fsf 2" and restore the last file. > No problems here doing this. > > However, backing the tape up seems to be working non-intuitively to me. > > Consider the following sequence of ops that I performed on the same tape. > > 1) mt rewind > 2) mt rdhpos : gives '0' > 3) mt fsf 1 > 4) mt rdhpos : gives '116' > 5) mt bsf 1 > 6) mt rdhpos : gives '115' > 7) rewind again and mt fsf 2 > 8) mt rdhpos : gives '697' > 9) mt bsf 1 > 10) mt rdhpos : gives '696' > > The following is how I picture the layout of the tape (#=filemark): > > 0 116 697 > -----------------#--------------------#---------------------# <--- end of tape > ^ ^ > | | > where fsf 1 put where fsf 2 put > the head the head > > At step 5, I was expecting the tape to essentially rewind back to the > beginning. I'd gone forward 1 file, I wanted to go back one file. Same goes for > step 8-9. I seeked forward 2 files and then wanted to go back one file. I > thought that rdhpos whould have returned 116 (which apparently is the beginning > of the "2nd file" on this tape). Nope. You're confused over the 'sf' part of Bsf and Fsf. It is 'space filemark'- not 'space file'. So, after step 5 you would be: > 0 116 697 > -----------------#--------------------#---------------------# <--- end of tape > ^ and after step 8 you would be: > -----------------#--------------------#---------------------# <--- end of tape > ^ Sun used to confuse the semantics of this a bit- they invented a "Backspace File" function. This is hard to implement in hardware since tape drives typically note when a fileMARK (or a setMARK) has passed- not datablocks. So, if you want to backspace *files*, the formula is: back_space_file(N Files) = mt bsf (N + 1), mt fsf 1 Naturally this has a problem if you're only N files into the tape, so watch out for errors. If you get any error with this, assume you don't know where the hell you are and rewind. Also- as a side note- don't be alarmed if 'hardware' block numbers differ by more than one over filemarks, or even block to block. You cannot assume that they are densely packed as they are what the *drive* finds most convenient for locating to a specific spot on the tape. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 5 22:49: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from localhost.primenet.com (206-132-49-158.nas-1.SCF.primenet.com [206.132.49.158]) by hub.freebsd.org (Postfix) with ESMTP id C805C15687 for ; Tue, 5 Oct 1999 22:48:36 -0700 (PDT) (envelope-from jreynold@primenet.com) Received: (from jreynold@localhost) by localhost.primenet.com (8.9.3/8.9.3) id WAA14346; Tue, 5 Oct 1999 22:50:41 -0700 (MST) (envelope-from jreynold@primenet.com) From: John and Jennifer Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14330.58161.440372.617607@localhost.primenet.com> Date: Tue, 5 Oct 1999 22:50:41 -0700 (MST) To: mjacob@feral.com Cc: John and Jennifer Reynolds , scsi@FreeBSD.ORG Subject: Re: questions on observed tape navigation behavior In-Reply-To: References: <14330.52789.99569.326161@localhost.primenet.com> X-Mailer: VM 6.73 under Emacs 20.3.1 Cc: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ On Tuesday, October 5, Matthew Jacob wrote: ] > > Nope. You're confused over the 'sf' part of Bsf and Fsf. It is 'space > filemark'- not 'space file'. > > So, after step 5 you would be: > > and after step 8 you would be: > > Sun used to confuse the semantics of this a bit- they invented a > "Backspace File" function. This is hard to implement in hardware since > tape drives typically note when a fileMARK (or a setMARK) has passed- not > datablocks. Aaaa ... then that would explain it. The behavior I was "used to" was based upon doing dumps long ago as a sysadmin of a SunOS 4.1.3 box in school. Your explaination of what FreeBSD is doing make sense. I just wanted to make sure that what I was seeing was in fact "reality." > So, if you want to backspace *files*, the formula is: > > back_space_file(N Files) = mt bsf (N + 1), mt fsf 1 > > Naturally this has a problem if you're only N files into the tape, so > watch out for errors. If you get any error with this, assume you don't > know where the hell you are and rewind. OK. > Also- as a side note- don't be alarmed if 'hardware' block numbers differ > by more than one over filemarks, or even block to block. You cannot assume > that they are densely packed as they are what the *drive* finds most > convenient for locating to a specific spot on the tape. OK. Thanks! -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jreynold@primenet.com FreeBSD 3.3-STABLE. FreeBSD: The Power to Serve. http://www.primenet.com/~jreynold/ Come join us!!! @ 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 Wed Oct 6 7:46:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 113D814BE7 for ; Wed, 6 Oct 1999 07:46:33 -0700 (PDT) (envelope-from spork@super-g.com) Received: by super-g.com (Postfix, from userid 1000) id D4165B91C; Wed, 6 Oct 1999 10:45:52 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id C1413B91B for ; Wed, 6 Oct 1999 10:45:52 -0400 (EDT) Date: Wed, 6 Oct 1999 10:45:52 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: freebsd-scsi@freebsd.org Subject: Applying CAM patches to 2.2-stable 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 Hello, I've massaged the CAM patchkit into applying cleanly to a 2.2-stable source tree from 9/1/99. Most changes were cosmetic, white space, or "$id" mismatches, nothing beyond that... Anyhow, on doing a make depend (after config'ing using config from the same tree) I get the following: ../../pci/aic7870.c:63: aic7xxx_reg.h: No such file or directory Of course, it's not there. It seems it's supposed to be created during the config step, as I don't see it anywhere but the compile/KERNEL directory on other machines. Can anyone point me to some info on how this file is created? I'd love to fix this, as I've spent some serious time on trying to get these patches going (and learned way too much about the patch format) in the past few days... Thanks, Charles --- Charles Sprickman spork@super-g.com --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 8:48:20 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 858B6156E6 for ; Wed, 6 Oct 1999 08:47:11 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id JAA87517; Wed, 6 Oct 1999 09:46:59 -0600 (MDT) (envelope-from ken) Message-Id: <199910061546.JAA87517@panzer.kdm.org> Subject: Re: Applying CAM patches to 2.2-stable In-Reply-To: from spork at "Oct 6, 1999 10:45:52 am" To: spork@super-g.com (spork) Date: Wed, 6 Oct 1999 09:46:59 -0600 (MDT) 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 spork wrote... > Hello, > > I've massaged the CAM patchkit into applying cleanly to a 2.2-stable > source tree from 9/1/99. Most changes were cosmetic, white space, or > "$id" mismatches, nothing beyond that... > > Anyhow, on doing a make depend (after config'ing using config from the > same tree) I get the following: > > ../../pci/aic7870.c:63: aic7xxx_reg.h: No such file or directory > > Of course, it's not there. It seems it's supposed to be created during > the config step, as I don't see it anywhere but the compile/KERNEL > directory on other machines. Can anyone point me to some info on how this > file is created? I'd love to fix this, as I've spent some serious time on > trying to get these patches going (and learned way too much about the > patch format) in the past few days... aic7870.c was the PCI attach code for the ahc driver in the old SCSI layer. It has been replaced by ahc_pci.c in CAM. My guess is that you've still got some things to clean up. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 8:59: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 758DA156E6; Wed, 6 Oct 1999 08:58:48 -0700 (PDT) (envelope-from spork@super-g.com) Received: by super-g.com (Postfix, from userid 1000) id 0B137B91C; Wed, 6 Oct 1999 11:57:57 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id EF02EB91B; Wed, 6 Oct 1999 11:57:56 -0400 (EDT) Date: Wed, 6 Oct 1999 11:57:56 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Mike Tancsa Cc: Stuart Henderson , scsi@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?) In-Reply-To: <3.0.5.32.19990809164854.01c08750@staff.sentex.ca> 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 Mon, 9 Aug 1999, Mike Tancsa wrote: > What I am not clear on from glancing at the mylex site is that they seem to > be cards only and cards with boxes ? Am I right in thinking that you > supply the case ? From the .pdf file Yes, and beyond that there is a model that is simply a "card" for OEM people putting together their own box. We've been buying the one that is in a 5 1/4" full-height drive format. Their webpages generally suck and are out of date. You probably want the DAC-960-SXI-H. > Do you save substantially 'putting it together' yourself ? Probably. We've been putting these inside a few machines (not an external box) for folks who wanted a "RAID solution". It's fast, very fast. Makes the DPT look like a real crawl. We're basically using it more for protection than anything else, but we didn't want to end up with something slower than straight drives off a UW controller. > What sort of price have people paid (in USD), and who is generally a good > outlet to buy from ? I think we paid about $2450 for the SXI-H w/32MB cache. You can probably do better elsewhere, check buy.com or Ingram (if you are or are friendly with a reseller). So an example array came out like so: $2450 SXI-H $1680 6*9GB IBM 34560's $4130 Add a box and you're ready to go... Charles > Thanks for any input anyone can provide on this topic. > > ---Mike > ------------------------------------------------------------------------ > Mike Tancsa, tel 01.519.651.3400 > Network Administrator, mike@sentex.net > Sentex Communications www.sentex.net > Cambridge, Ontario Canada > > > 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 Wed Oct 6 10:43:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 9CCC61572E for ; Wed, 6 Oct 1999 10:42:43 -0700 (PDT) (envelope-from spork@super-g.com) Received: by super-g.com (Postfix, from userid 1000) id 6EFB8B91C; Wed, 6 Oct 1999 13:42:42 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id 5AD37B91B; Wed, 6 Oct 1999 13:42:42 -0400 (EDT) Date: Wed, 6 Oct 1999 13:42:42 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Applying CAM patches to 2.2-stable In-Reply-To: <199910061546.JAA87517@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 On Wed, 6 Oct 1999, Kenneth D. Merry wrote: > spork wrote... > > Hello, > > > > I've massaged the CAM patchkit into applying cleanly to a 2.2-stable > > source tree from 9/1/99. Most changes were cosmetic, white space, or > > "$id" mismatches, nothing beyond that... > > > > Anyhow, on doing a make depend (after config'ing using config from the > > same tree) I get the following: > > > > ../../pci/aic7870.c:63: aic7xxx_reg.h: No such file or directory > > > aic7870.c was the PCI attach code for the ahc driver in the old SCSI layer. > It has been replaced by ahc_pci.c in CAM. > > My guess is that you've still got some things to clean up. The weird thing is that a machine running the 2.2 CAM snapshot has the file after running config on the kernel config file: spork@shell[~/tmp/kern-patch]$ ls /sys/compile/SHELL/aic7xxx aic7xxx.o aic7xxx_reg.h aic7xxx_seq.h and in the original diffs I see this file come up: *** src/sys/conf/files.orig --- src/sys/conf/files (around line 12 or so) + aic7xxx_{seq,reg}.h optional ahc device-driver \ + compile-with "./aicasm ${INCLUDES} -o aic7xxx_seq.h -r aic7xxx_reg.h $S/d ev/aic7xxx/aic7xxx.seq" \ + no-obj no-implicit-rule before-depend \ + clean "aic7xxx_seq.h aic7xxx_reg.h" \ and down around 350 or so: ! pci/ahc_pci.c optional ahc device-driver \ ! dependency "aic7xxx_reg.h $S/pci/ahc_pci.c" Does that make sense? I'm getting this from the original, unaltered diffs for 2.2... Charles > Ken > -- > Kenneth Merry > ken@kdm.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 Wed Oct 6 11:17: 2 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 92C3915136 for ; Wed, 6 Oct 1999 11:16:55 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA88316; Wed, 6 Oct 1999 12:16:29 -0600 (MDT) (envelope-from ken) Message-Id: <199910061816.MAA88316@panzer.kdm.org> Subject: Re: Applying CAM patches to 2.2-stable In-Reply-To: from spork at "Oct 6, 1999 01:42:42 pm" To: spork@super-g.com (spork) Date: Wed, 6 Oct 1999 12:16:29 -0600 (MDT) 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 spork wrote... > On Wed, 6 Oct 1999, Kenneth D. Merry wrote: > > spork wrote... > > > Anyhow, on doing a make depend (after config'ing using config from the > > > same tree) I get the following: > > > > > > ../../pci/aic7870.c:63: aic7xxx_reg.h: No such file or directory > > > > > aic7870.c was the PCI attach code for the ahc driver in the old SCSI layer. > > It has been replaced by ahc_pci.c in CAM. > > > > My guess is that you've still got some things to clean up. > > The weird thing is that a machine running the 2.2 CAM snapshot has the > file after running config on the kernel config file: > > spork@shell[~/tmp/kern-patch]$ ls /sys/compile/SHELL/aic7xxx > aic7xxx.o aic7xxx_reg.h aic7xxx_seq.h > > and in the original diffs I see this file come up: > > *** src/sys/conf/files.orig > --- src/sys/conf/files > > (around line 12 or so) > > + aic7xxx_{seq,reg}.h optional ahc device-driver \ > + compile-with "./aicasm ${INCLUDES} -o aic7xxx_seq.h -r > aic7xxx_reg.h $S/d > ev/aic7xxx/aic7xxx.seq" \ > + no-obj no-implicit-rule before-depend \ > + clean "aic7xxx_seq.h aic7xxx_reg.h" \ > > and down around 350 or so: > > ! pci/ahc_pci.c optional ahc device-driver \ > ! dependency "aic7xxx_reg.h $S/pci/ahc_pci.c" > > Does that make sense? I'm getting this from the original, unaltered diffs > for 2.2... Yes, it makes sense. aic7xxx_{seq,reg}.h are built automatically by aicasm. You should not, however, be compiling aic7870.c. If you are, your setup/patches are broken. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 11:36:38 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 726811572D for ; Wed, 6 Oct 1999 11:36:09 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id MAA25143; Wed, 6 Oct 1999 12:23:35 -0600 (MDT) Date: Wed, 6 Oct 1999 12:23:35 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199910061823.MAA25143@narnia.plutotech.com> To: Vadim Belman Cc: scsi@FreeBSD.org Subject: Re: 'Unexpected busfree' X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <85k8p2vvmt.fsf@eagle.plab.ku.dk> 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 <85k8p2vvmt.fsf@eagle.plab.ku.dk> you wrote: > I wonder if someone can tell me: what kind of error is the > following? > > Unexpected busfree. LASTPHASE == 0x0 > SEQADDR == 0x5e > > And what do I do with it? This means that the bus appeared to go free during the middle of a transaction. In this case, it happened during a DATAOUT phase. Essentially the target hung up without saying good bye first. These kinds of problems can be caused by bad cabling setups. Perhaps the REQ/ACK offset counters got out of sync (initiator did not see a REQ pulse) so the target timedout and ended the connection. It's hard to say without an analyzer. Be sure to use forced perfect terminators, high quality cables, and don't exceed 3m in cable length. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 13:11:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from munin.odin-corporation.com (fredriks-2.pr.mcs.net [205.164.50.242]) by hub.freebsd.org (Postfix) with ESMTP id AF52E15259 for ; Wed, 6 Oct 1999 13:11:46 -0700 (PDT) (envelope-from lars@odin-corporation.com) Received: from odin-corporation.com (localhost [127.0.0.1]) by munin.odin-corporation.com (8.9.3/8.9.1) with ESMTP id PAA05292 for ; Wed, 6 Oct 1999 15:10:20 -0500 (CDT) (envelope-from lars@odin-corporation.com) Message-ID: <37FBACAC.DFBE7736@odin-corporation.com> Date: Wed, 06 Oct 1999 15:10:20 -0500 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: scsi@freebsd.org Subject: Anyone got the scsi interface docs for a Sony SDT-9000 DAT drive? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Subject covers most of it. I was just looking to see if anyone have gotten their hands on the SCSI interface specification/programmer doc for the Sony SDT-9000 DAT drive. Especially the one that covers the 0400 firmware. Or perhaps someone knows where I can get a hold of a copy.... Thanks, Lars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 13:13:44 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 6B77B1576C for ; Wed, 6 Oct 1999 13:12:53 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA01559; Wed, 6 Oct 1999 13:11:46 -0700 Date: Wed, 6 Oct 1999 13:11:46 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: Vadim Belman , scsi@FreeBSD.ORG Subject: Re: 'Unexpected busfree' In-Reply-To: <199910061823.MAA25143@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 <85k8p2vvmt.fsf@eagle.plab.ku.dk> you wrote: > > I wonder if someone can tell me: what kind of error is the > > following? > > > > Unexpected busfree. LASTPHASE == 0x0 > > SEQADDR == 0x5e > > > > And what do I do with it? > > This means that the bus appeared to go free during the middle of a > transaction. In this case, it happened during a DATAOUT phase. > Essentially the target hung up without saying good bye first. > > These kinds of problems can be caused by bad cabling setups. Perhaps > the REQ/ACK offset counters got out of sync (initiator did not see a > REQ pulse) so the target timedout and ended the connection. It's hard > to say without an analyzer. Be sure to use forced perfect terminators, > high quality cables, and don't exceed 3m in cable length. Also, for some older peripherals I've found that if they detect a parity error when receiving data they just drop off the bus rather than go to the bother of completing the command first. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 13:38: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 77BEC1575C for ; Wed, 6 Oct 1999 13:38:00 -0700 (PDT) (envelope-from spork@super-g.com) Received: by super-g.com (Postfix, from userid 1000) id CDF15B91C; Wed, 6 Oct 1999 16:37:59 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id B3B66B91B; Wed, 6 Oct 1999 16:37:59 -0400 (EDT) Date: Wed, 6 Oct 1999 16:37:59 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Applying CAM patches to 2.2-stable In-Reply-To: <199910061816.MAA88316@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 Thanks, found the problem in /usr/src/sys/conf/files... I might as well go ahead and ask, is there going to possibly be another patchkit released for 2.2? Thanks again, Charles On Wed, 6 Oct 1999, Kenneth D. Merry wrote: > spork wrote... > > On Wed, 6 Oct 1999, Kenneth D. Merry wrote: > > > spork wrote... > > > > Anyhow, on doing a make depend (after config'ing using config from the > > > > same tree) I get the following: > > > > > > > > ../../pci/aic7870.c:63: aic7xxx_reg.h: No such file or directory > > > > > > > aic7870.c was the PCI attach code for the ahc driver in the old SCSI layer. > > > It has been replaced by ahc_pci.c in CAM. > > > > > > My guess is that you've still got some things to clean up. > > > > The weird thing is that a machine running the 2.2 CAM snapshot has the > > file after running config on the kernel config file: > > > > spork@shell[~/tmp/kern-patch]$ ls /sys/compile/SHELL/aic7xxx > > aic7xxx.o aic7xxx_reg.h aic7xxx_seq.h > > > > and in the original diffs I see this file come up: > > > > *** src/sys/conf/files.orig > > --- src/sys/conf/files > > > > (around line 12 or so) > > > > + aic7xxx_{seq,reg}.h optional ahc device-driver \ > > + compile-with "./aicasm ${INCLUDES} -o aic7xxx_seq.h -r > > aic7xxx_reg.h $S/d > > ev/aic7xxx/aic7xxx.seq" \ > > + no-obj no-implicit-rule before-depend \ > > + clean "aic7xxx_seq.h aic7xxx_reg.h" \ > > > > and down around 350 or so: > > > > ! pci/ahc_pci.c optional ahc device-driver \ > > ! dependency "aic7xxx_reg.h $S/pci/ahc_pci.c" > > > > Does that make sense? I'm getting this from the original, unaltered diffs > > for 2.2... > > Yes, it makes sense. aic7xxx_{seq,reg}.h are built automatically by > aicasm. > > You should not, however, be compiling aic7870.c. If you are, your > setup/patches are broken. > > Ken > -- > Kenneth Merry > ken@kdm.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 13:43: 4 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 0D1CE151E0 for ; Wed, 6 Oct 1999 13:42:57 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA89423; Wed, 6 Oct 1999 14:42:54 -0600 (MDT) (envelope-from ken) Message-Id: <199910062042.OAA89423@panzer.kdm.org> Subject: Re: Applying CAM patches to 2.2-stable In-Reply-To: from spork at "Oct 6, 1999 04:37:59 pm" To: spork@super-g.com (spork) Date: Wed, 6 Oct 1999 14:42:54 -0600 (MDT) 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 spork wrote... > Thanks, found the problem in /usr/src/sys/conf/files... Cool. > I might as well go ahead and ask, is there going to possibly be another > patchkit released for 2.2? Probably not, unless someone contracts Justin to do it. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 13:54:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front6.grolier.fr (front6.grolier.fr [194.158.96.56]) by hub.freebsd.org (Postfix) with ESMTP id 3E04E1576C for ; Wed, 6 Oct 1999 13:53:24 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-159-183.villette.club-internet.fr [195.36.159.183]) by front6.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id WAA24728 for ; Wed, 6 Oct 1999 22:53:18 +0200 (MET DST) Date: Wed, 6 Oct 1999 23:14:46 +0200 (MET DST) From: Gerard Roudier X-Sender: groudier@localhost To: scsi@FreeBSD.org Subject: sym-0.7.0 available. 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 Hello, I just uploaded latest diff (0.7.0) for the sym_hipd driver: ftp://ftp.tux.org/pub/roudier/drivers/freebsd/experimental/README.sym Change log: * SYM-0.0.0-19990915 Initial release. * SYM-0.1.0-19990919 (diff file PATCH-SYM-0.1.0-19990919 Add NVRAM support for latest Tekram boards using 24c16 EEPROM. * SYM-0.2.0-19990922 (diff file PATCH-SYM-0.2.0-19990922 Add PPR negotiation and Ultra3 DT transfers for the LSI53C1010. The corresponding code is untested since I haven't yet the hardware. But the driver is not broken for current chips. * SYM-0.3.0-19990925 (diff file PATCH-SYM-0.3.0-19990925 Source review. Testing of the QUEUE FULL handling (some fixes applied). * SYM-0.4.0-19990928 (diff file PATCH-SYM-0.4.0-19990928) Fixes, notably the QUEUE FULL handling that requeued everything without telling the XPT about the error. Note that this did not break anything, but the queue depth was never reduced. * SYM-0.5.0-19991001 (diff file PATCH-SYM-0.5..0-19991001) Problem of not discovering LUNs != 0 hopefully fixed. Some other minor fixes. * SYM-0.6.0-19991003 (diff file PATCH-SYM-0.6.0-19991003) Test error recovery pathes and residual calculation. Improve Symbios NVRAM support by applying the SCAN_LUNS flag. The driver answers DEV_NOT_THERE to INQUIRYs for LUNs that are not to be scanned. Switch the driver status for SPI2 support to BETA-RELEASE. * SYM-0.7.0-19991006 (diff file PATCH-SYM-0.7.0-19991006) Add support of the LSI1510D that emulates a 895 (infos sent by Compaq that seems to be the only supplier of this chip) Return CAM_REQ_ABORTED on HS_ABORT host status. Fix a tiny bug that let the driver miss the TAG setting. October 6 1999. "Gerard Roudier" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 14:36:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front4.grolier.fr (front4.grolier.fr [194.158.96.54]) by hub.freebsd.org (Postfix) with ESMTP id 96BF014EA4 for ; Wed, 6 Oct 1999 14:36:14 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-112-249.villette.club-internet.fr [194.158.112.249]) by front4.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id XAA03888; Wed, 6 Oct 1999 23:35:40 +0200 (MET DST) Date: Wed, 6 Oct 1999 23:57:07 +0200 (MET DST) From: Gerard Roudier X-Sender: groudier@localhost To: Matthew Jacob Cc: "Justin T. Gibbs" , Vadim Belman , scsi@FreeBSD.ORG Subject: Re: 'Unexpected busfree' In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 6 Oct 1999, Matthew Jacob wrote: > > In article <85k8p2vvmt.fsf@eagle.plab.ku.dk> you wrote: > > > =09I wonder if someone can tell me: what kind of error is the > > > =09following? > > >=20 > > > Unexpected busfree. LASTPHASE =3D=3D 0x0 > > > SEQADDR =3D=3D 0x5e > > >=20 > > > =09And what do I do with it? > >=20 > > This means that the bus appeared to go free during the middle of a > > transaction. In this case, it happened during a DATAOUT phase. > > Essentially the target hung up without saying good bye first. > >=20 > > These kinds of problems can be caused by bad cabling setups. Perhaps > > the REQ/ACK offset counters got out of sync (initiator did not see a > > REQ pulse) so the target timedout and ended the connection. It's hard > > to say without an analyzer. Be sure to use forced perfect terminators, > > high quality cables, and don't exceed 3m in cable length. >=20 > Also, for some older peripherals I've found that if they detect a parity > error when receiving data they just drop off the bus rather than go to th= e > bother of completing the command first. The behaviour of those old peripherals does not look that bad to me, even if some better one may be possible. Since SCSI parity bit mostly protects against single bit error, a SCSI BUS that experiences oftently SCSI parity errors has some non negligible probability to lead to undetected data corruptions. So, dropping the BUS is such a situation is quite acceptable and warn user about possible BUS problem, provided that the unexpected bus free condition is loudly reported to him by the system.=20 The SCSI device may elect to try to recover by restoring the saved=20 pointers. This may look more user-friendly but will increase the risk of silent data corruption as seen by user. May-be the most clever device decision should be to try asap to complete the command with appropriate sense data, but just dropping the BUS seems to me a more safe device behaviour than trying to recover from a SCSI parity error.=20 G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 14:43:48 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 B86D915163 for ; Wed, 6 Oct 1999 14:43:42 -0700 (PDT) (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 PAA11327; Wed, 6 Oct 1999 15:43:41 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199910062143.PAA11327@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Gerard Roudier Cc: Matthew Jacob , "Justin T. Gibbs" , Vadim Belman , scsi@FreeBSD.ORG Subject: Re: 'Unexpected busfree' In-reply-to: Your message of "Wed, 06 Oct 1999 23:57:07 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Wed, 06 Oct 1999 15:43:41 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Also, for some older peripherals I've found that if they detect a pari= ty >> error when receiving data they just drop off the bus rather than go to= the >> bother of completing the command first. > >The behaviour of those old peripherals does not look that bad to me, >even if some better one may be possible. Reporting sense information exonerates the device from your suspect list.= Without that information, you cannot assume that the device did not simply lose its mind. The sense information will also allow you to attempt to increase the reliability of the connection to the device by lowering the sync rate or reverting to narrow transfers. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 14:43:55 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 1670115163 for ; Wed, 6 Oct 1999 14:43:47 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA01887; Wed, 6 Oct 1999 14:43:36 -0700 Date: Wed, 6 Oct 1999 14:43:36 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Gerard Roudier Cc: "Justin T. Gibbs" , Vadim Belman , scsi@FreeBSD.ORG Subject: Re: 'Unexpected busfree' In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The behaviour of those old peripherals does not look that bad to me, > even if some better one may be possible. > > Since SCSI parity bit mostly protects against single bit error, a SCSI BUS > that experiences oftently SCSI parity errors has some non negligible > probability to lead to undetected data corruptions. So, dropping the BUS > is such a situation is quite acceptable and warn user about possible BUS > problem, provided that the unexpected bus free condition is loudly > reported to him by the system. > > The SCSI device may elect to try to recover by restoring the saved > pointers. This may look more user-friendly but will increase the risk of > silent data corruption as seen by user. May-be the most clever device > decision should be to try asap to complete the command with appropriate > sense data, but just dropping the BUS seems to me a more safe device > behaviour than trying to recover from a SCSI parity error. I agree with you. An unexpected bus free shouldn't be a problem. It does make it difficult to use the correct sense key for the next command though as an unexpected bus free is not an indicator to run Request Sense. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 14:44: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 6E20E14EF9 for ; Wed, 6 Oct 1999 14:44:48 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA01895; Wed, 6 Oct 1999 14:44:33 -0700 Date: Wed, 6 Oct 1999 14:44:33 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: Gerard Roudier , "Justin T. Gibbs" , Vadim Belman , scsi@FreeBSD.ORG Subject: Re: 'Unexpected busfree' In-Reply-To: <199910062143.PAA11327@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 > >> Also, for some older peripherals I've found that if they detect a parity > >> error when receiving data they just drop off the bus rather than go to the > >> bother of completing the command first. > > > >The behaviour of those old peripherals does not look that bad to me, > >even if some better one may be possible. > > Reporting sense information exonerates the device from your suspect list. > Without that information, you cannot assume that the device did not > simply lose its mind. The sense information will also allow you to > attempt to increase the reliability of the connection to the device > by lowering the sync rate or reverting to narrow transfers. Or, for some devices (e.g., ESP100 chips), even going to different onchip signal filtration.... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 6 21:13:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 6931214A26; Wed, 6 Oct 1999 21:13:04 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id XAA23869; Wed, 6 Oct 1999 23:10:33 -0500 (CDT) Date: Wed, 6 Oct 1999 23:10:33 -0500 From: Tim Tsai To: spork Cc: Mike Tancsa , Stuart Henderson , scsi@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?) Message-ID: <19991006231032.A23636@futuresouth.com> References: <3.0.5.32.19990809164854.01c08750@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Note that David Greenman recently wrote that he wasn't happy with Mylex's performance for cdrom.com and has (or is about to) moved to the CMD Viper II series. I am personally waiting for DPT V and Mylex (PCI) drivers. It's really hard to justify the price of external RAID units. Tim On Wed, Oct 06, 1999 at 11:57:56AM -0400, spork wrote: > On Mon, 9 Aug 1999, Mike Tancsa wrote: > > > What I am not clear on from glancing at the mylex site is that they seem to > > be cards only and cards with boxes ? Am I right in thinking that you > > supply the case ? From the .pdf file > > Yes, and beyond that there is a model that is simply a "card" for OEM > people putting together their own box. We've been buying the one that is > in a 5 1/4" full-height drive format. Their webpages generally suck and > are out of date. You probably want the DAC-960-SXI-H. > > > Do you save substantially 'putting it together' yourself ? > > Probably. We've been putting these inside a few machines (not an external > box) for folks who wanted a "RAID solution". It's fast, very fast. Makes > the DPT look like a real crawl. We're basically using it more for > protection than anything else, but we didn't want to end up with something > slower than straight drives off a UW controller. > > > What sort of price have people paid (in USD), and who is generally a good > > outlet to buy from ? > > I think we paid about $2450 for the SXI-H w/32MB cache. You can probably > do better elsewhere, check buy.com or Ingram (if you are or are friendly > with a reseller). > > So an example array came out like so: > > $2450 SXI-H > $1680 6*9GB IBM 34560's > > $4130 > > Add a box and you're ready to go... > > Charles > > > Thanks for any input anyone can provide on this topic. > > > > ---Mike > > ------------------------------------------------------------------------ > > Mike Tancsa, tel 01.519.651.3400 > > Network Administrator, mike@sentex.net > > Sentex Communications www.sentex.net > > Cambridge, Ontario Canada > > > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Oct 7 11:31:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (nat203.183.mpoweredpc.net [142.177.203.183]) by hub.freebsd.org (Postfix) with ESMTP id 84B1C14D38 for ; Thu, 7 Oct 1999 11:31:35 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id PAA62503 for ; Thu, 7 Oct 1999 15:31:31 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 7 Oct 1999 15:31:31 -0300 (ADT) From: The Hermit Hacker To: freebsd-scsi@freebsd.org Subject: DPT Controller options ... one question 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 # DPT_FREELIST_IS_STACK For optimal L{1,2} CPU cache utilization, # enable this option. Otherwise, the transaction # queue is a LIFO. I cannot measure the performance # gain. First part seems to indicate its a good thing to enable, second part seems to indicate it makes no different whether I do or not...*raised eyebrow* Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Oct 7 20:55:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id A075F14F25 for ; Thu, 7 Oct 1999 20:55:42 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 11ZPdd-0004eg-00; Thu, 7 Oct 1999 19:20:05 -0700 Date: Thu, 7 Oct 1999 19:20:04 -0700 (PDT) From: Tom To: The Hermit Hacker Cc: freebsd-scsi@freebsd.org Subject: Re: DPT Controller options ... one question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 7 Oct 1999, The Hermit Hacker wrote: > # DPT_FREELIST_IS_STACK For optimal L{1,2} CPU cache utilization, > # enable this option. Otherwise, the transaction > # queue is a LIFO. I cannot measure the performance > # gain. > > First part seems to indicate its a good thing to enable, second part seems > to indicate it makes no different whether I do or not...*raised eyebrow* As I understand, the feature looked good on the drawing board, but once implemented didn't hold as much benefit as it would thought it could. The feature was left in anyways. As I understand, it makes about 1 to 2% difference. > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Oct 7 21:17:22 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 8DBBC14BDE for ; Thu, 7 Oct 1999 21:17:17 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 11ZPwl-0004fZ-00; Thu, 7 Oct 1999 19:39:51 -0700 Date: Thu, 7 Oct 1999 19:39:50 -0700 (PDT) From: Tom To: The Hermit Hacker Cc: freebsd-scsi@freebsd.org Subject: Re: DPT Controller options ... one question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 8 Oct 1999, The Hermit Hacker wrote: > > Okay, thanks... > > If there are cache's on the DPT controllers, does the OS make use of > that, or is it automagic and transparent to the OS? Just want to make > sure I'm getting full use of these things... > > Thanks... The onboard cache is transparent to the host. Howerver, there are many settings available for tuning it though. You can set things like delay before writing, and maximum amount of cache that can be "dirty" before a flush is forced. Regardless, DPT IV cards are optimized for random access. My DPT IV card never benchmarked well, but on a mail server, it always exceeded my expectations. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Oct 7 23:42:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (nat203.183.mpoweredpc.net [142.177.203.183]) by hub.freebsd.org (Postfix) with ESMTP id CD03114CC3 for ; Thu, 7 Oct 1999 23:42:31 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id BAA65446; Fri, 8 Oct 1999 01:07:21 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Oct 1999 01:07:21 -0300 (ADT) From: The Hermit Hacker To: Tom Cc: freebsd-scsi@freebsd.org Subject: Re: DPT Controller options ... one question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Okay, thanks... If there are cache's on the DPT controllers, does the OS make use of that, or is it automagic and transparent to the OS? Just want to make sure I'm getting full use of these things... Thanks... On Thu, 7 Oct 1999, Tom wrote: > > On Thu, 7 Oct 1999, The Hermit Hacker wrote: > > > # DPT_FREELIST_IS_STACK For optimal L{1,2} CPU cache utilization, > > # enable this option. Otherwise, the transaction > > # queue is a LIFO. I cannot measure the performance > > # gain. > > > > First part seems to indicate its a good thing to enable, second part seems > > to indicate it makes no different whether I do or not...*raised eyebrow* > > As I understand, the feature looked good on the drawing board, but once > implemented didn't hold as much benefit as it would thought it could. The > feature was left in anyways. As I understand, it makes about 1 to 2% > difference. > > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy > > Systems Administrator @ hub.org > > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > Tom > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Oct 8 0: 3:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id A151514DC5 for ; Fri, 8 Oct 1999 00:03:38 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA97636; Fri, 8 Oct 1999 16:33:16 +0930 (CST) Date: Fri, 8 Oct 1999 16:33:16 +0930 From: Greg Lehey To: Tom Cc: The Hermit Hacker , freebsd-scsi@FreeBSD.ORG Subject: Re: DPT Controller options ... one question Message-ID: <19991008163316.E78191@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thursday, 7 October 1999 at 19:39:50 -0700, Tom wrote: > > On Fri, 8 Oct 1999, The Hermit Hacker wrote: > >> >> Okay, thanks... >> >> If there are cache's on the DPT controllers, does the OS make use of >> that, or is it automagic and transparent to the OS? Just want to make >> sure I'm getting full use of these things... >> >> Thanks... > > The onboard cache is transparent to the host. Howerver, there are many > settings available for tuning it though. You can set things like delay > before writing, and maximum amount of cache that can be "dirty" before a > flush is forced. Regardless, DPT IV cards are optimized for random > access. My DPT IV card never benchmarked well, but on a mail server, it > always exceeded my expectations. The general consensus is that the DPT IV is a very poor performer. Mike Smith has just committed drivers for AMI and Mylex controllers, which work a little better. So far nobody has been overwhelmed by the performance of any of them. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Oct 8 11: 0:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from tinker.com (troll.tinker.com [204.214.7.146]) by hub.freebsd.org (Postfix) with ESMTP id E282B1503E for ; Fri, 8 Oct 1999 11:00:36 -0700 (PDT) (envelope-from kim@tinker.com) Received: by localhost (8.8.5/8.8.5) Received: by mail.tinker.com via smap (V2.0) id xma012520; Fri Oct 8 12:37:49 1999 Received: by localhost (8.8.8/8.8.8) id NAA00497 for ; Fri, 8 Oct 1999 13:00:38 -0500 (CDT) Message-ID: <37FE3166.8FA01938@tinker.com> Date: Fri, 08 Oct 1999 13:01:10 -0500 From: Kim Shrier Organization: Shrier and Deihl X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: scsi@freebsd.org Subject: Driver for GDT6517RD RAID controller Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a client that has a Compaq Proliant PL1600R that he wants to put FreeBSD on. It has a GDT6517RD RAID controller in it and I don't see any support for it in LINT. Is there a device driver for this thing? Thanks, Kim Shrier -- Kim Shrier - principal, Shrier and Deihl - mailto:kim@tinker.com Remote Unix Network Admin, Security, Internet Software Development Tinker Internet Services - Superior FreeBSD-based Web Hosting http://www.tinker.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Oct 8 11:43:37 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id F40C21549F for ; Fri, 8 Oct 1999 11:43:35 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA00821; Fri, 8 Oct 1999 11:35:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910081835.LAA00821@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kim Shrier Cc: scsi@freebsd.org Subject: Re: Driver for GDT6517RD RAID controller In-reply-to: Your message of "Fri, 08 Oct 1999 13:01:10 CDT." <37FE3166.8FA01938@tinker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Oct 1999 11:35:52 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have a client that has a Compaq Proliant PL1600R that he wants > to put FreeBSD on. It has a GDT6517RD RAID controller in it and > I don't see any support for it in LINT. Is there a device driver > for this thing? This is an ICP Vortex controller, and no, we don't have any support yet. If someone sends me one, or I can find one secondhand at a reasonable price, support will be added promptly. -- \\ 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 Fri Oct 8 12:23: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 4BA7A14EB0 for ; Fri, 8 Oct 1999 12:22:55 -0700 (PDT) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id PAA28421 for ; Fri, 8 Oct 1999 15:18:04 -0400 (EDT) Reply-To: Randell Jesup To: scsi@FreeBSD.ORG Subject: Re: Driver for GDT6517RD RAID controller References: <199910081835.LAA00821@dingo.cdrom.com> From: Randell Jesup Date: 08 Oct 1999 15:18:06 +0000 In-Reply-To: Mike Smith's message of "Fri, 08 Oct 1999 11:35:52 -0700" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gerard Roudier writes: >I invite you to read my previous postings about this topic and will just >post the following output from iostat I got using 2 10K disk on a single >SYM53C896 channel (I have described the test conditions in a previous >posting): > >(Cheetah2 LVD + DRVS LVD) > > tty da0 da1 da2 cpu > tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id > 0 0 4.00 4461 17.43 4.00 4460 17.42 0.00 0 0.00 3 0 56 14 27 > 0 0 4.00 4461 17.42 4.00 4462 17.43 0.00 0 0.00 3 0 52 16 29 >The sym_hipd driver is also very fast using 53C875 and 895 controllers. I >cannot perform CCD testings at the moment since I donnot have time enough >for that, but I have some additionnal benchmarks I could flood the list >with. Nice results. I haven't played with 53c8xx chips, but I wrote some very fast drivers for the 53c7xx chips a long time ago ('93) for the Amiga. I'd planned to support full CAM for that and for the 53c90(? I forget), but never got the time to finish it (I wrote/tested the XPT and some other parts (partial SIM)). (Amiga's had a mostly-equivalent of CAM called SCSIDirect.) >On the result above (sequential read), may-be disconnections are not so >frequent, but I know the reselection path of the sym_hipd driver enough >to claim that this path is also very fast and certainly faster than the >ncr since it is just O(1) for both SCRIPTS and C code with regards to >the number of concurrent IOs (all that from 810A to C1010). The 53c7xx was missing some important abilities (like an ALU!), but you could do some cool things to avoid interrupting the processor. In particular, I supported reselection without processor interrupts - disconnect would cause modifications to the code-path for reselection. (The structures for tracking active requests included code used to determine if that was the request asking for reselection; on disconnect it was linked into the tree of code for "we have a reconnect"). This included tagged commands. I still have the code kicking around somewhere. I'm not sure my setup was O(1), but it was pretty good (probably O(log(n)), maybe O(n) where n is number of active requests per target. If it's O(n), then making it O(log(n)) would be trivial by using a (b)tree instead of a list. FYI, I was also on the "section 10" CAM working group that rewrote the target-mode part of CAM from the ground up after I discovered it was totally un-implementable and informed them. Target-mode is potentially handy for very-high-speed short-distance networking, as well as for situations where you want machines to have direct access the same drives, etc. I know DEC implemented section 10 of CAM (several of the other section 10 people were from DEC). I'm now working using FreeBSD machines, and figured I'd see what was up in the disk-driver area of FreeBSD. I also wrote all the IDE drivers for Commodore (based on SCSI emulation - I made a SCSIDirect (CAM-like)-to-IDE conversion layer, so IDE drives appeared to be SCSI. Ditto for ATAPI. I was also the primary FS person in later days there, and added the "dir-cache" extensions (and something that was mostly the equivalent to "soft-updates"), and worked on the peer-to-peer networking code (which used RDP). -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Oct 8 17:27: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 60D8A14DE5 for ; Fri, 8 Oct 1999 17:26:56 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id UAA19282; Fri, 8 Oct 1999 20:26:51 -0400 (EDT) Date: Fri, 8 Oct 1999 20:26:50 -0400 (EDT) From: "Matthew N. Dodd" To: Randell Jesup Cc: scsi@FreeBSD.ORG Subject: Re: Driver for GDT6517RD RAID controller In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 8 Oct 1999, Randell Jesup wrote: > Nice results. I haven't played with 53c8xx chips, but I wrote some > very fast drivers for the 53c7xx chips a long time ago ('93) for the > Amiga. I'd be interested in hearing your observation of the differences between the 53c7xx and the 53c8xx chips as I'd really like to see the existing NCR driver support them. I suspect that all but the very early 53c700 and 710 chips would require minimal changes. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Oct 8 18:41:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id EA6A214F1A for ; Fri, 8 Oct 1999 18:41:41 -0700 (PDT) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id VAA08900; Fri, 8 Oct 1999 21:36:52 -0400 (EDT) Reply-To: Randell Jesup To: "Matthew N. Dodd" Cc: scsi@FreeBSD.ORG Subject: Re: Driver for GDT6517RD RAID controller References: From: Randell Jesup Date: 08 Oct 1999 21:36:54 +0000 In-Reply-To: "Matthew N. Dodd"'s message of "Fri, 8 Oct 1999 20:26:50 -0400 (EDT)" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Matthew N. Dodd" writes: >On 8 Oct 1999, Randell Jesup wrote: >> Nice results. I haven't played with 53c8xx chips, but I wrote some >> very fast drivers for the 53c7xx chips a long time ago ('93) for the >> Amiga. > >I'd be interested in hearing your observation of the differences between >the 53c7xx and the 53c8xx chips as I'd really like to see the existing NCR >driver support them. > >I suspect that all but the very early 53c700 and 710 chips would require >minimal changes. The 53c700 wasn't really usable for a 680x0 architecture machine (and had some other serious problems for us). We used the 53c710 in the A4000T (A4000 tower) and A4091 Zorro-III card. Are there docs on the differences, or at least on-line or available docs on the 53c8xx chips? Weren't the x810's 710's with built-in PCI bus support? -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Oct 8 18:44:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id E830D14D60 for ; Fri, 8 Oct 1999 18:44:38 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id VAA22493; Fri, 8 Oct 1999 21:44:35 -0400 (EDT) Date: Fri, 8 Oct 1999 21:44:35 -0400 (EDT) From: "Matthew N. Dodd" To: Randell Jesup Cc: scsi@FreeBSD.ORG Subject: Re: Driver for GDT6517RD RAID controller In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 8 Oct 1999, Randell Jesup wrote: > Are there docs on the differences, or at least on-line or available > docs on the 53c8xx chips? Weren't the x810's 710's with built-in PCI > bus support? Essentially. I was kind of hopeing you'd glance at the NCR driver and see if anything looked amiss. Spliting out the bus front ends isn't a big problem but I really don't have the cycles to wrap my head around the 53c7xx docs ATM. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Oct 8 19: 7: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 8C135152CC for ; Fri, 8 Oct 1999 19:07:01 -0700 (PDT) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id WAA09285; Fri, 8 Oct 1999 22:02:08 -0400 (EDT) Reply-To: Randell Jesup To: "Matthew N. Dodd" Cc: scsi@FreeBSD.ORG Subject: Re: Driver for GDT6517RD RAID controller References: From: Randell Jesup Date: 08 Oct 1999 22:02:09 +0000 In-Reply-To: "Matthew N. Dodd"'s message of "Fri, 8 Oct 1999 21:44:35 -0400 (EDT)" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Matthew N. Dodd" writes: >On 8 Oct 1999, Randell Jesup wrote: >> Are there docs on the differences, or at least on-line or available >> docs on the 53c8xx chips? Weren't the x810's 710's with built-in PCI >> bus support? > >Essentially. I was kind of hopeing you'd glance at the NCR driver and see >if anything looked amiss. Spliting out the bus front ends isn't a big >problem but I really don't have the cycles to wrap my head around the >53c7xx docs ATM. Ok, I'll glance at them. Forgive me if I end up shuddering; I've seen some of their code before. I might end up rewriting it.... or at least incorporating some of my ideas to minimize interrupts. (interrupting the CPU for SCSI state changes: bad). For many IO's, I was able to take a single interrupt (completion); few were more than 2 ints (one for disconnect after a transfer (damn '710 processor can't do math), one for completion - no ints for reselects, and I think none for disconnect before any bytes are xferred - I forget.) -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 9 4:41:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front7.grolier.fr (front7.grolier.fr [194.158.96.57]) by hub.freebsd.org (Postfix) with ESMTP id 486CC14C25 for ; Sat, 9 Oct 1999 04:40:55 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-105-184.villette.club-internet.fr [194.158.105.184]) by front7.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id NAA17493; Sat, 9 Oct 1999 13:40:48 +0200 (MET DST) Date: Sat, 9 Oct 1999 14:02:25 +0200 (MET DST) From: Gerard Roudier X-Sender: groudier@localhost To: "Matthew N. Dodd" Cc: Randell Jesup , scsi@FreeBSD.ORG Subject: Re: Driver for GDT6517RD RAID controller In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 8 Oct 1999, Matthew N. Dodd wrote: > On 8 Oct 1999, Randell Jesup wrote: > > Nice results. I haven't played with 53c8xx chips, but I wrote some > > very fast drivers for the 53c7xx chips a long time ago ('93) for the > > Amiga. >=20 > I'd be interested in hearing your observation of the differences between > the 53c7xx and the 53c8xx chips as I'd really like to see the existing NC= R > driver support them. One year ago, I asked SYMBIOS about their opinion of having good support under Linux for 53c710 and later 7xx chips (basically the 720). They were absolutely not interested in this and even discouraged me to provide such support. The FreeBSD case should not be that different in this regard. In fact, the 7xx chips are only used nowadays as generic SCSI core for some intelligent controllers. > I suspect that all but the very early 53c700 and 710 chips would require > minimal changes. The 53c700 must be considered as having never existed. ;) About the 710 and later 7xx chips, speaking of a driver for this family does not make sense, since the system BUS stuff allows and requires proprietary implementations from the system hardware. Since it seems that machines that use on-board 7xx controllers are old, the needed documentation may just be no longer available. A driver that will separate system BUS code and SCSI core code may allow to support some set of 53c7xx based controllers. The 53c7xx support looks like that under Linux, for example. Basically, a SIM that supports 53c810 rev 1 can support 53c710 and later 53c7xx chips with minimal changes, provided that the BUS stuff be added or changed. The stock ncr driver supports the 53c810 rev 1, so starting from this code should be just fine for some 710 support.=20 No chance at all with the sym_hipd driver I am currently developping, since the aim of this driver is to take advantages of recent chips and PCI bus. Now, my 0.02 euro opinion about this topic: I am always been amazed by people who wants latest softwares to support old hardwares. If such compatibilty constraints had been always applied, may-be the fastest hardware nowadays would be a Z80 at 5 GigaHz and graphic would be some incredibly fast 16 colors VGA. ;-) Note that the poorness of latest IA32 arch we have to deal with may well be due to some backward compatibility + $$ issues. IMO, the 53c7xx parts are now material for history books and IT museums, and an O/S that does not provide support yet for these chips should not consider adding such a support, unless some driver magically be provided by some volonteer and be actually _maintained_.=20 G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 9 12:33:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 3152314DB5 for ; Sat, 9 Oct 1999 12:33:56 -0700 (PDT) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id PAA01219; Sat, 9 Oct 1999 15:29:12 -0400 (EDT) Reply-To: Randell Jesup To: Gerard Roudier Cc: "Matthew N. Dodd" , scsi@FreeBSD.ORG Subject: Re: Driver for GDT6517RD RAID controller References: From: Randell Jesup Date: 09 Oct 1999 15:29:10 +0000 In-Reply-To: Gerard Roudier's message of "Sat, 9 Oct 1999 14:02:25 +0200 (MET DST)" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gerard Roudier writes: >On Fri, 8 Oct 1999, Matthew N. Dodd wrote: >> I suspect that all but the very early 53c700 and 710 chips would require >> minimal changes. > >The 53c700 must be considered as having never existed. ;) Quite true. :-) >About the 710 and later 7xx chips, speaking of a driver for this family >does not make sense, since the system BUS stuff allows and requires >proprietary implementations from the system hardware. Since it seems that >machines that use on-board 7xx controllers are old, the needed >documentation may just be no longer available. Quite true; I know the c710 was used on about 5 or 6 different Amiga SCSI boards (including the ones I wrote the software for), but I don't know how much it was used in the PC world, and I don't know if anyone would care. >A driver that will separate system BUS code and SCSI core code may allow >to support some set of 53c7xx based controllers. The 53c7xx support looks >like that under Linux, for example. There's support for c710's in NetBSD as well (at least in the Amiga port). I haven't looked at it. If it's based on the NCR reference driver examples, it can't perform all that well. Their reference drivers for PC's didn't come close to using all the possible performance/power in the c710, especially the ability to execute (really simplistic) code. >Basically, a SIM that supports 53c810 rev 1 can support 53c710 and later >53c7xx chips with minimal changes, provided that the BUS stuff be added or >changed. The stock ncr driver supports the 53c810 rev 1, so starting from >this code should be just fine for some 710 support. Sounds exactly as I'd suspect. >Now, my 0.02 euro opinion about this topic: >I am always been amazed by people who wants latest softwares to support >old hardwares. If such compatibilty constraints had been always applied, >may-be the fastest hardware nowadays would be a Z80 at 5 GigaHz and >graphic would be some incredibly fast 16 colors VGA. ;-) :-) There are some good reasons: a LOT of us over here have older (once-powerful) machines and boards hanging around, and we'd like to get some use out of them. Also, machines used (or donated to) charities and the like are often old or very old, and they want to be able to use them to get something good done without having to buy new $$$ machines every year or two. One doesn't _need_ a PIII/450 w/ 64MB, 20GB disk and a SCSI ultra-wide controller to send email/browse/serve pages (ok, maybe with Microsoft/IE/etc, but not with BSD). Others use them for NAT's, or dedicated firewall/router/proxies, etc. Again, massive horsepower isn't needed. Sometimes it's just for amusement. I have a computer museum in my basement with multiple Sun 2/120's (68010@12MHz), a DEC PDP 11/23, TRS80 model 1, Mac+, Sage, Amigas of all sorts (up to 50MHz 68040 A4000T), Apple II, Pet's, C64's, C128's, etc. >IMO, the 53c7xx parts are now material for history books and IT museums, >and an O/S that does not provide support yet for these chips should not >consider adding such a support, unless some driver magically be provided >by some volonteer and be actually _maintained_. Sure. In this case, if someone had docs on the bus interface for a 710-based card, and people had some real use for a driver for them (I don't know if that's true), it probably wouldn't be hard to modify an '810 driver to support it. I didn't have any real plans to do so when I joined this group, but Matt Dodd asked me to look into how easy it would be, and that's not a bad way to get a handle on how SCSI drivers under FreeBSD work. My main interests lie more in performance, support for weird-ass SCSI devices (I learned a LOT being the primary SCSI person at Commodore, and also in qualifying drives for production), and finding out if FreeBSD supports Section 10 of CAM (target mode), since I was one of the people who wrote that section. If it doesn't, I may look at adding support to (a) SIM for that. I had some of the (NCR) code written to do so for the 710; that code might be applicable, or serve as a guideline. Admittedly, my specialized knowledge of the 33c93(b) and it's myriad bugs and gotcha's probably isn't greatly useful.... ;-) -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 9 15:37:46 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 ED56F151F1 for ; Sat, 9 Oct 1999 15:37:27 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA09565; Sat, 9 Oct 1999 16:37:16 -0600 (MDT) (envelope-from ken) Message-Id: <199910092237.QAA09565@panzer.kdm.org> Subject: Re: Driver for GDT6517RD RAID controller In-Reply-To: from Randell Jesup at "Oct 9, 1999 03:29:10 pm" To: rjesup@wgate.com (Randell Jesup) Date: Sat, 9 Oct 1999 16:37:16 -0600 (MDT) Cc: groudier@club-internet.fr (Gerard Roudier), winter@jurai.net (Matthew N. Dodd), 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 Randell Jesup wrote... > My main interests lie more in performance, support for weird-ass > SCSI devices (I learned a LOT being the primary SCSI person at Commodore, > and also in qualifying drives for production), and finding out if FreeBSD > supports Section 10 of CAM (target mode), since I was one of the people who > wrote that section. If it doesn't, I may look at adding support to (a) SIM > for that. I had some of the (NCR) code written to do so for the 710; that > code might be applicable, or serve as a guideline. It looks like target mode is covered in section 11 of the CAM-2 spec and section 12 of the CAM-3 spec. In any case, FreeBSD does support target mode. The only chips it currently works for are the Adaptec 7890/1 and 7896/7. It may also work on the 7895, although I'm not positive about that. (Justin would know.) Those are the only Adaptec chips with the instruction space needed to fit the target mode Adaptec firmware. 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 Oct 9 17: 7:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 6A5FB14DB5 for ; Sat, 9 Oct 1999 17:07:17 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11a6WD-0001Gy-00 for freebsd-scsi@freebsd.org; Sat, 09 Oct 1999 17:07:17 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-scsi@freebsd.org Subject: softupdates Message-Id: Date: Sat, 09 Oct 1999 17:07:17 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org how can i tell for which partitons softupdates are enabled? would like to know for non-scsi as well. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 9 17:20: 4 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 BF43914CF0 for ; Sat, 9 Oct 1999 17:20:02 -0700 (PDT) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id RAA53971; Sat, 9 Oct 1999 17:15:13 -0700 (PDT) Date: Sat, 9 Oct 1999 17:15:04 -0700 (PDT) From: Julian Elischer X-Sender: julian@home.elischer.org To: Randy Bush Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: softupdates In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org soft updates is independent of disk type. it is a feature of teh filesystem code. The 'mount' command can tell you what filesystems are mounted Soft updates. e.g julian@home:mount /dev/sd1s1a on / (local, writes: sync 43 async 31702) /dev/sd1s1d on /tmp (local, soft-updates, writes: sync 109 async 2598) /dev/sd1s1e on /var (local, soft-updates, writes: sync 1021 async 45317) /dev/sd2s1d on /usr (local, soft-updates, writes: sync 5034 async 345844) /dev/sd0s2a on /usr/obj (local, soft-updates, writes: sync 2 async 5558) /dev/sd2s1e on /free3 (local, writes: sync 2 async 35) /dev/sd1s1g on /usr/local (local, soft-updates, writes: sync 2 async 5379) /dev/sd1s1f on /free1 (local, writes: sync 2 async 35) procfs on /proc (local) use tunefs(8) to enable or disable softupdates. julian On Sat, 9 Oct 1999, Randy Bush wrote: > how can i tell for which partitons softupdates are enabled? > > would like to know for non-scsi as well. > > randy > > > 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 Oct 9 17:33:12 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id CFCCD14C80 for ; Sat, 9 Oct 1999 17:33:10 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11a6vF-0000Ns-00; Sat, 09 Oct 1999 17:33:09 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Julian Elischer Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: softupdates References: Message-Id: Date: Sat, 09 Oct 1999 17:33:09 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The 'mount' command can tell you what filesystems are mounted Soft > updates. thanks. > use tunefs(8) to enable or disable softupdates. execpt i never have figured out how to make it work for the root partition. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 9 17:40: 8 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 AD5C814D75 for ; Sat, 9 Oct 1999 17:40:05 -0700 (PDT) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id RAA54322; Sat, 9 Oct 1999 17:38:59 -0700 (PDT) Date: Sat, 9 Oct 1999 17:38:50 -0700 (PDT) From: Julian Elischer X-Sender: julian@home.elischer.org To: Randy Bush Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: softupdates In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I believe that louqi made a change so that you can now do it from single user mode, while the root is still read-only. The brute force method is to boot single user.. (with readonly root) enable with tunefs. hit reset button. On Sat, 9 Oct 1999, Randy Bush wrote: > > The 'mount' command can tell you what filesystems are mounted Soft > > updates. > > thanks. > > > use tunefs(8) to enable or disable softupdates. > > execpt i never have figured out how to make it work for the root partition. > > randy > > > 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 Oct 9 17:41:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from FreeBSD.ORG (ppp28-besancon.isdnet.net [195.154.11.235]) by hub.freebsd.org (Postfix) with ESMTP id E6EB415161 for ; Sat, 9 Oct 1999 17:41:13 -0700 (PDT) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.3) id CAA95951; Sun, 10 Oct 1999 02:41:52 +0200 (MET DST) (envelope-from jmz@FreeBSD.ORG) Date: Sun, 10 Oct 1999 02:41:52 +0200 (MET DST) Message-Id: <199910100041.CAA95951@qix.jmz.org> From: Jean-Marc Zucconi To: randy@psg.com Cc: julian@whistle.com, freebsd-scsi@FreeBSD.ORG In-reply-to: (message from Randy Bush on Sat, 09 Oct 1999 17:33:09 -0700) Subject: Re: softupdates X-Mailer: Emacs References: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> Randy Bush writes: >> The 'mount' command can tell you what filesystems are mounted Soft >> updates. > thanks. >> use tunefs(8) to enable or disable softupdates. > execpt i never have figured out how to make it work for the root partition. Boot in single user mode and then '/sbin/tunefs -n enable /' It worked for me. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@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 Oct 9 17:42: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 21453150C3; Sat, 9 Oct 1999 17:42:01 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11a73p-0007GY-00; Sat, 09 Oct 1999 17:42:01 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jean-Marc Zucconi Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: softupdates References: <199910100041.CAA95951@qix.jmz.org> Message-Id: Date: Sat, 09 Oct 1999 17:42:01 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Boot in single user mode and then '/sbin/tunefs -n enable /' > It worked for me. did that. but a long time ago. will try again with current. thanks. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 9 19: 9:13 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id B9347154A7 for ; Sat, 9 Oct 1999 19:09:10 -0700 (PDT) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id WAA08308; Sat, 9 Oct 1999 22:04:27 -0400 (EDT) Reply-To: Randell Jesup To: "Kenneth D. Merry" Cc: groudier@club-internet.fr (Gerard Roudier), winter@jurai.net (Matthew N. Dodd), scsi@FreeBSD.ORG Subject: Re: Driver for GDT6517RD RAID controller References: <199910092237.QAA09565@panzer.kdm.org> From: Randell Jesup Date: 09 Oct 1999 22:04:24 +0000 In-Reply-To: "Kenneth D. Merry"'s message of "Sat, 9 Oct 1999 16:37:16 -0600 (MDT)" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" writes: >> and also in qualifying drives for production), and finding out if FreeBSD >> supports Section 10 of CAM (target mode), since I was one of the people who >> wrote that section. If it doesn't, I may look at adding support to (a) SIM >> for that. I had some of the (NCR) code written to do so for the 710; that >> code might be applicable, or serve as a guideline. > >It looks like target mode is covered in section 11 of the CAM-2 spec and >section 12 of the CAM-3 spec. Aha, they renumbered the sections from between the CAM2 draft and final I guess (it's been a while). We did a total rewrite of the section; the original draft was totally non-implementable (and pretty useless even if you worked around the problems). >In any case, FreeBSD does support target mode. The only chips it currently >works for are the Adaptec 7890/1 and 7896/7. It may also work on the 7895, >although I'm not positive about that. (Justin would know.) Those are the >only Adaptec chips with the instruction space needed to fit the target mode >Adaptec firmware. Cool. Perhaps I'll look at adding target mode to some of the NCR 53xNNN* chips; they certainly can support it. Thanks for the info. Has anyone here used target-mode? Or written an IP transport layer on top of it? -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 9 19:17: 0 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 6E03E14D45 for ; Sat, 9 Oct 1999 19:16:57 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA10353; Sat, 9 Oct 1999 20:16:50 -0600 (MDT) (envelope-from ken) Message-Id: <199910100216.UAA10353@panzer.kdm.org> Subject: Re: Driver for GDT6517RD RAID controller In-Reply-To: from Randell Jesup at "Oct 9, 1999 10:04:24 pm" To: rjesup@wgate.com (Randell Jesup) Date: Sat, 9 Oct 1999 20:16:50 -0600 (MDT) Cc: groudier@club-internet.fr (Gerard Roudier), winter@jurai.net (Matthew N. Dodd), 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 Randell Jesup wrote... > "Kenneth D. Merry" writes: > >In any case, FreeBSD does support target mode. The only chips it currently > >works for are the Adaptec 7890/1 and 7896/7. It may also work on the 7895, > >although I'm not positive about that. (Justin would know.) Those are the > >only Adaptec chips with the instruction space needed to fit the target mode > >Adaptec firmware. > > Cool. Perhaps I'll look at adding target mode to some of the > NCR 53xNNN* chips; they certainly can support it. Thanks for the info. You should probably coordinate with Gerard Roudier, and probably Justin Gibbs as well. > Has anyone here used target-mode? Or written an IP transport layer > on top of it? Justin has used target mode. (Obviously, since he wrote the Adaptec driver support for it.) I think his setup was/is primarily processor target devices on both ends. No one (as far as I know) has written an IP transport layer on top of it. 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 Oct 9 20:55:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 7A5A014D8C for ; Sat, 9 Oct 1999 20:55:40 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id XAA22685; Sat, 9 Oct 1999 23:54:18 -0400 (EDT) Date: Sat, 9 Oct 1999 23:54:18 -0400 (EDT) From: "Matthew N. Dodd" To: Randell Jesup Cc: Gerard Roudier , scsi@FreeBSD.ORG Subject: Re: Driver for GDT6517RD RAID controller In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 9 Oct 1999, Randell Jesup wrote: > Sure. In this case, if someone had docs on the bus interface for a > 710-based card, and people had some real use for a driver for them (I > don't know if that's true), it probably wouldn't be hard to modify an > '810 driver to support it. I didn't have any real plans to do so when > I joined this group, but Matt Dodd asked me to look into how easy it > would be, and that's not a bad way to get a handle on how SCSI drivers > under FreeBSD work. I've taken a look at the NCR driver and my conclusion, outside of any SIM issues is that 2 things need to happen. 1. The NCR driver needs to be converted to bus_space. Since the driver currently uses a number of macros to do various inb/outb functions this won't be all that difficult but will involve a bit of cleanup, mostly tedious. I suggest that such cleanup move relevent sections of the defines to ncr_reg.h, and the shared struct definitions to ncr_var.h. Currently ncrreg.h has some content that would go in one or the other. 2. The NCR driver needs be converted to use newbus, not the legacy shims it is currently using. This would give us a chance to rip all of the PCI front end code out and place it in a separate file (ncr_pci.c) This would also mean that the 'generic' ncr_attach() functionality be isolated from the new ncr_pci_attach(). If someone wants to start working on this I will make myself available for newbus related questions and will also provide EISA bus front ends for the various onboard and expansion 53c7xx based boards I've got laying around. Since the 53c[78]xx chips either have onboad PCI interfacing logic, or make use of fairly standard bus interface logic I don't think that the actual bus specific bits will be anything more than bus_space and attention to proper alignment. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 9 23:21:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4261A1513E for ; Sat, 9 Oct 1999 23:21:26 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA10004 for ; Sat, 9 Oct 1999 23:21:25 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA00729 for scsi@freebsd.org; Sat, 9 Oct 1999 23:21:25 -0700 (PDT) (envelope-from obrien) Date: Sat, 9 Oct 1999 23:21:25 -0700 From: "David O'Brien" To: scsi@freebsd.org Subject: CAM hanging and not reseting properly on 2940UW Message-ID: <19991009232125.A693@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My system has hung twice tonight -- running X, and find a rouge process is stating stuff in / and causes one of the CDROM drives to spin up and things "hang". I Ctrl-Alt-F1 to get to the real console and see: (cd1:ahc0:0:5:0): SCB 0x16 - timed out in datain phase, SEQADDR == 0x110 (cd1:ahc0:0:5:0): BDR message in message buffer (cd1:ahc0:0:5:0): SCB 0x16 - timed out in datain phase, SEQADDR == 0x10f (cd1:ahc0:0:5:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 17SCBs aborted Then the machine is hung. Most all keyboard input is ignored in the console. I can "scroll lock" and scroll back to see console messages. Hit "scroll lock" again, and no input accepted. I cannot Ctrl-Alt-ESC to enter the debugger. Nor is Ctrl-Alt-Del accepted. I can how however Alt-Fx to enter other virtual consoles and keyboard input is accpted -- that is until what is typed causes the a disk access. Shouldn't CAM reset the SCSI bus and recover from the above errors? I tried powering down & up the CDROM drive and that didn't change anything. Is this a bug, or just life? FreeBSD 4.0-CURRENT #20: Sun Oct 3 14:30:16 PDT 1999 ... ahc0: irq 15 at device 9.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs (this controlers has BIOS version 1.23) ncr0: irq 11 at device 10.0 on pci0 ... Waiting 2 seconds for SCSI devices to settle sa0 at ncr0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 8) da22 at ncr0 bus 0 target 2 lun 0 da22: Fixed Direct Access SCSI-2 device da22: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da22: 2049MB (4197520 512 byte sectors: 255H 63S/T 261C) da23 at ncr0 bus 0 target 3 lun 0 da23: Fixed Direct Access SCSI-2 device da23: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da23: 2033MB (4165272 512 byte sectors: 255H 63S/T 259C) da21 at ncr0 bus 0 target 1 lun 0 da21: Fixed Direct Access SCSI-2 device da21: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da21: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) da9 at ahc0 bus 0 target 9 lun 0 da9: Fixed Direct Access SCSI-2 device da9: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da9: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) da8 at ahc0 bus 0 target 8 lun 0 da8: Fixed Direct Access SCSI-2 device da8: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da8: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da10 at ncr0 bus 0 target 0 lun 0 da10: Fixed Direct Access SCSI-2 device da10: 10.000MB/s transfers (10.000MHz, offset 16), Tagged Queueing Enabled da10: 4303MB (8813870 512 byte sectors: 255H 63S/T 548C) ccd0-3: Concatenated disk drivers cd2 at ahc0 bus 0 target 6 lun 0 cd2: Removable CD-ROM SCSI-2 device cd2: 5.000MB/s transfers (5.000MHz, offset 15) cd2: cd present [298211 x 2048 byte records] cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: cd present [316874 x 2048 byte records] cd1 at ahc0 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message