From owner-freebsd-scsi Sun Sep 13 05:22:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26006 for freebsd-scsi-outgoing; Sun, 13 Sep 1998 05:22:17 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA26001 for ; Sun, 13 Sep 1998 05:22:13 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA02204 (5.67b/IDA-1.5); Sun, 13 Sep 1998 14:19:23 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id LAA25506; Sun, 13 Sep 1998 11:14:00 +0200 (CEST) From: Wilko Bulte Message-Id: <199809130914.LAA25506@yedi.iaf.nl> Subject: Re: Weird Toshiba CD causes CAM to crash. In-Reply-To: <199809122240.AAA20591@yedi.iaf.nl> from Wilko Bulte at "Sep 13, 98 00:40:06 am" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sun, 13 Sep 1998 11:14:00 +0200 (CEST) Cc: ken@plutotech.com, cattelan@thebarn.com, freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Wilko Bulte wrote... > As Kenneth D. Merry wrote... > > Wilko Bulte wrote... > > > As Russell Cattelan wrote... > > > > I has to put his hack back into scsi_da.c > > > > > > > > + if (!strncmp(*(&(&cgd->inq_data)->product),"CD-ROM XM-5401TA", > > > > + strlen("CD-ROM XM-5401TA"))){ > > > > + printf("daasync skipping device that looks like CD\n"); > > > > + break; > > > > + } > > > > + > > > > if (cgd->pd_type != T_DIRECT) > > > > break; > > > > > > > > Other wise it would crash someplace in "dadone" at boot time. > > > > > > > > I know this drive is a little weird. > > > > > > Said drive worked fine for me in the non-CAM world. I would not generally > > > qualify Toshiba CDs as weird, they tend to be pretty good. Currently I have > > > a 12x that replaced the 5401: > > > > > > TOSHIBA CD-ROM XM-5701TA 0557 > > > > Most Toshiba drives work just fine. His problem is that his drive probes > > as a direct access device for some reason. > > I can explain that part: it was probably inside an SGI or something like > that. Older SGI machines (maybe new ones also?) need CD drives to behave > like a DA (disk) device in order for the CDs to be bootable. > > Digital has the same thing in their RRDxx cdrom drives. For the newer Hmm. Not completely right: they had to 512 byte blocks by default, like disks... > DEC drives (the Toshiba ones) you can switch from DEC RRD4x to Toshiba > mode (512 and 2048 byte blocks respectively) by (un)setting the parity > jumper. Parity is always enabled. > > Sun also has/had 512 byte block drives. > > I don't know if the DEC and Sun drives probe as DA devices, but I > think they do not. At least I never had troubles getting DEC RRD drives > probed as harddisks. Never tried them with CAM though. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 15 15:24:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24220 for freebsd-scsi-outgoing; Tue, 15 Sep 1998 15:24:14 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from po1.namesecure.com (po1.namesecure.com [205.229.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA24143 for ; Tue, 15 Sep 1998 15:23:43 -0700 (PDT) (envelope-from patrick@namesecure.com) Received: (qmail 1768 invoked by uid 100); 15 Sep 1998 22:23:17 -0000 Date: Tue, 15 Sep 1998 15:23:17 -0700 (PDT) From: Patrick Greenwell To: scsi@FreeBSD.ORG Subject: DPT driver support Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I was wondering if the DPT support was finished, and if so, where one could retrieve the new patches for 2.2.7? /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ Patrick Greenwell (800) 299-1288 v Systems Administrator (925) 377-1212 v NameSecure (925) 377-1414 f Coming to the ISPF? The Forum for ISPs by ISPs http://www.ispf.com \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 15 15:31:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25949 for freebsd-scsi-outgoing; Tue, 15 Sep 1998 15:31:48 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fledge.watson.org (COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25901 for ; Tue, 15 Sep 1998 15:31:19 -0700 (PDT) (envelope-from shafeeq@cyrus.watson.org) Received: from localhost (shafeeq@localhost) by fledge.watson.org (8.8.8/8.8.8) with SMTP id SAA24730 for ; Tue, 15 Sep 1998 18:30:57 -0400 (EDT) X-Authentication-Warning: fledge.watson.org: shafeeq owned process doing -bs Date: Tue, 15 Sep 1998 18:30:57 -0400 (EDT) From: Shafeeq Sinnamohideen X-Sender: shafeeq@fledge.watson.org To: scsi@FreeBSD.ORG Subject: Re: SANE+CAM works... In-Reply-To: <199807271851.MAA25876@panzer.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 Hi, Are the patches to get SANE to work with CAM available somewhere, or should we just wait until the next snapshot of SANE ? Thanks, Shafeeq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 15 18:28:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29066 for freebsd-scsi-outgoing; Tue, 15 Sep 1998 18:28:52 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29019 for ; Tue, 15 Sep 1998 18:28:34 -0700 (PDT) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id VAA04625; Tue, 15 Sep 1998 21:27:59 -0400 (EDT) To: Shafeeq Sinnamohideen , freebsd-scsi@FreeBSD.ORG Subject: Re: SANE+CAM works... References: X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A X-PGP-Keyloc: ; finger ckempf@enigami.com From: Cory Kempf Date: 15 Sep 1998 21:27:57 -0400 In-Reply-To: Shafeeq Sinnamohideen's message of "Tue, 15 Sep 1998 18:30:57 -0400 (EDT)" Message-ID: Lines: 24 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Shafeeq" == Shafeeq Sinnamohideen writes: > Hi, > Are the patches to get SANE to work with CAM available somewhere, or > should we just wait until the next snapshot of SANE ? I have submitted the patches, but they arrived too late for the 0.74 release. I don't know what the schedule is for 0.75... At the moment, they reside on my machine, but I am not at all set up as a public ftp server. Anyone have any suggestions what else should be done with what I have? I have the mods in two forms: the full source tree and as a diffs file. +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 15 19:26:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09671 for freebsd-scsi-outgoing; Tue, 15 Sep 1998 19:26:07 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09555 for ; Tue, 15 Sep 1998 19:25:58 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id UAA22195; Tue, 15 Sep 1998 20:25:23 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809160225.UAA22195@panzer.plutotech.com> Subject: Re: SANE+CAM works... In-Reply-To: from Cory Kempf at "Sep 15, 98 09:27:57 pm" To: ckempf@enigami.com (Cory Kempf) Date: Tue, 15 Sep 1998 20:25:23 -0600 (MDT) Cc: shafeeq@cyrus.watson.org, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Cory Kempf wrote... > "Shafeeq" == Shafeeq Sinnamohideen writes: > > > Hi, > > Are the patches to get SANE to work with CAM available somewhere, or > > should we just wait until the next snapshot of SANE ? > > I have submitted the patches, but they arrived too late for the 0.74 > release. I don't know what the schedule is for 0.75... > > At the moment, they reside on my machine, but I am not at all set up > as a public ftp server. > > Anyone have any suggestions what else should be done with what I have? > I have the mods in two forms: the full source tree and as a diffs > file. I would suggest talking to someone on the "ports team" and get them to commit your patches to the ports tree. (I would offer to do it, but I'm not very ports-savvy, and I might screw it up.) You'll probably want to make sure that with your patch, SANE will work on either a CAM or a non-CAM system. (I generally autodetect by looking for /usr/include/camlib.h.) Then, when 0.75 comes out with your CAM patches, we can nuke the CAM patch in the ports tree. That reminds me, I need to talk to the ports folks about getting the tosha, xmcd and cdrecord patches in. (the cdrecord patches will hopefully be part of the next release) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 15 20:14:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17247 for freebsd-scsi-outgoing; Tue, 15 Sep 1998 20:14:43 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nash.pubnix.net (Nash.pubnix.net [192.172.250.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17242 for ; Tue, 15 Sep 1998 20:14:41 -0700 (PDT) (envelope-from aal@pubnix.net) Received: from pubnix.net (aal.pubnix.net [199.202.137.130]) by nash.pubnix.net (8.8.8/8.8.7) with ESMTP id XAA19628 for ; Tue, 15 Sep 1998 23:14:24 -0400 (EDT) (envelope-from aal@pubnix.net) Message-ID: <35FF2D28.AB977FC4@pubnix.net> Date: Tue, 15 Sep 1998 23:14:48 -0400 From: Alain Hebert Reply-To: ahebert@pubnix.net Organization: PubNIX Montreal, Inc. X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 CC: scsi@FreeBSD.ORG Subject: Yamaha CD-R and CAM: What I'm doing wrong... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Anybody has been successful in using this device to do something else than playing audio? xcmd works (From the patch on ftp://ftp.freebsd.org), tosha CANNOT read CD-ROM but any track from a gold disk is seen has audio and can be read (ie: tosha -i 1), and cdrecord cannot even give me a useful result from a scsi probe (cdrecord -scanbus). I will walk through everything and try to debug it the best I can... OKCT: (Obligatory Kernel CAM Texts...) cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 3.300MB/s transfers cd0: cd present [324701 x 2048 byte records] BTW, CAM and 3.0-current has been stable since I re-work the wiring inside the cabinet... I've been using it for parallel work (got about 15 xterms doing mp3 plays, compiling, databases (mSQL, MySQL and Postgres (which I like very much...), coding, cvs and others without any single CAM glitch...) In fact except for the Kernel boot 0x17d that was caused by EMI and cable on the UW, it has been a charm... (Me too's...) I will like to thanks Kenneth and Justin! Have fun... (Now if I can get this CD-R to write... I got 600MB of mp3 to move out...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 15 21:32:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27296 for freebsd-scsi-outgoing; Tue, 15 Sep 1998 21:32:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27281 for ; Tue, 15 Sep 1998 21:32:05 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id WAA23611; Tue, 15 Sep 1998 22:31:43 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809160431.WAA23611@panzer.plutotech.com> Subject: Re: Yamaha CD-R and CAM: What I'm doing wrong... In-Reply-To: <35FF2D28.AB977FC4@pubnix.net> from Alain Hebert at "Sep 15, 98 11:14:48 pm" To: ahebert@pubnix.net Date: Tue, 15 Sep 1998 22:31:43 -0600 (MDT) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Alain Hebert wrote... > Hi! > > Anybody has been successful in using this device to do something else > than playing audio? > > xcmd works (From the patch on ftp://ftp.freebsd.org), tosha CANNOT read > CD-ROM but any track from a gold disk is seen has audio and can be read > (ie: tosha -i 1), and cdrecord cannot even give me a useful result from > a scsi probe (cdrecord -scanbus). Hmm, tosha doesn't work? Did it print any error messages? Perhaps it doesn't know much about your CD-R? Did it work before CAM? As for cdrecord, I'm working with Joerg Schilling on getting the CAM patches into the main distribution. Try this binary, and let me know whether it works: ftp://ftp.kdm.org/pub/FreeBSD/cam/test/cdrecord-1.6.1a3.test The -scanbus option is known to be non-functional with the verison of the CAM patches for cdrecord that you've got. It should work okay with the binary above. > BTW, CAM and 3.0-current has been stable since I re-work the wiring > inside the cabinet... Good deal. :) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 15 23:15:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09718 for freebsd-scsi-outgoing; Tue, 15 Sep 1998 23:15:58 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA09711 for ; Tue, 15 Sep 1998 23:15:49 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0zJAJI-0002GD-00; Tue, 15 Sep 1998 22:39:24 -0700 Date: Tue, 15 Sep 1998 22:39:22 -0700 (PDT) From: Tom To: Patrick Greenwell cc: scsi@FreeBSD.ORG Subject: Re: DPT driver support 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 Tue, 15 Sep 1998, Patrick Greenwell wrote: > Hi, > > I was wondering if the DPT support was finished, and if so, where one > could retrieve the new patches for 2.2.7? I'm not sure what you are talking about. The DPT driver is in 2.2.7. There are no patches I'm aware of. I think you might be confusing DPT support in 2.2.7 with DPT support in FreeBSD-current. > /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ > Patrick Greenwell (800) 299-1288 v > Systems Administrator (925) 377-1212 v > NameSecure (925) 377-1414 f > Coming to the ISPF? The Forum for ISPs by ISPs http://www.ispf.com > \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 16 10:08:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16296 for freebsd-scsi-outgoing; Wed, 16 Sep 1998 10:08:14 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from po1.namesecure.com (po1.namesecure.com [205.229.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA16045 for ; Wed, 16 Sep 1998 10:07:52 -0700 (PDT) (envelope-from patrick@namesecure.com) Received: (qmail 6337 invoked by uid 100); 16 Sep 1998 17:07:31 -0000 Date: Wed, 16 Sep 1998 10:07:31 -0700 (PDT) From: Patrick Greenwell To: Tom cc: scsi@FreeBSD.ORG Subject: Re: DPT driver support 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 Tue, 15 Sep 1998, Tom wrote: > > On Tue, 15 Sep 1998, Patrick Greenwell wrote: > > > Hi, > > > > I was wondering if the DPT support was finished, and if so, where one > > could retrieve the new patches for 2.2.7? > > I'm not sure what you are talking about. The DPT driver is in 2.2.7. > There are no patches I'm aware of. > > I think you might be confusing DPT support in 2.2.7 with DPT support in > FreeBSD-current. My apologies for not being more specific. I was told that I couldn't use the CAM patches previously as the DPT support was not finished and they were due Sept. 13th. Does this only apply to 3.0 and not 2.2.7? /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ Patrick Greenwell (800) 299-1288 v Systems Administrator (925) 377-1212 v NameSecure (925) 377-1414 f Coming to the ISPF? The Forum for ISPs by ISPs http://www.ispf.com \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 16 16:34:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09469 for freebsd-scsi-outgoing; Wed, 16 Sep 1998 16:34:45 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09370 for ; Wed, 16 Sep 1998 16:34:16 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id RAA05156; Wed, 16 Sep 1998 17:27:29 -0600 (MDT) Date: Wed, 16 Sep 1998 17:27:29 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809162327.RAA05156@narnia.plutotech.com> To: Patrick Greenwell cc: scsi@FreeBSD.ORG Subject: Re: DPT driver support Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > On Tue, 15 Sep 1998, Tom wrote: > > My apologies for not being more specific. I was told that I couldn't use > the CAM patches previously as the DPT support was not finished and they > were due Sept. 13th. Does this only apply to 3.0 and not 2.2.7? I have been too busy fighting fires to port the code back to stable yet. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 16 17:09:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16316 for freebsd-scsi-outgoing; Wed, 16 Sep 1998 17:09:51 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16120 for ; Wed, 16 Sep 1998 17:08:49 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id SAA28775; Wed, 16 Sep 1998 18:08:12 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809170008.SAA28775@panzer.plutotech.com> Subject: Re: DPT driver support In-Reply-To: from Patrick Greenwell at "Sep 16, 98 10:07:31 am" To: patrick@namesecure.com (Patrick Greenwell) Date: Wed, 16 Sep 1998 18:08:12 -0600 (MDT) Cc: tom@sdf.com, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Patrick Greenwell wrote... > On Tue, 15 Sep 1998, Tom wrote: > > > > > On Tue, 15 Sep 1998, Patrick Greenwell wrote: > > > > > Hi, > > > > > > I was wondering if the DPT support was finished, and if so, where one > > > could retrieve the new patches for 2.2.7? > > > > I'm not sure what you are talking about. The DPT driver is in 2.2.7. > > There are no patches I'm aware of. > > > > I think you might be confusing DPT support in 2.2.7 with DPT support in > > FreeBSD-current. > > My apologies for not being more specific. I was told that I couldn't use > the CAM patches previously as the DPT support was not finished and they > were due Sept. 13th. Does this only apply to 3.0 and not 2.2.7? The CAM port of the DPT driver is done; CAM has been checked into -current as well. We haven't released a -stable snapshot with the DPT driver in it, and I'm not sure when that will happen. It may be a while, since we're busy fixing bugs that have cropped up in the -current integration and doing our "real" jobs. :) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 16 17:10:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16611 for freebsd-scsi-outgoing; Wed, 16 Sep 1998 17:10:48 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from po1.namesecure.com (po1.namesecure.com [205.229.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA16343 for ; Wed, 16 Sep 1998 17:09:42 -0700 (PDT) (envelope-from patrick@namesecure.com) Received: (qmail 22253 invoked by uid 100); 17 Sep 1998 00:09:10 -0000 Date: Wed, 16 Sep 1998 17:09:10 -0700 (PDT) From: Patrick Greenwell To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: DPT driver support In-Reply-To: <199809162327.RAA05156@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 On Wed, 16 Sep 1998, Justin T. Gibbs wrote: > In article you wrote: > > On Tue, 15 Sep 1998, Tom wrote: > > > > My apologies for not being more specific. I was told that I couldn't use > > the CAM patches previously as the DPT support was not finished and they > > were due Sept. 13th. Does this only apply to 3.0 and not 2.2.7? > > I have been too busy fighting fires to port the code back to stable > yet. No problem, just wondering. :-) /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ Patrick Greenwell (800) 299-1288 v Systems Administrator (925) 377-1212 v NameSecure (925) 377-1414 f Coming to the ISPF? The Forum for ISPs by ISPs http://www.ispf.com \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 16 17:17:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18505 for freebsd-scsi-outgoing; Wed, 16 Sep 1998 17:17:56 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from laker.net (jet.laker.net [205.245.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18300 for ; Wed, 16 Sep 1998 17:16:59 -0700 (PDT) (envelope-from sfriedri@laker.net) Received: from nt (digital-pbi-162.laker.net [208.0.233.62]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id UAA16372 for ; Wed, 16 Sep 1998 20:16:31 -0400 Message-Id: <199809170016.UAA16372@laker.net> From: "Steve Friedrich" To: "freebsd-scsi" Date: Wed, 16 Sep 1998 20:16:35 -0400 Reply-To: "Steve Friedrich" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: old SCSI vs CAM Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am pretty new to FreeBSD, but have been around unix awhile. I am currently running 2.2.7 STABLE and I believe that in the near future, CAM is going to affect me. I have a CD-ROM attached to a MediaVision PAS16 using the nca driver. I believe that when CAM gets rolled into STABLE, I'll lose the nca driver... Am I right ?? This won't be catastrophic for me, it will just be something to address. I'd hope that someone would whack together a CAM version of nca... But I can understand if you don't want to bother. I'm planning on switching to 3.0.0 on Oct 15th, don't know if CAM will be just rolled into current or also stable... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 16 20:14:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24509 for freebsd-scsi-outgoing; Wed, 16 Sep 1998 20:14:21 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24429 for ; Wed, 16 Sep 1998 20:14:01 -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.1/8.8.8) with ESMTP id UAA02075; Wed, 16 Sep 1998 20:19:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199809170319.UAA02075@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Steve Friedrich" cc: "freebsd-scsi" Subject: Re: old SCSI vs CAM In-reply-to: Your message of "Wed, 16 Sep 1998 20:16:35 EDT." <199809170016.UAA16372@laker.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Sep 1998 20:19:31 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am pretty new to FreeBSD, but have been around unix awhile. > > I am currently running 2.2.7 STABLE and I believe that in the near > future, CAM is going to affect me. > > I have a CD-ROM attached to a MediaVision PAS16 using the nca driver. > I believe that when CAM gets rolled into STABLE, I'll lose the nca > driver... Am I right ?? This won't be catastrophic for me, it will > just be something to address. I'd hope that someone would whack > together a CAM version of nca... But I can understand if you don't want > to bother. CAM won't be rolled into -stable. It's likely to continue to continue to exist as a set of patches against -stable though. It's unlikely that an nca driver will be written for CAM unless someone becomes wildly enthusiastic about it; the 53c80 family really don't feature on anyones' map as a major SCSI controller solution these days. Without someone with a strong agenda featuring this family and a wide variety of implementations (there are probably half a dozen significantly different ways you can integrate one of these controllers into an ISA system) I'd say you can write the 'nca' driver off with the 2.2 family. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Wed Sep 16 20:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25187 for freebsd-scsi-outgoing; Wed, 16 Sep 1998 20:17:42 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nash.pubnix.net (Nash.pubnix.net [192.172.250.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25116 for ; Wed, 16 Sep 1998 20:17:14 -0700 (PDT) (envelope-from aal@pubnix.net) Received: from pubnix.net (aal.pubnix.net [199.202.137.130]) by nash.pubnix.net (8.8.8/8.8.7) with ESMTP id XAA07252 for ; Wed, 16 Sep 1998 23:16:44 -0400 (EDT) (envelope-from aal@pubnix.net) Message-ID: <36007F34.A4EAE2B9@pubnix.net> Date: Wed, 16 Sep 1998 23:17:08 -0400 From: Alain Hebert Reply-To: ahebert@pubnix.net Organization: PubNIX Montreal, Inc. X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: Re: Yamaha CD-R and CAM: What I'm doing wrong... References: <199809160431.WAA23611@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote: > > Alain Hebert wrote... > > Hi! > > > > Anybody has been successful in using this device to do something else > > than playing audio? > Hmm, tosha doesn't work? Did it print any error messages? Perhaps it > doesn't know much about your CD-R? Did it work before CAM? 'tosha -t 1' give me (when used with normal Audio CD): (pass2:ahc0:0:3:0): READ(10). CDB: 28 0 0 0 0 0 0 0 a 0 (pass2:ahc0:0:3:0): ILLEGAL REQUEST asc:64,0 (pass2:ahc0:0:3:0): Illegal mode for this track I never used anything else than CAM with this setup... > As for cdrecord, I'm working with Joerg Schilling on getting the CAM > patches into the main distribution. Try this binary, and let me know > whether it works: > > ftp://ftp.kdm.org/pub/FreeBSD/cam/test/cdrecord-1.6.1a3.test Tried it!... not much positives (got some message about can open SCSI device...) BUT! I got the alpha version (1.6.1a3) apply the patches from 1.6 (made some adjustments) and got it to work (all the features including scanbus, but didn't write a CD yet). That is how I found 'What I was doing wrong': The device shows up in dev=2,3,0 which is logical since I got this ASUS P2B-DS with 7890 and the 3xxx chipset which give me access all SCSI types... Now, its time to waste some CD... Have fun... (and thanks for the lightning response!) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 16 23:07:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25563 for freebsd-scsi-outgoing; Wed, 16 Sep 1998 23:07:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA25540 for ; Wed, 16 Sep 1998 23:07:03 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0zJWeF-0003Mw-00; Wed, 16 Sep 1998 22:30:31 -0700 Date: Wed, 16 Sep 1998 22:30:30 -0700 (PDT) From: Tom To: Patrick Greenwell cc: scsi@FreeBSD.ORG Subject: Re: DPT driver support In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 16 Sep 1998, Patrick Greenwell wrote: > On Tue, 15 Sep 1998, Tom wrote: > > > On Tue, 15 Sep 1998, Patrick Greenwell wrote: > > > > > Hi, > > > > > > I was wondering if the DPT support was finished, and if so, where one > > > could retrieve the new patches for 2.2.7? > > > > I'm not sure what you are talking about. The DPT driver is in 2.2.7. > > There are no patches I'm aware of. > > > > I think you might be confusing DPT support in 2.2.7 with DPT support in > > FreeBSD-current. > > My apologies for not being more specific. I was told that I couldn't use > the CAM patches previously as the DPT support was not finished and they > were due Sept. 13th. Does this only apply to 3.0 and not 2.2.7? The dpt driver in 2.2.7 is not CAMifed. There really is no need to use CAM when using a DPT card anyhow. > /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ > Patrick Greenwell (800) 299-1288 v > Systems Administrator (925) 377-1212 v > NameSecure (925) 377-1414 f > Coming to the ISPF? The Forum for ISPs by ISPs http://www.ispf.com > \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 16 23:25:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28371 for freebsd-scsi-outgoing; Wed, 16 Sep 1998 23:25:06 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nash.pubnix.net (Nash.pubnix.net [192.172.250.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28360 for ; Wed, 16 Sep 1998 23:25:00 -0700 (PDT) (envelope-from aal@pubnix.net) Received: from pubnix.net (aal.pubnix.net [199.202.137.130]) by nash.pubnix.net (8.8.8/8.8.7) with ESMTP id CAA08635 for ; Thu, 17 Sep 1998 02:24:43 -0400 (EDT) (envelope-from aal@pubnix.net) Message-ID: <3600AB43.F6CB9224@pubnix.net> Date: Thu, 17 Sep 1998 02:25:07 -0400 From: Alain Hebert Organization: PubNIX Montreal, Inc. X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: Re: Yamaha CD-R and CAM: What I'm doing wrong... References: <199809160431.WAA23611@panzer.plutotech.com> <36007F34.A4EAE2B9@pubnix.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Conclusion... IT WORK! Just finish creating a 11h (167 tunes in MP3) CD! 4x writing speed too! So you can add the 'YAMAHA CRW4260 1.0g' as a working device with 3.0-current, cdrecord 1.6.1a3 and standard mkisofs... Have fun... (add xamp, amp and a good collection of CD... Who need radio! Now if I can get those *&&%*#$ at ATI to release there propriatory reg's info about the All-In-Wonder, I will not need a TV and a VCR either.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 16 23:32:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29843 for freebsd-scsi-outgoing; Wed, 16 Sep 1998 23:32:42 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA29824 for ; Wed, 16 Sep 1998 23:32:39 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zJXbq-0003Pb-00; Thu, 17 Sep 1998 00:32:06 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id AAA14773; Thu, 17 Sep 1998 00:33:14 -0600 (MDT) Message-Id: <199809170633.AAA14773@harmony.village.org> To: Mike Smith Subject: Re: old SCSI vs CAM Cc: "Steve Friedrich" , "freebsd-scsi" In-reply-to: Your message of "Wed, 16 Sep 1998 20:19:31 PDT." <199809170319.UAA02075@dingo.cdrom.com> References: <199809170319.UAA02075@dingo.cdrom.com> Date: Thu, 17 Sep 1998 00:33:14 -0600 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199809170319.UAA02075@dingo.cdrom.com> Mike Smith writes: : It's unlikely that an nca driver will be written for CAM unless someone : becomes wildly enthusiastic about it; the 53c80 family really don't : feature on anyones' map as a major SCSI controller solution these days. The same goes for the sea and wds drivers. The aic driver and uha drivers have crazy people that really want to see them supported working on them. Well, at least the uha worker is crazy :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 17 00:01:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05700 for freebsd-scsi-outgoing; Thu, 17 Sep 1998 00:01:01 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from friley-185-114.res.iastate.edu (friley-185-114.res.iastate.edu [129.186.185.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05679 for ; Thu, 17 Sep 1998 00:00:59 -0700 (PDT) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Received: from friley-185-114.res.iastate.edu (loopback [127.0.0.1]) by friley-185-114.res.iastate.edu (8.9.1/8.9.1) with ESMTP id CAA07250 for ; Thu, 17 Sep 1998 02:00:38 -0500 (CDT) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Message-Id: <199809170700.CAA07250@friley-185-114.res.iastate.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG Subject: Selection Timeout messages.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Sep 1998 02:00:37 -0500 From: Chris Csanady Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have been getting the following messages recently, and was wondering if anyone might enlighten me as to what they mean. It only seems to occur right at boot time as well.. Sep 16 16:14:43 friley-185-114 /kernel: (noperiph:ahc0:0:X:X): SCSI bus reset delivered. 0 SCBs a borted. Sep 16 16:14:43 friley-185-114 /kernel: ahc0: Selection Timeout on A:3. 1 SCBs aborted Sep 16 16:14:43 friley-185-114 /kernel: ahc0: Selection Timeout on A:4. 1 SCBs aborted Sep 16 16:14:43 friley-185-114 /kernel: ahc0: Selection Timeout on A:5. 1 SCBs aborted Sep 16 16:14:43 friley-185-114 /kernel: ahc0: Selection Timeout on A:8. 1 SCBs aborted ... Thanks, Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 17 03:50:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15447 for freebsd-scsi-outgoing; Thu, 17 Sep 1998 03:50:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rmstar.campus.luth.se (rmstar.campus.luth.se [130.240.197.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15369 for ; Thu, 17 Sep 1998 03:50:17 -0700 (PDT) (envelope-from murduth@rmstar.campus.luth.se) Received: from rmstar.campus.luth.se (murduth@localhost [127.0.0.1]) by rmstar.campus.luth.se (8.9.1/8.9.1) with ESMTP id KAA01448 for ; Thu, 17 Sep 1998 10:49:46 GMT (envelope-from murduth@rmstar.campus.luth.se) Message-Id: <199809171049.KAA01448@rmstar.campus.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG Subject: CAM and the amazing locking scsi bus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Sep 1998 12:49:45 +0200 From: Joakim Henriksson Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! When i tried CAM today after the integration i get a locked SCSI bus when doing lots of seeks (fts on whole filesystems). Here comes some outputs from my logs. It doesnt seem serious and probably is me shooting myself in the foot. Could someone tell me how not to, or is more data needed? :) I run current as of yesterday if that makes any difference. Sep 17 07:39:30 rmstar /kernel: (da0:ncr0:0:0:0): tagged openings now 25 Sep 17 07:40:32 rmstar /kernel: ncr0: timeout nccb=f0bcda00 (skip) Sep 17 07:40:32 rmstar /kernel: ncr0: timeout nccb=f0c63800 (skip) Sep 17 07:40:32 rmstar /kernel: ncr0: timeout nccb=f0c47e00 (skip) . . . ncr0: rev 0x02 int a irq 12 on pci0.10.0 ncr0: waiting for scsi devices to settle scbus0 at ncr0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: 10.0 MB/s (100 ns, offset 8) 1034MB (2118144 512 byte sectors) sd0: with 4903 cyls, 4 heads, and an average 108 sectors/track sd1 at scbus0 target 2 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access sd1: 10.0 MB/s (100 ns, offset 8) 2048MB (4194304 512 byte sectors) sd1: with 3999 cyls, 10 heads, and an average 104 sectors/track st0 at scbus0 target 4 lun 0 st0: type 1 removable SCSI 2 st0: Sequential-Access st0: 4.0 MB/s (250 ns, offset 8) density code 0x15, drive empty cd0 at scbus0 target 6 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd0: 10.0 MB/s (100 ns, offset 8) -- mvh/ Joakim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 17 07:46:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17335 for freebsd-scsi-outgoing; Thu, 17 Sep 1998 07:46:36 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17268 for ; Thu, 17 Sep 1998 07:46:15 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id IAA03254; Thu, 17 Sep 1998 08:45:17 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809171445.IAA03254@panzer.plutotech.com> Subject: Re: CAM and the amazing locking scsi bus In-Reply-To: <199809171049.KAA01448@rmstar.campus.luth.se> from Joakim Henriksson at "Sep 17, 98 12:49:45 pm" To: murduth@ludd.luth.se (Joakim Henriksson) Date: Thu, 17 Sep 1998 08:45:17 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Joakim Henriksson wrote... > Hi! When i tried CAM today after the integration i get a locked SCSI bus when > doing lots of seeks (fts on whole filesystems). Here comes some outputs from > my logs. It doesnt seem serious and probably is me shooting myself in the > foot. Could someone tell me how not to, or is more data needed? :) I run > current as of yesterday if that makes any difference. > > Sep 17 07:39:30 rmstar /kernel: (da0:ncr0:0:0:0): tagged openings now 25 > Sep 17 07:40:32 rmstar /kernel: ncr0: timeout nccb=f0bcda00 (skip) > Sep 17 07:40:32 rmstar /kernel: ncr0: timeout nccb=f0c63800 (skip) > Sep 17 07:40:32 rmstar /kernel: ncr0: timeout nccb=f0c47e00 (skip) > . > . > . > Justin fixed a number of bugs in the NCR driver yesterday. You may want to re-cvsup and get his latest fixes. I was able to do a large amount of I/O (albeit on a slow disk) with an NCR 810 in my test box without any trouble. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 17 11:23:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25829 for freebsd-scsi-outgoing; Thu, 17 Sep 1998 11:23:16 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from absinthe.shenton.org (Absinthe.Shenton.Org [209.31.147.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25814; Thu, 17 Sep 1998 11:23:10 -0700 (PDT) (envelope-from chris@absinthe.shenton.org) Received: (from chris@localhost) by absinthe.shenton.org (8.9.1/8.9.1) id OAA02137; Thu, 17 Sep 1998 14:21:07 -0400 (EDT) To: questions@FreeBSD.ORG cc: scsi@FreeBSD.ORG Subject: st0: 262144-byte record too big (reading SGI tar tape) X-Emacs: Emacs 20.3, MULE 4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.8.5 - "Nishi-Takaoka") Content-Type: text/plain; charset=US-ASCII From: Chris Shenton Date: 17 Sep 1998 14:21:06 -0400 Message-ID: <87hfy6wqgd.fsf@absinthe.shenton.org> Lines: 14 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to restore files from tar image tape made on an SGI. Whether I use "dd" or "tar" I get the same complaint in syslog: st0: 262144-byte record too big I've tried various "bs=" and "conv=" to dd but get the same error so I suspect the "st" driver is upset with the tape. 262144 bytes is 256KB which seems unlikely to be a coincidence. This is on an Archive (Connor/Seagate) Python 4mm DDS2 which I've used successfully for Amanda. Kernel is 2.2.7-STABLE with a 2.2.6-STABLE OS. Any hints on how to recover this tape? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 17 12:17:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07918 for freebsd-scsi-outgoing; Thu, 17 Sep 1998 12:17:46 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA07913 for ; Thu, 17 Sep 1998 12:17:41 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA00562 (5.67b/IDA-1.5); Thu, 17 Sep 1998 20:51:39 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id UAA00751; Thu, 17 Sep 1998 20:02:35 +0200 (CEST) From: Wilko Bulte Message-Id: <199809171802.UAA00751@yedi.iaf.nl> Subject: Re: old SCSI vs CAM In-Reply-To: <199809170633.AAA14773@harmony.village.org> from Warner Losh at "Sep 17, 98 00:33:14 am" To: imp@village.org (Warner Losh) Date: Thu, 17 Sep 1998 20:02:35 +0200 (CEST) Cc: mike@smith.net.au, sfriedri@laker.net, freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Warner Losh wrote... > In message <199809170319.UAA02075@dingo.cdrom.com> Mike Smith writes: > : It's unlikely that an nca driver will be written for CAM unless someone > : becomes wildly enthusiastic about it; the 53c80 family really don't > : feature on anyones' map as a major SCSI controller solution these days. > > The same goes for the sea and wds drivers. The aic driver and uha > drivers have crazy people that really want to see them supported > working on them. Well, at least the uha worker is crazy :-) The world would be boring without some crazy people to spice things.. ;-) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 17 13:07:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14658 for freebsd-scsi-outgoing; Thu, 17 Sep 1998 13:07:18 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14643 for ; Thu, 17 Sep 1998 13:07:12 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id NAA02296; Thu, 17 Sep 1998 13:03:40 -0700 Date: Thu, 17 Sep 1998 13:03:40 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Wilko Bulte cc: Warner Losh , mike@smith.net.au, sfriedri@laker.net, freebsd-scsi@FreeBSD.ORG Subject: Re: old SCSI vs CAM In-Reply-To: <199809171802.UAA00751@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > The same goes for the sea and wds drivers. The aic driver and uha > > drivers have crazy people that really want to see them supported > > working on them. Well, at least the uha worker is crazy :-) > > The world would be boring without some crazy people to spice things.. ;-) Unfortunately, the world is crazy with boring people who don't like to spice things.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 17 13:17:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17331 for freebsd-scsi-outgoing; Thu, 17 Sep 1998 13:17:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rmstar.campus.luth.se (rmstar.campus.luth.se [130.240.197.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17264 for ; Thu, 17 Sep 1998 13:17:03 -0700 (PDT) (envelope-from murduth@rmstar.campus.luth.se) Received: from rmstar.campus.luth.se (murduth@localhost [127.0.0.1]) by rmstar.campus.luth.se (8.9.1/8.9.1) with ESMTP id WAA22396; Thu, 17 Sep 1998 22:16:05 +0200 (CEST) (envelope-from murduth@rmstar.campus.luth.se) Message-Id: <199809172016.WAA22396@rmstar.campus.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" cc: murduth@ludd.luth.se (Joakim Henriksson), freebsd-scsi@FreeBSD.ORG Subject: Re: CAM and the amazing locking scsi bus In-reply-to: Your message of "Thu, 17 Sep 1998 08:45:17 MDT." <199809171445.IAA03254@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Sep 1998 22:16:05 +0200 From: Joakim Henriksson Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Justin fixed a number of bugs in the NCR driver yesterday. You may want to > re-cvsup and get his latest fixes. Tried that and it doesn't work (it might be slightly better) but when i extracted XFree86 it hanged again. The filesystem was in a very bad way after this. I'm at the latest version of ncr.c (1.128). > I was able to do a large amount of I/O (albeit on a slow disk) with an NCR > 810 in my test box without any trouble. Yeah i can do pretty heavy IO for a while and then _wham_ locked bus. -- regards/ Joakim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 17 14:58:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16651 for freebsd-scsi-outgoing; Thu, 17 Sep 1998 14:58:48 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16465 for ; Thu, 17 Sep 1998 14:57:33 -0700 (PDT) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.1/8.9.1) with ESMTP id XAA20501 for ; Thu, 17 Sep 1998 23:56:58 +0200 (CEST) Message-Id: <199809172156.XAA20501@midten.fast.no> To: freebsd-scsi@FreeBSD.ORG Subject: aic7xxx.c: Fatal trap 12: page fault while in kernel mode From: Tor.Egge@fast.no X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 17 Sep 1998 23:56:58 +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org With target mode disabled and 255 scbs available, scb index TARGET_CMD_CMPLT (0xfe) is used for normal commands. Unfortunately, ahc_intr does not check for target mode being enabled when the scb index is TARGET_CMD_CMPLT. A suggested fix is appended. ------ ahc0: rev 0x00 int a irq 19 on pci0.6.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs [..snip..] (da2:ahc0:0:2:0): tagged openings now 63 (da0:ahc0:0:0:0): tagged openings now 63 (da0:ahc0:0:0:0): tagged openings now 49 (da1:ahc0:0:1:0): tagged openings now 62 (da2:ahc0:0:2:0): tagged openings now 62 (da3:ahc0:0:3:0): tagged openings now 63 (da3:ahc0:0:3:0): tagged openings now 62 (da4:ahc0:0:4:0): tagged openings now 57 (da1:ahc0:0:1:0): tagged openings now 53 (da5:ahc0:0:5:0): tagged openings now 60 (da2:ahc0:0:2:0): tagged openings now 58 Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xe0117577 stack pointer = 0x10:0xff806f60 frame pointer = 0x10:0xff806f78 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = cam <- SMP: XXX kernel: type 12 trap, code=0 Stopped at _ahc_handle_target_cmd+0x3f: movb 0(%ecx),%al db> trace _ahc_handle_target_cmd(e1b60000) at _ahc_handle_target_cmd+0x3f _ahc_intr(e1b60000,cc080000,0,6,0) at _ahc_intr+0xd5 _intr_mux(e115af60,0,e01e0010,10,0) at _intr_mux+0x1d Xresume19() at Xresume19+0x51 --- interrupt, eip = 0xe01f4f60, esp = 0xff806ff0, ebp = 0 --- _default_halt() at _default_halt db> panic panic: from debugger mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 Debugger("panic") Stopped at _ahc_handle_target_cmd+0x3f: movb 0(%ecx),%al db> panic panic: from debugger mp_lock = 00000003; cpuid = 0; lapic.id = 01000000 boot() called on cpu#0 Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#0 ------ Index: aic7xxx.c =================================================================== RCS file: /home/ncvs/src/sys/dev/aic7xxx/aic7xxx.c,v retrieving revision 1.2 diff -u -r1.2 aic7xxx.c --- aic7xxx.c 1998/09/16 03:26:10 1.2 +++ aic7xxx.c 1998/09/17 21:15:47 @@ -961,7 +961,8 @@ scb_index = ahc->qoutfifo[ahc->qoutfifonext]; ahc->qoutfifo[ahc->qoutfifonext++] = SCB_LIST_NULL; - if (scb_index == TARGET_CMD_CMPLT) { + if (scb_index == TARGET_CMD_CMPLT && + (ahc->flags & AHC_TARGETMODE) != 0) { ahc_handle_target_cmd(ahc); continue; } - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 17 18:37:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29610 for freebsd-scsi-outgoing; Thu, 17 Sep 1998 18:37:48 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tbuswell.ne.mediaone.net (tbuswell.ne.mediaone.net [24.128.24.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29533 for ; Thu, 17 Sep 1998 18:36:55 -0700 (PDT) (envelope-from tbuswell@tbuswell.ne.mediaone.net) Received: (from tbuswell@localhost) by tbuswell.ne.mediaone.net (8.9.1/8.8.8) id VAA08413; Thu, 17 Sep 1998 21:35:49 -0400 (EDT) (envelope-from tbuswell) From: Ted Buswell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 17 Sep 1998 21:35:49 -0400 (EDT) To: freebsd-scsi@FreeBSD.ORG Subject: CAM/ncr messages.. X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13825.46672.35984.907842@tbuswell.ne.mediaone.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On a -current system that was CVSup'd and installed today, I'm getting some interesting messages and was wondering if anyone had any insight. The messages occur when doing significant I/O [rm -rf, buildworld, etc.] No softupdates or anything. Attached is my dmesg output. ncr.c is rev 1.128 cam_xpt.c is rev 1.5 Should messages like this be going to -scsi or -current? Thanks, -Ted Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Thu Sep 17 20:55:48 EDT 1998 tbuswell@tbuswell.ne.mediaone.net:/usr/src/sys/compile/SMPBOX Timecounter "i8254" frequency 1193182 Hz cost 3372 ns CPU: Pentium II (686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80fbff real memory = 134217728 (131072K bytes) avail memory = 127528960 (124540K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.4.0 chip3: rev 0x01 int d irq 11 on pci0.4.2 chip4: rev 0x01 on pci0.4.3 ahc0: rev 0x00 int a irq 19 on pci0.6.0 ahc0: Illegal cable configuration!!. Only two connectors on the adapter may be used at a time! ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs de0: rev 0x11 int a irq 17 on pci0.11.0 de0: DEC DE450-TA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:05:94:b1 ncr0: rev 0x02 int a irq 16 on pci0.12.0 Probing for devices on PCI bus 1: vga0: rev 0x04 int a irq 16 on pci1.0.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x320 ed1 at 0x300-0x31f irq 9 on isa ed1: address 00:c0:d1:57:4b:24, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model IntelliMouse, device ID 3 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa Hmm... Could this be an ESS688 based card (rev 11) NOTE! SB Pro support required with your soundcard! snd0: opl0 at 0x388 on isa snd0: sbmidi0 not found at 0x330 de0: enabling 10baseT port APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, unlimited logging SMP: AP CPU #1 Launched! da0 at ahc0 bus 0 target 5 lun 0 da0: Removable Direct Access SCSI2 device da0: 3.300MB/s transfers da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C) da1 at ncr0 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI2 device da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) da2 at ncr0 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI2 device da2: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) da3 at ncr0 bus 0 target 2 lun 0 da3: Fixed Direct Access SCSI2 device da3: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) da4 at ncr0 bus 0 target 3 lun 0 da4: Fixed Direct Access SCSI2 device da4: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) cd0 at ahc0 bus 0 target 0 lun 0 cd0: < CRW620 2.03> Removable CD-ROM SCSI2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present changing root device to da2s1a (da4:ncr0:0:3:0): tagged openings now 31 (da2:ncr0:0:1:0): tagged openings now 30 (da4:ncr0:0:3:0): tagged openings now 29 ncr0: timeout nccb=f09dda00 (skip) ncr0: timeout nccb=f0996400 (skip) ncr0: timeout nccb=f098aa00 (skip) ncr0: timeout nccb=f0989600 (skip) ncr0: timeout nccb=f0989a00 (skip) ncr0: timeout nccb=f0989c00 (skip) ncr0: timeout nccb=f0989e00 (skip) ncr0: timeout nccb=f096de00 (skip) ncr0: timeout nccb=f096c000 (skip) (da2:ncr0:0:1:0): tagged openings now 27 ncr0: timeout nccb=f0a7e000 (skip) ncr0: timeout nccb=f09dde00 (skip) ncr0: timeout nccb=f09b2800 (skip) ncr0: timeout nccb=f09b2a00 (skip) ncr0: timeout nccb=f09b2c00 (skip) ncr0: timeout nccb=f09b2e00 (skip) (da2:ncr0:0:1:0): tagged openings now 23 ncr0: timeout nccb=f0989800 (skip) ncr0: timeout nccb=f0989a00 (skip) ncr0: timeout nccb=f0989c00 (skip) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 17 20:07:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15020 for freebsd-scsi-outgoing; Thu, 17 Sep 1998 20:07:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14970 for ; Thu, 17 Sep 1998 20:07:16 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id VAA09134; Thu, 17 Sep 1998 21:00:24 -0600 (MDT) Date: Thu, 17 Sep 1998 21:00:24 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809180300.VAA09134@narnia.plutotech.com> To: Tor.Egge@fast.no cc: scsi@FreeBSD.ORG Subject: Re: aic7xxx.c: Fatal trap 12: page fault while in kernel mode Newsgroups: pluto.freebsd.scsi In-Reply-To: <199809172156.XAA20501@midten.fast.no> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199809172156.XAA20501@midten.fast.no> you wrote: > > With target mode disabled and 255 scbs available, scb index > TARGET_CMD_CMPLT (0xfe) is used for normal commands. Unfortunately, > ahc_intr does not check for target mode being enabled when the scb index > is TARGET_CMD_CMPLT. > > A suggested fix is appended. Serves me right for committing the driver with my "hack target mode cdb queuing" still in it. The suggested fix looks fine and will be committed shortly. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 17 20:36:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21271 for freebsd-scsi-outgoing; Thu, 17 Sep 1998 20:36:49 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21180 for ; Thu, 17 Sep 1998 20:36:07 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id VAA07472; Thu, 17 Sep 1998 21:35:36 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809180335.VAA07472@panzer.plutotech.com> Subject: Re: CAM/ncr messages.. In-Reply-To: <13825.46672.35984.907842@tbuswell.ne.mediaone.net> from Ted Buswell at "Sep 17, 98 09:35:49 pm" To: tbuswell@mediaone.net (Ted Buswell) Date: Thu, 17 Sep 1998 21:35:36 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Ted Buswell wrote... > > On a -current system that was CVSup'd and installed today, I'm > getting some interesting messages and was wondering if > anyone had any insight. The messages occur when doing > significant I/O [rm -rf, buildworld, etc.] No softupdates > or anything. > > Attached is my dmesg output. > ncr.c is rev 1.128 > cam_xpt.c is rev 1.5 Justin fixed some more bugs in the NCR driver today that might help your problem. Get revision 1.129 of ncr.c, and see if that helps. The problems in the earlier versions of the NCR driver are basically caused by drives that send queue full messages. I see you have a number of Atlas II drives. You'll get lots of queue full messages from them, which would cause the problem you're seeing. The firmware on your Atlas II's (LXY4) is also somewhat buggy. The newer LYK8 firmware fixes some of the bugs: ftp://ftp.quantum.com/Firmware/Atlas-II/LYK8/ When there is a high amount of traffic on the bus, drives with the LXY4 firmware sometimes just go "out to lunch" and don't come back. CAM deals with this by sending a BDR to the device after 10 seconds to wake it up. With the LYK8 firmware, the drives won't go "out to lunch", but they will still send the queue full messages continually. We deal with this via quirk entries for the Atlas II that don't let the number of queue entries go below 24. You may not run into this problem since you're not running at Ultra speeds. I ran into it quite frequently on one of my machines at work that has two Atlas II's and a Plextor CDROM on an Adaptec 2940. If you see your drives behaving like that, though, upgrading the firmware may help. > Should messages like this be going to -scsi or -current? You'll probably get a faster response by mailing -scsi. Sometimes there is a lot of noise (and lag) on -current. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 17 20:38:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21569 for freebsd-scsi-outgoing; Thu, 17 Sep 1998 20:38:04 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21514 for ; Thu, 17 Sep 1998 20:37:52 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id VAA11109; Thu, 17 Sep 1998 21:31:02 -0600 (MDT) Date: Thu, 17 Sep 1998 21:31:02 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809180331.VAA11109@narnia.plutotech.com> To: Ted Buswell cc: scsi@FreeBSD.ORG Subject: Re: CAM/ncr messages.. Newsgroups: pluto.freebsd.scsi In-Reply-To: <13825.46672.35984.907842@tbuswell.ne.mediaone.net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <13825.46672.35984.907842@tbuswell.ne.mediaone.net> you wrote: > > On a -current system that was CVSup'd and installed today, I'm > getting some interesting messages and was wondering if > anyone had any insight. The messages occur when doing > significant I/O [rm -rf, buildworld, etc.] No softupdates > or anything. You need rev 1.129 of ncr.c. I committed a patch (cross fingers) for this problem. > Should messages like this be going to -scsi or -current? scsi is better for me. I only skim -current due to volume, but I read all messages on -scsi. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 06:14:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23530 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 06:14:42 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23525 for ; Fri, 18 Sep 1998 06:14:38 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.1/8.9.1) with ESMTP id JAA02080; Fri, 18 Sep 1998 09:14:09 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <199809181314.JAA02080@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Justin T. Gibbs" cc: Ted Buswell , scsi@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: CAM/ncr messages.. References: <199809180331.VAA11109@narnia.plutotech.com> In-reply-to: Your message of "Thu, 17 Sep 1998 21:31:02 MDT." <199809180331.VAA11109@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Sep 1998 09:14:09 -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm still getting hangs during boot with the 1.129 version of ncr.c. It's a succession of ncr0: timeout nccb= It does this for quite a while, never finding and SCSI devices. I have to punch the reset button to restart the system. Here's an excerpt from a non-CAM kernel (that I backed up to) to see the SCSI configuration. Note that all the devices on the SCSI bus a narrow devices. ... de0: address 00:80:c8:0d:15:9f ncr0: rev 0x02 int a irq 15 on pci0.20.0 scbus0 at ncr0 bus 0 sd0 at scbus0 target 1 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: 10.0 MB/s (100 ns, offset 8) 2049MB (4197520 512 byte sectors) sd0: with 3045 cyls, 16 heads, and an average 86 sectors/track st0 at scbus0 target 2 lun 0 st0: type 1 removable SCSI 2 st0: Sequential-Access st0: 5.0 MB/s (200 ns, offset 8) density code 0x24, 512-byte blocks, write-enabled ch0 at scbus0 target 2 lun 1 ch0: type 8 removable SCSI 2 ch0: Medium-Changer 4 slots, 1 drive, 1 picker cd0 at scbus0 target 3 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd0: 4.0 MB/s (250 ns, offset 8) can't get the size worm0 at scbus0 target 5 lun 0 worm0: type 5 removable SCSI 2 worm0: Write-Once sd1 at scbus0 target 6 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access sd1: 10.0 MB/s (100 ns, offset 8) 2047MB (4194058 512 byte sectors) sd1: with 3703 cyls, 9 heads, and an average 125 sectors/track Probing for devices on the ISA bus: .... This isn't too much to go on; is there any other information I can gather on the next boot attempts? And debug knobs to twiddle? I've successfully converted another Adaptec based machine to CAM and ELF; this system is converted to ELF, but still running the old non-CAM kernel. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 07:47:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04819 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 07:47:23 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from friley-185-114.res.iastate.edu (friley-185-114.res.iastate.edu [129.186.185.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04802 for ; Fri, 18 Sep 1998 07:47:20 -0700 (PDT) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Received: from friley-185-114.res.iastate.edu (loopback [127.0.0.1]) by friley-185-114.res.iastate.edu (8.9.1/8.9.1) with ESMTP id JAA05183 for ; Fri, 18 Sep 1998 09:46:55 -0500 (CDT) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Message-Id: <199809181446.JAA05183@friley-185-114.res.iastate.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG Subject: Verbosity of CAM.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Sep 1998 09:46:55 -0500 From: Chris Csanady Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have some machines at work, and whenever I do lots of disk io, I get tons of the "tagged openings now XX" messages. I noticed that this is due to line 2819 in cam_xpt.c: if (bootverbose || 1) { xpt_print_path(crs->ccb_h.path); printf("tagged openings " "now %d\n", crs->openings); } Would it be possible to remove this 1 before the 3.0 release? -Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 08:18:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07754 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 08:18:49 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tbuswell.ne.mediaone.net (tbuswell.ne.mediaone.net [24.128.24.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07749 for ; Fri, 18 Sep 1998 08:18:47 -0700 (PDT) (envelope-from tbuswell@tbuswell.ne.mediaone.net) Received: (from tbuswell@localhost) by tbuswell.ne.mediaone.net (8.9.1/8.8.8) id LAA00355; Fri, 18 Sep 1998 11:17:28 -0400 (EDT) (envelope-from tbuswell) From: Ted Buswell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 18 Sep 1998 11:17:27 -0400 (EDT) To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG, gibbs@narnia.plutotech.com Subject: Re: CAM/ncr messages.. In-Reply-To: <199809180335.VAA07472@panzer.plutotech.com> References: <13825.46672.35984.907842@tbuswell.ne.mediaone.net> <199809180335.VAA07472@panzer.plutotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13826.30510.420123.343940@tbuswell.ne.mediaone.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry writes: > Justin fixed some more bugs in the NCR driver today that might help your > problem. Get revision 1.129 of ncr.c, and see if that helps. I obtained 1.129 and after some initial testing, the timeout messages seem to have gone away. > still send the queue full messages continually. We deal with this via > quirk entries for the Atlas II that don't let the number of queue entries > go below 24. My "tagged openings" messages would go below the 24 that you're talking about here; problem was that my disks are diff and the inquiry is "XP34550WD" which is not matched by the "XP34550?" string in the quirks table. Attached is a patch for cam_xpt.c. I'll probably try the fw update you mentioned, as soon as quantum's NT ftp server lets me do an 'ls'. Thanks CAM team, this stuff looks like it's going to really kick ass! -Ted Index: cam_xpt.c =================================================================== RCS file: /home/ncvs/src/sys/cam/cam_xpt.c,v retrieving revision 1.6 diff -r1.6 cam_xpt.c 244c244 < { T_DIRECT, SIP_MEDIA_FIXED, quantum, "XP34550?", "*" }, --- > { T_DIRECT, SIP_MEDIA_FIXED, quantum, "XP34550*", "*" }, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 08:58:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12984 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 08:58:32 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12972 for ; Fri, 18 Sep 1998 08:58:30 -0700 (PDT) (envelope-from scsi@artorius.sunflower.com) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by artorius.sunflower.com (8.8.8/8.8.7) with SMTP id KAA17180 for ; Fri, 18 Sep 1998 10:58:11 -0500 (CDT) (envelope-from scsi@artorius.sunflower.com) Date: Fri, 18 Sep 1998 10:58:11 -0500 (CDT) From: "Stephen D. Spencer" To: scsi@FreeBSD.ORG Subject: losing drives in a ccd array 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 --begin system information-- FreeBSD 2.2-980705-SNAP + 2.2CAM-19980716-SNAP.diffs 7 of these (ccd0) (da5-da11) da6 at ahc1 bus 0 target 2 lun 0 da6: Fixed Direct Access SCSI2 device da6: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da6: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) on 3 of these ahc1 rev 1 int a irq 9 on pci0:17:0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs /dev/ccd0 is mounted async --begin error message-- Unexpected busfree. LASTPHASE == 0x0 SEQADDR == 0x10e (da11:ahc3:0:2:0): lost device (da11:ahc3:0:2:0): Invalidating pack (da11:ahc3:0:2:0): Invalidating pack (da11:ahc3:0:2:0): Invalidating pack (da11:ahc3:0:2:0): Invalidating pack (da11:ahc3:0:2:0): Invalidating pack (da11:ahc3:0:2:0): WRITE(10). CDB: 2a 0 0 6d 1 70 0 0 10 0 (da11:ahc3:0:2:0): UNIT ATTENTION asc:29,1 (da11:ahc3:0:2:0): Power on occurred field replaceable unit: 1 biodone: buffer already done biodone: buffer already done -------------------------- This machine is a usenet server so it does quite a bit of disk i/o. Any help in interpreting the above error messages would be greatly appreciated. Thanks in advance. Regards, Stephen Spencer Sunflower Datavision Lawrence, KS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 09:05:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13814 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 09:05:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13801 for ; Fri, 18 Sep 1998 09:05:44 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id JAA15014; Fri, 18 Sep 1998 09:58:49 -0600 (MDT) Date: Fri, 18 Sep 1998 09:58:49 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809181558.JAA15014@narnia.plutotech.com> To: Chris Csanady cc: scsi@FreeBSD.ORG Subject: Re: Verbosity of CAM.. Newsgroups: pluto.freebsd.scsi In-Reply-To: <199809181446.JAA05183@friley-185-114.res.iastate.edu> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199809181446.JAA05183@friley-185-114.res.iastate.edu> you wrote: > > Would it be possible to remove this 1 before the 3.0 release? > Perhaps. Perhaps not. The messages should stop after the tag count has settled. Right now, these messages have already helped diagnose at least one problem the NCR driver. They also provide a good indication of the load on the SCSI system that leads up to errors. I don't want to remove a useful diagnostic utility until we're sure the kinks are worked out. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 09:42:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18541 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 09:42:39 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18530 for ; Fri, 18 Sep 1998 09:42:29 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id SAA00438 for ; Fri, 18 Sep 1998 18:42:05 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA16653; Fri, 18 Sep 1998 18:42:04 +0200 (MET DST) Message-ID: <19980918184204.00622@follo.net> Date: Fri, 18 Sep 1998 18:42:04 +0200 From: Eivind Eklund To: scsi@FreeBSD.ORG Subject: Fixing LINT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following patch fix LINT to compile again. Anybody here that mind if I commit it? Eivind. Index: LINT =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/LINT,v retrieving revision 1.470 diff -u -r1.470 LINT --- LINT 1998/09/18 00:46:41 1.470 +++ LINT 1998/09/18 16:25:21 @@ -879,19 +879,19 @@ # controller bt0 at isa? port "IO_BT0" cam irq ? -controller adv0 at isa? port ? cam irq ? -controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr -controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr - -controller aic0 at isa? port 0x340 bio irq 11 vector aicintr -controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr -controller nca1 at isa? port 0x1f84 -controller nca2 at isa? port 0x1f8c -controller nca3 at isa? port 0x1e88 -controller nca4 at isa? port 0x350 bio irq 5 vector ncaintr +#!CAM# controller adv0 at isa? port ? cam irq ? +#!CAM# controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr +#!CAM# controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr + +#!CAM# controller aic0 at isa? port 0x340 bio irq 11 vector aicintr +#!CAM# controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr +#!CAM# controller nca1 at isa? port 0x1f84 +#!CAM# controller nca2 at isa? port 0x1f8c +#!CAM# controller nca3 at isa? port 0x1e88 +#!CAM# controller nca4 at isa? port 0x350 bio irq 5 vector ncaintr -controller sea0 at isa? bio irq 5 iomem 0xdc000 iosiz 0x2000 vector seaintr -controller wds0 at isa? port 0x350 bio irq 15 drq 6 vector wdsintr +#!CAM# controller sea0 at isa? bio irq 5 iomem 0xdc000 iosiz 0x2000 vector seaintr +#!CAM# controller wds0 at isa? port 0x350 bio irq 15 drq 6 vector wdsintr # # ST-506, ESDI, and IDE hard disks: `wdc' and `wd' @@ -1462,7 +1462,7 @@ controller ahc1 controller ncr0 controller isp0 -controller amd0 +#!CAM# controller amd0 device de0 device fxp0 device tl0 @@ -1558,7 +1558,7 @@ # ppc ISA-bus parallel port interfaces. # controller ppbus0 -controller vpo0 at ppbus? +#!CAM# controller vpo0 at ppbus? device nlpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? @@ -1709,9 +1709,9 @@ # DPT options options DPT_VERIFY_HINTR options DPT_RESTRICTED_FREELIST -options DPT_MEASURE_PERFORMANCE +#!CAM# options DPT_MEASURE_PERFORMANCE options DPT_FREELIST_IS_STACK -options DPT_HANDLE_TIMEOUTS +#!CAM# options DPT_HANDLE_TIMEOUTS options DPT_TIMEOUT_FACTOR=4 options DPT_INTR_DELAY=200 # Some motherboards need that options DPT_LOST_IRQ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 09:49:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19267 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 09:49:55 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from opi.flirtbox.ch ([62.48.0.50]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA19260 for ; Fri, 18 Sep 1998 09:49:50 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 27321 invoked from network); 18 Sep 1998 16:48:29 -0000 Received: from unknown (HELO pipeline.ch) (195.134.140.2) by opi.flirtbox.ch with SMTP; 18 Sep 1998 16:48:29 -0000 Message-ID: <36028F15.83040AFA@pipeline.ch> Date: Fri, 18 Sep 1998 18:49:25 +0200 From: Andre Oppermann Organization: Internet Business Solutions Ltd. X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Adaptec RAID supported? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello CAM guys Are the Adaptec ARO-1130CA or ARO-1130SA RAIDPortII Cards supported by FreeBSD? There is an DOS based software for setup of the array. TIA -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 10:02:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20993 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 10:02:50 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20980 for ; Fri, 18 Sep 1998 10:02:48 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id KAA05213; Fri, 18 Sep 1998 10:02:21 -0700 Date: Fri, 18 Sep 1998 10:02:21 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Stephen D. Spencer" cc: scsi@FreeBSD.ORG Subject: Re: losing drives in a ccd array 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 Sounds like a power failure for that drive occurred. Justin, Ken- aren't you retrying disk operations? On Fri, 18 Sep 1998, Stephen D. Spencer wrote: > > --begin system information-- > > FreeBSD 2.2-980705-SNAP + 2.2CAM-19980716-SNAP.diffs > > 7 of these (ccd0) (da5-da11) > da6 at ahc1 bus 0 target 2 lun 0 > da6: Fixed Direct Access SCSI2 device > da6: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing > Enabled > da6: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) > > on 3 of these > ahc1 rev 1 int a irq 9 on pci0:17:0 > ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > /dev/ccd0 is mounted async > > --begin error message-- > > Unexpected busfree. LASTPHASE == 0x0 > SEQADDR == 0x10e > (da11:ahc3:0:2:0): lost device > (da11:ahc3:0:2:0): Invalidating pack > (da11:ahc3:0:2:0): Invalidating pack > (da11:ahc3:0:2:0): Invalidating pack > (da11:ahc3:0:2:0): Invalidating pack > (da11:ahc3:0:2:0): Invalidating pack > (da11:ahc3:0:2:0): WRITE(10). CDB: 2a 0 0 6d 1 70 0 0 10 0 > (da11:ahc3:0:2:0): UNIT ATTENTION asc:29,1 > (da11:ahc3:0:2:0): Power on occurred field replaceable unit: 1 > biodone: buffer already done > biodone: buffer already done > > -------------------------- > > This machine is a usenet server so it does quite a bit of disk i/o. > Any help in interpreting the above error messages would be greatly > appreciated. > > Thanks in advance. > > Regards, > Stephen Spencer > Sunflower Datavision > Lawrence, KS > > > > > > > > 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 Fri Sep 18 10:07:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21967 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 10:07:55 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21960 for ; Fri, 18 Sep 1998 10:07:53 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id LAA10835; Fri, 18 Sep 1998 11:07:23 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809181707.LAA10835@panzer.plutotech.com> Subject: Re: Fixing LINT In-Reply-To: <19980918184204.00622@follo.net> from Eivind Eklund at "Sep 18, 98 06:42:04 pm" To: eivind@yes.no (Eivind Eklund) Date: Fri, 18 Sep 1998 11:07:22 -0600 (MDT) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Eivind Eklund wrote... > The following patch fix LINT to compile again. Anybody here that mind > if I commit it? A number of these are wrong: > =================================================================== > RCS file: /home/ncvs/src/sys/i386/conf/LINT,v > retrieving revision 1.470 > diff -u -r1.470 LINT > --- LINT 1998/09/18 00:46:41 1.470 > +++ LINT 1998/09/18 16:25:21 > @@ -879,19 +879,19 @@ > # > > controller bt0 at isa? port "IO_BT0" cam irq ? > -controller adv0 at isa? port ? cam irq ? AdvanSys controllers are supported under CAM. > -controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr The Adaptec 154x controllers are also supported under CAM. Also, the "#!CAM#" stuff is kinda tacky, IMO. I would suggest either taking the unsupported controllers out altogether, or else doing something like this: # The following controllers are not supported under CAM, but support may be # brough back someday. #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr [ ...and so on... ] > @@ -1558,7 +1558,7 @@ > # ppc ISA-bus parallel port interfaces. > # > controller ppbus0 > -controller vpo0 at ppbus? > +#!CAM# controller vpo0 at ppbus? I believe this one will be brought back shortly. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 10:22:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24202 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 10:22:50 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24166; Fri, 18 Sep 1998 10:22:45 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id TAA15964; Fri, 18 Sep 1998 19:21:49 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id TAA01549; Fri, 18 Sep 1998 19:16:11 +0200 (MET DST) (envelope-from j) Message-ID: <19980918191611.12243@uriah.heep.sax.de> Date: Fri, 18 Sep 1998 19:16:11 +0200 From: J Wunsch To: Chris Shenton Cc: questions@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: st0: 262144-byte record too big (reading SGI tar tape) Reply-To: Joerg Wunsch References: <87hfy6wqgd.fsf@absinthe.shenton.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <87hfy6wqgd.fsf@absinthe.shenton.org>; from Chris Shenton on Thu, Sep 17, 1998 at 02:21:06PM -0400 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Chris Shenton wrote: > I'm trying to restore files from tar image tape made on an > SGI. Whether I use "dd" or "tar" I get the same complaint in syslog: > > st0: 262144-byte record too big You cannot read SGI tapes (with their default blocksize) on FreeBSD, due to limitations in physio(9) (which have been constrained by older SCSI controllers that cannot handle more than 16 scatter/gather segments). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 10:46:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27049 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 10:46:04 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26985 for ; Fri, 18 Sep 1998 10:46:00 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id TAA00998; Fri, 18 Sep 1998 19:45:34 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id TAA16855; Fri, 18 Sep 1998 19:45:34 +0200 (MET DST) Message-ID: <19980918194533.52865@follo.net> Date: Fri, 18 Sep 1998 19:45:33 +0200 From: Eivind Eklund To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: Fixing LINT References: <19980918184204.00622@follo.net> <199809181707.LAA10835@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199809181707.LAA10835@panzer.plutotech.com>; from Kenneth D. Merry on Fri, Sep 18, 1998 at 11:07:22AM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Sep 18, 1998 at 11:07:22AM -0600, Kenneth D. Merry wrote: > Eivind Eklund wrote... > > The following patch fix LINT to compile again. Anybody here that mind > > if I commit it? > > A number of these are wrong: No. All of them were necessary to get LINT to compile and link. > > =================================================================== > > RCS file: /home/ncvs/src/sys/i386/conf/LINT,v > > retrieving revision 1.470 > > diff -u -r1.470 LINT > > --- LINT 1998/09/18 00:46:41 1.470 > > +++ LINT 1998/09/18 16:25:21 > > @@ -879,19 +879,19 @@ > > # > > > > controller bt0 at isa? port "IO_BT0" cam irq ? > > -controller adv0 at isa? port ? cam irq ? > > AdvanSys controllers are supported under CAM. It doesn't link. (This is first-order due to a commented out part of files.i386, IIRC). > > -controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr > > The Adaptec 154x controllers are also supported under CAM. It doesn't link, either. Same reason. > Also, the "#!CAM#" stuff is kinda tacky, IMO. I would suggest either > taking the unsupported controllers out altogether, or else doing something > like this: > > # The following controllers are not supported under CAM, but support may be > # brough back someday. > #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr > #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr > [ ...and so on... ] I seem to remember the controller probe order is significant, so it seems slightly dumb to loose that information - if somebody try to convert a driver, it may not work, even though it would work if probed in the correct order. I know the !CAM stuff is tacky, but so is not indicating why the options are commented out is bad too. Besides, I assume the comments will have a short life, as the drivers are either fixed or removed from the tree. > > @@ -1558,7 +1558,7 @@ > > # ppc ISA-bus parallel port interfaces. > > # > > controller ppbus0 > > -controller vpo0 at ppbus? > > +#!CAM# controller vpo0 at ppbus? > > I believe this one will be brought back shortly. Great! Still, it block LINT from compiling/linking at the moment. (It is unfortunate that the CAM team didn't use it as resource during development, but these things happen - let us now get it fixed :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 11:01:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28626 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 11:01:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from absinthe.shenton.org (Absinthe.Shenton.Org [209.31.147.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28596; Fri, 18 Sep 1998 11:01:06 -0700 (PDT) (envelope-from chris@shenton.org) Received: (from chris@localhost) by absinthe.shenton.org (8.9.1/8.9.1) id NAA06910; Fri, 18 Sep 1998 13:58:50 -0400 (EDT) To: Joerg Wunsch Cc: questions@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: st0: 262144-byte record too big (reading SGI tar tape) References: <87hfy6wqgd.fsf@absinthe.shenton.org> <19980918191611.12243@uriah.heep.sax.de> X-Emacs: Emacs 20.3, MULE 4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.8.5 - "Nishi-Takaoka") Content-Type: text/plain; charset=US-ASCII From: Chris Shenton Date: 18 Sep 1998 13:58:49 -0400 In-Reply-To: J Wunsch's message of "Fri, 18 Sep 1998 19:16:11 +0200" Message-ID: <87k931fgkm.fsf@absinthe.shenton.org> Lines: 11 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org J Wunsch writes: > You cannot read SGI tapes (with their default blocksize) on FreeBSD, > due to limitations in physio(9) (which have been constrained by older > SCSI controllers that cannot handle more than 16 scatter/gather > segments). Any suggestions for blocksize? The "st" man page suggests a maximum of 64KB so I was thinking 32K. Should that be OK? Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 11:30:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05648 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 11:30:36 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA05458; Fri, 18 Sep 1998 11:30:04 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA09782 (5.67b/IDA-1.5); Fri, 18 Sep 1998 20:01:48 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id SAA00725; Fri, 18 Sep 1998 18:23:52 +0200 (CEST) From: Wilko Bulte Message-Id: <199809181623.SAA00725@yedi.iaf.nl> Subject: Re: st0: 262144-byte record too big (reading SGI tar tape) In-Reply-To: <87hfy6wqgd.fsf@absinthe.shenton.org> from Chris Shenton at "Sep 17, 98 02:21:06 pm" To: chris@absinthe.shenton.org (Chris Shenton) Date: Fri, 18 Sep 1998 18:23:52 +0200 (CEST) Cc: questions@FreeBSD.ORG, scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Chris Shenton wrote... > I'm trying to restore files from tar image tape made on an > SGI. Whether I use "dd" or "tar" I get the same complaint in syslog: > > st0: 262144-byte record too big > > I've tried various "bs=" and "conv=" to dd but get the same error so I > suspect the "st" driver is upset with the tape. 262144 bytes is 256KB > which seems unlikely to be a coincidence. FreeBSD currently cannot handle records > 64kB. > This is on an Archive (Connor/Seagate) Python 4mm DDS2 which I've used > successfully for Amanda. Kernel is 2.2.7-STABLE with a 2.2.6-STABLE > OS. > > Any hints on how to recover this tape? Write another on the SGI.. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 12:05:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11751 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 12:05:42 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11746 for ; Fri, 18 Sep 1998 12:05:41 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id MAA15386; Fri, 18 Sep 1998 12:58:53 -0600 (MDT) Date: Fri, 18 Sep 1998 12:58:53 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809181858.MAA15386@narnia.plutotech.com> To: mjacob@feral.com cc: scsi@FreeBSD.ORG Subject: Re: losing drives in a ccd array Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > Sounds like a power failure for that drive occurred. > > Justin, Ken- aren't you retrying disk operations? We are. Actually a couple things happened here and perhaps it show that CAM is trying to be just "too smart" in situations like this: 1) One of the drives in this system experienced a power spike or lossage. It may be that your power-supply for this enclosure is not quite up to snuff and craps out if you have enough seek activity on all the drives in the enclosure, but this is a secondary issue. 2) The aic7xxx driver saw the bus go free unexpectedly since it was talking to this device when it lost power. 3) The peripheral driver got an "unexpected bus free" error code which is a retry-able offsense. 4) The transaction was retried, but we got a selection timeout. 5) The peripheral driver interpreted the selection timeout as, "Crap the device has gone away". 6) We invalidated the pack, returned EIO for all pending buffers, and setup for device removal. There are some bugs here caused by missing support for the XPT_ABORT_CCB function code and that we don't necessarily wait for all CCBs to be returned to the peripheral driver before device removal, but that isn't too important for this discussion. 7) One of the last I/Os did finally get through and we see the enexpected UA. There are lots of problems (most already on my whiteboard): a single selection timeout shouldn't nuke a device, our policy of treating unexpected UAs as fatal may be too extreme considering the fact that we don't have even a reasonable scheme in place yet to determine if the device hasn't changed out from under us, XPT_ABORT_CCB really needs to be implemented before 3.0. We may want to completely disable the "selection timeout invalidates a device" before 3.0 until we have more discussion on how to deal with these kinds of errors. Luckily all of this is really easy to adjust in the CAM error recovery code. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 12:06:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11874 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 12:06:55 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11868 for ; Fri, 18 Sep 1998 12:06:54 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id MAA15393; Fri, 18 Sep 1998 12:59:59 -0600 (MDT) Date: Fri, 18 Sep 1998 12:59:59 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809181859.MAA15393@narnia.plutotech.com> To: Andre Oppermann cc: scsi@FreeBSD.ORG Subject: Re: Adaptec RAID supported? Newsgroups: pluto.freebsd.scsi In-Reply-To: <36028F15.83040AFA@pipeline.ch> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <36028F15.83040AFA@pipeline.ch> you wrote: > Hello CAM guys > > Are the Adaptec ARO-1130CA or ARO-1130SA RAIDPortII Cards supported > by FreeBSD? As independent SCSI controllers, yes. In RAID configurations, no. I don't know when/if the state of RAID support will change. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 12:25:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13604 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 12:25:05 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA13595 for ; Fri, 18 Sep 1998 12:25:02 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zK68q-0004Wx-00; Fri, 18 Sep 1998 13:24:28 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id NAA28114; Fri, 18 Sep 1998 13:25:54 -0600 (MDT) Message-Id: <199809181925.NAA28114@harmony.village.org> To: Eivind Eklund Subject: Re: Fixing LINT Cc: "Kenneth D. Merry" , scsi@FreeBSD.ORG In-reply-to: Your message of "Fri, 18 Sep 1998 19:45:33 +0200." <19980918194533.52865@follo.net> References: <19980918194533.52865@follo.net> <19980918184204.00622@follo.net> <199809181707.LAA10835@panzer.plutotech.com> Date: Fri, 18 Sep 1998 13:25:54 -0600 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19980918194533.52865@follo.net> Eivind Eklund writes: : It doesn't link, either. Same reason. What are you talking about? It links and works fine for me. I've been using it to access my cdrom changer for a few weeks. The file that is commented out in sys/i386/conf/files.i386 is the OLD aha driver. The new one is in both the sys/conf/files and sys/i386/conf/files.i386 files. What is missing for you? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 12:29:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14161 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 12:29:40 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14155 for ; Fri, 18 Sep 1998 12:29:38 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id NAA15474; Fri, 18 Sep 1998 13:22:49 -0600 (MDT) Date: Fri, 18 Sep 1998 13:22:49 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809181922.NAA15474@narnia.plutotech.com> To: "Johan Granlund" cc: scsi@FreeBSD.ORG Subject: Re: CAM and exabyte EXB-8200 problems Newsgroups: pluto.freebsd.current In-Reply-To: <199809181605.SAA00314@phoenix.granlund.nu> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199809181605.SAA00314@phoenix.granlund.nu> you wrote: > Hi > > I got a small problem (TM) after uppgrading to CAM, my tapestation is > hanging on boot. This is an old Exabyte 8200. When looking at a boot -v > it hangs when all devices EXCEPT the tapestation has been found. This is > a fullblown SCSI hang with the busylamp on > > The exabyte is doing a lengthy recalibration on a SCSI reset. When looking > on the output from a preCAM boot i got a couple of busy timeouts. > SCSI_DELAY=30000 (30sec) > > Is appendig two boot -v outputs one precam (beetwen E-Day and C-Day) and > one without the tape from today at 17:00 CEDT > > Any solutions? I need a bit more information. This is likely a bug in the handling of the BUSY status code. A boot with -v with the tape drive hooked up (I know it will hang...) would help a lot. > /Johan -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 12:36:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15271 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 12:36:22 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15261 for ; Fri, 18 Sep 1998 12:36:14 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id VAA02145; Fri, 18 Sep 1998 21:35:37 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA17395; Fri, 18 Sep 1998 21:35:35 +0200 (MET DST) Message-ID: <19980918213533.18854@follo.net> Date: Fri, 18 Sep 1998 21:35:33 +0200 From: Eivind Eklund To: Warner Losh Cc: "Kenneth D. Merry" , scsi@FreeBSD.ORG Subject: Re: Fixing LINT References: <19980918194533.52865@follo.net> <19980918184204.00622@follo.net> <199809181707.LAA10835@panzer.plutotech.com> <19980918194533.52865@follo.net> <199809181925.NAA28114@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199809181925.NAA28114@harmony.village.org>; from Warner Losh on Fri, Sep 18, 1998 at 01:25:54PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Sep 18, 1998 at 01:25:54PM -0600, Warner Losh wrote: > In message <19980918194533.52865@follo.net> Eivind Eklund writes: > : It doesn't link, either. Same reason. > > What are you talking about? It links and works fine for me. I've > been using it to access my cdrom changer for a few weeks. The file > that is commented out in sys/i386/conf/files.i386 is the OLD aha > driver. The new one is in both the sys/conf/files and > sys/i386/conf/files.i386 files. What is missing for you? That LINT compiles and link, as it is supposed to do at all times. At least bde and I use it as a tool for doing global kernel checks; more people should (after any large-scale change, LINT should compile with no new warnings). However, after looking some more at this, I found (about 1 minute before I got your mail :-) that the problem for aha is that the wrong aha line is in LINT, and for adv that it has non-compilable code inside #ifdef DIAGNOSTIC. I've copied the correct aha line over, and commented out adv from LINT for the time being. New diffs are: Index: LINT =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/LINT,v retrieving revision 1.470 diff -u -r1.470 LINT --- LINT 1998/09/18 00:46:41 1.470 +++ LINT 1998/09/18 19:28:12 @@ -879,19 +879,20 @@ # controller bt0 at isa? port "IO_BT0" cam irq ? -controller adv0 at isa? port ? cam irq ? -controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr -controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr - -controller aic0 at isa? port 0x340 bio irq 11 vector aicintr -controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr -controller nca1 at isa? port 0x1f84 -controller nca2 at isa? port 0x1f8c -controller nca3 at isa? port 0x1e88 -controller nca4 at isa? port 0x350 bio irq 5 vector ncaintr +# adv is broken when DIAGNOSTIC is defined +#controller adv0 at isa? port ? cam irq ? +controller aha0 at isa? port ? cam irq ? +#!CAM# controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr + +#!CAM# controller aic0 at isa? port 0x340 bio irq 11 vector aicintr +#!CAM# controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr +#!CAM# controller nca1 at isa? port 0x1f84 +#!CAM# controller nca2 at isa? port 0x1f8c +#!CAM# controller nca3 at isa? port 0x1e88 +#!CAM# controller nca4 at isa? port 0x350 bio irq 5 vector ncaintr -controller sea0 at isa? bio irq 5 iomem 0xdc000 iosiz 0x2000 vector seaintr -controller wds0 at isa? port 0x350 bio irq 15 drq 6 vector wdsintr +#!CAM# controller sea0 at isa? bio irq 5 iomem 0xdc000 iosiz 0x2000 vector seaintr +#!CAM# controller wds0 at isa? port 0x350 bio irq 15 drq 6 vector wdsintr # # ST-506, ESDI, and IDE hard disks: `wdc' and `wd' @@ -1462,7 +1463,7 @@ controller ahc1 controller ncr0 controller isp0 -controller amd0 +#!CAM# controller amd0 device de0 device fxp0 device tl0 @@ -1558,7 +1559,7 @@ # ppc ISA-bus parallel port interfaces. # controller ppbus0 -controller vpo0 at ppbus? +#!CAM# controller vpo0 at ppbus? device nlpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? @@ -1709,9 +1710,9 @@ # DPT options options DPT_VERIFY_HINTR options DPT_RESTRICTED_FREELIST -options DPT_MEASURE_PERFORMANCE +#!CAM# options DPT_MEASURE_PERFORMANCE options DPT_FREELIST_IS_STACK -options DPT_HANDLE_TIMEOUTS +#!CAM# options DPT_HANDLE_TIMEOUTS options DPT_TIMEOUT_FACTOR=4 options DPT_INTR_DELAY=200 # Some motherboards need that options DPT_LOST_IRQ Any protests this time around? (I can't easily fix the adv driver, as it is mumbling about missing symbols that I have no idea where have come from or gone to). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 13:13:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22789 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 13:13:02 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22784 for ; Fri, 18 Sep 1998 13:12:58 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id OAA11933; Fri, 18 Sep 1998 14:12:23 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809182012.OAA11933@panzer.plutotech.com> Subject: Re: Fixing LINT In-Reply-To: <19980918213533.18854@follo.net> from Eivind Eklund at "Sep 18, 98 09:35:33 pm" To: eivind@yes.no (Eivind Eklund) Date: Fri, 18 Sep 1998 14:12:23 -0600 (MDT) Cc: imp@village.org, ken@plutotech.com, scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com X-Mailer: ELM [version 2.4ME+ PL28s (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 Eivind Eklund wrote... > On Fri, Sep 18, 1998 at 01:25:54PM -0600, Warner Losh wrote: > > In message <19980918194533.52865@follo.net> Eivind Eklund writes: > > : It doesn't link, either. Same reason. > > > > What are you talking about? It links and works fine for me. I've > > been using it to access my cdrom changer for a few weeks. The file > > that is commented out in sys/i386/conf/files.i386 is the OLD aha > > driver. The new one is in both the sys/conf/files and > > sys/i386/conf/files.i386 files. What is missing for you? > > That LINT compiles and link, as it is supposed to do at all times. At > least bde and I use it as a tool for doing global kernel checks; more > people should (after any large-scale change, LINT should compile with > no new warnings). > > However, after looking some more at this, I found (about 1 minute > before I got your mail :-) that the problem for aha is that the wrong > aha line is in LINT, and for adv that it has non-compilable code inside > #ifdef DIAGNOSTIC. > > I've copied the correct aha line over, and commented out adv from LINT > for the time being. New diffs are: [ ... ] > @@ -1709,9 +1710,9 @@ > # DPT options > options DPT_VERIFY_HINTR > options DPT_RESTRICTED_FREELIST > -options DPT_MEASURE_PERFORMANCE > +#!CAM# options DPT_MEASURE_PERFORMANCE > options DPT_FREELIST_IS_STACK > -options DPT_HANDLE_TIMEOUTS > +#!CAM# options DPT_HANDLE_TIMEOUTS [ ... ] > Any protests this time around? (I can't easily fix the adv driver, as > it is mumbling about missing symbols that I have no idea where have > come from or gone to). That will probably work. I still think the "#!CAM#" stuff is annoying, but if you insist... Justin can uncomment the adv driver when he checks in a fix. (I think he's got some other, unrelated fixes in the works for that driver.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 13:14:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23123 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 13:14:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23118 for ; Fri, 18 Sep 1998 13:14:20 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id GAA31665; Sat, 19 Sep 1998 06:13:44 +1000 Date: Sat, 19 Sep 1998 06:13:44 +1000 From: Bruce Evans Message-Id: <199809182013.GAA31665@godzilla.zeta.org.au> To: eivind@yes.no, scsi@FreeBSD.ORG Subject: Re: Fixing LINT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >The following patch fix LINT to compile again. Anybody here that mind >if I commit it? This mostly breaks LINT. LINT is supposed to not compile when supported devices are broken. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 13:19:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23928 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 13:19:50 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23916 for ; Fri, 18 Sep 1998 13:19:48 -0700 (PDT) (envelope-from scsi@artorius.sunflower.com) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by artorius.sunflower.com (8.8.8/8.8.7) with SMTP id PAA18162 for ; Fri, 18 Sep 1998 15:19:31 -0500 (CDT) (envelope-from scsi@artorius.sunflower.com) Date: Fri, 18 Sep 1998 10:58:11 -0500 (CDT) From: "Stephen D. Spencer" To: scsi@FreeBSD.ORG Subject: losing drives in a ccd array 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 --begin system information-- FreeBSD 2.2-980705-SNAP + 2.2CAM-19980716-SNAP.diffs 7 of these (ccd0) (da5-da11) da6 at ahc1 bus 0 target 2 lun 0 da6: Fixed Direct Access SCSI2 device da6: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da6: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) on 3 of these ahc1 rev 1 int a irq 9 on pci0:17:0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs /dev/ccd0 is mounted async --begin error message-- Unexpected busfree. LASTPHASE == 0x0 SEQADDR == 0x10e (da11:ahc3:0:2:0): lost device (da11:ahc3:0:2:0): Invalidating pack (da11:ahc3:0:2:0): Invalidating pack (da11:ahc3:0:2:0): Invalidating pack (da11:ahc3:0:2:0): Invalidating pack (da11:ahc3:0:2:0): Invalidating pack (da11:ahc3:0:2:0): WRITE(10). CDB: 2a 0 0 6d 1 70 0 0 10 0 (da11:ahc3:0:2:0): UNIT ATTENTION asc:29,1 (da11:ahc3:0:2:0): Power on occurred field replaceable unit: 1 biodone: buffer already done biodone: buffer already done -------------------------- This machine is a usenet server so it does quite a bit of disk i/o. Any help in interpreting the above error messages would be greatly appreciated. Thanks in advance. Regards, Stephen Spencer Sunflower Datavision Lawrence, KS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 13:20:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24281 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 13:20:30 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24264 for ; Fri, 18 Sep 1998 13:20:27 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id WAA02706; Fri, 18 Sep 1998 22:19:51 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id WAA17626; Fri, 18 Sep 1998 22:19:50 +0200 (MET DST) Message-ID: <19980918221949.40388@follo.net> Date: Fri, 18 Sep 1998 22:19:49 +0200 From: Eivind Eklund To: Bruce Evans , scsi@FreeBSD.ORG Subject: Re: Fixing LINT References: <199809182013.GAA31665@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199809182013.GAA31665@godzilla.zeta.org.au>; from Bruce Evans on Sat, Sep 19, 1998 at 06:13:44AM +1000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Sep 19, 1998 at 06:13:44AM +1000, Bruce Evans wrote: > >The following patch fix LINT to compile again. Anybody here that mind > >if I commit it? > > This mostly breaks LINT. LINT is supposed to not compile when supported > devices are broken. Only adv is supported and broken. The support for the other devices has been removed (but may be added back in later). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 13:29:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25904 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 13:29:36 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25855 for ; Fri, 18 Sep 1998 13:29:20 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id GAA32430; Sat, 19 Sep 1998 06:28:37 +1000 Date: Sat, 19 Sep 1998 06:28:37 +1000 From: Bruce Evans Message-Id: <199809182028.GAA32430@godzilla.zeta.org.au> To: eivind@yes.no, ken@plutotech.com Subject: Re: Fixing LINT Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> A number of these are wrong: > >No. All of them were necessary to get LINT to compile and link. Yes. That's why they are wrong. >> AdvanSys controllers are supported under CAM. > >It doesn't link. (This is first-order due to a commented out part of >files.i386, IIRC). It isn't for adv, but it is for a couple of other drivers, e.g., uha. This commenting out also breaks LINT. config(8) of course can't know about missing files (but it should warn when there are no files for an optional driver). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 15:24:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16717 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 15:24:46 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16706 for ; Fri, 18 Sep 1998 15:24:41 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id IAA06604; Sat, 19 Sep 1998 08:23:51 +1000 Date: Sat, 19 Sep 1998 08:23:51 +1000 From: Bruce Evans Message-Id: <199809182223.IAA06604@godzilla.zeta.org.au> To: eivind@yes.no, imp@village.org Subject: Re: Fixing LINT Cc: ken@plutotech.com, scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Any protests this time around? (I can't easily fix the adv driver, as >it is mumbling about missing symbols that I have no idea where have >come from or gone to). Yes, it defeats the point of LINT. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 16:21:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29023 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 16:21:57 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28952 for ; Fri, 18 Sep 1998 16:21:40 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id RAA13212; Fri, 18 Sep 1998 17:20:58 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809182320.RAA13212@panzer.plutotech.com> Subject: Re: Fixing LINT In-Reply-To: <199809182223.IAA06604@godzilla.zeta.org.au> from Bruce Evans at "Sep 19, 98 08:23:51 am" To: bde@zeta.org.au (Bruce Evans) Date: Fri, 18 Sep 1998 17:20:58 -0600 (MDT) Cc: eivind@yes.no, imp@village.org, ken@plutotech.com, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Bruce Evans wrote... > >Any protests this time around? (I can't easily fix the adv driver, as > >it is mumbling about missing symbols that I have no idea where have > >come from or gone to). > > Yes, it defeats the point of LINT. Well, if you want to add the adv driver back in, feel free to do so. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 16:38:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02134 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 16:38:10 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02076 for ; Fri, 18 Sep 1998 16:37:50 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA11178; Sat, 19 Sep 1998 09:37:02 +1000 Date: Sat, 19 Sep 1998 09:37:02 +1000 From: Bruce Evans Message-Id: <199809182337.JAA11178@godzilla.zeta.org.au> To: bde@zeta.org.au, ken@plutotech.com Subject: Re: Fixing LINT Cc: eivind@yes.no, imp@village.org, scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> >Any protests this time around? (I can't easily fix the adv driver, as >> >it is mumbling about missing symbols that I have no idea where have >> >come from or gone to). >> >> Yes, it defeats the point of LINT. > >Well, if you want to add the adv driver back in, feel free to do so. It's already in, and even compiles unless "options DIAGNOSTIC" is configured. The commented-out driver files are: dpt_control.c aha1542.c (nonexistent - should have been deleted) aic6360.c ncr5380.c seagate.c ultra14f.c Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 18:55:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26738 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 18:55:22 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26711 for ; Fri, 18 Sep 1998 18:55:06 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.1/8.9.1) with ESMTP id VAA00452; Fri, 18 Sep 1998 21:54:30 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <199809190154.VAA00452@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG From: "Louis A. Mamakos" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Sep 1998 21:54:30 -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FYI, with the lastest version of sys/pci/ncr.c, my problem is gone, and the systems seems to be running just fine. I'll trying running a 'make world' through it to beat on it. Looks like a strange situation; it seems that undefining #define NCR_GETCC_WITHMSG would have the same effect. Anyway, thanks very much for the fix. louie ------- Forwarded Message To: "Justin T. Gibbs" cc: Ted Buswell , scsi@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: CAM/ncr messages.. Date: Fri, 18 Sep 1998 09:14:09 -0400 I'm still getting hangs during boot with the 1.129 version of ncr.c. It's a succession of ncr0: timeout nccb= It does this for quite a while, never finding and SCSI devices. I have to punch the reset button to restart the system. Here's an excerpt from a non-CAM kernel (that I backed up to) to see the SCSI configuration. Note that all the devices on the SCSI bus a narrow devices. ... de0: address 00:80:c8:0d:15:9f ncr0: rev 0x02 int a irq 15 on pci0.20.0 scbus0 at ncr0 bus 0 sd0 at scbus0 target 1 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: 10.0 MB/s (100 ns, offset 8) 2049MB (4197520 512 byte sectors) sd0: with 3045 cyls, 16 heads, and an average 86 sectors/track st0 at scbus0 target 2 lun 0 st0: type 1 removable SCSI 2 st0: Sequential-Access st0: 5.0 MB/s (200 ns, offset 8) density code 0x24, 512-byte blocks, write-enabled ch0 at scbus0 target 2 lun 1 ch0: type 8 removable SCSI 2 ch0: Medium-Changer 4 slots, 1 drive, 1 picker cd0 at scbus0 target 3 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd0: 4.0 MB/s (250 ns, offset 8) can't get the size worm0 at scbus0 target 5 lun 0 worm0: type 5 removable SCSI 2 worm0: Write-Once sd1 at scbus0 target 6 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access sd1: 10.0 MB/s (100 ns, offset 8) 2047MB (4194058 512 byte sectors) sd1: with 3703 cyls, 9 heads, and an average 125 sectors/track Probing for devices on the ISA bus: .... This isn't too much to go on; is there any other information I can gather on the next boot attempts? And debug knobs to twiddle? I've successfully converted another Adaptec based machine to CAM and ELF; this system is converted to ELF, but still running the old non-CAM kernel. louie ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 19:15:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29161 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 19:15:03 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29139; Fri, 18 Sep 1998 19:15:00 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt2-64.HiWAAY.net [208.147.148.64]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id VAA22627; Fri, 18 Sep 1998 21:14:34 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id UAA04692; Fri, 18 Sep 1998 20:40:52 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199809190140.UAA04692@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Shenton cc: questions@FreeBSD.ORG, scsi@FreeBSD.ORG From: David Kelly Subject: Re: st0: 262144-byte record too big (reading SGI tar tape) In-reply-to: Message from Chris Shenton of "18 Sep 1998 13:58:49 EDT." <87k931fgkm.fsf@absinthe.shenton.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Sep 1998 20:40:51 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chris Shenton writes: > J Wunsch writes: > > > You cannot read SGI tapes (with their default blocksize) on FreeBSD, > > due to limitations in physio(9) (which have been constrained by older > > SCSI controllers that cannot handle more than 16 scatter/gather > > segments). > > Any suggestions for blocksize? The "st" man page suggests a maximum of > 64KB so I was thinking 32K. Should that be OK? If your write the tape on the SGI with a 64k or smaller blocksize then you'll be OK. (tar -cvb 128 file(s)...) You can also modify /var/sysgen/*/scsi, then build a new kernel (autoconfig), and change your SGI's default tape blocksize. (sorry, I forgot what directory the scsi file is in, you can't miss it. I'd love to see FreeBSD break the 64k barrier, at least for controllers that can handle it. Would hope Adaptec 2940's can as SGI uses AIC7880's in the O2 on my desk at work. This topic has come up a time or two in discussion of CAM. In the rewrite for CAM I get the impression the authors decided it was more important to get CAM working than to add features such as large tape blocks. I can't blame them. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 19:17:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29622 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 19:17:01 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29614 for ; Fri, 18 Sep 1998 19:16:59 -0700 (PDT) (envelope-from root@eyelab.psy.msu.edu) Received: from logrus-p2 (dyn1-tnt5-48.detroit.mi.ameritech.net [206.141.209.48]) by eyelab.psy.msu.edu (8.9.1/8.8.7) with SMTP id WAA21875 for ; Fri, 18 Sep 1998 22:16:31 -0400 (EDT) (envelope-from root@eyelab.psy.msu.edu) Message-Id: <199809190216.WAA21875@eyelab.psy.msu.edu> X-Sender: root@eyelab.msu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.52 (Beta) Date: Fri, 18 Sep 1998 22:16:14 -0400 To: freebsd-scsi@FreeBSD.ORG From: Gary Schrock Subject: using a cd-r as a cd-rom drive, and a general cam question Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, I've got two questions here. One is that I've got a machine that I've got an older Pinnacle Micro rcd-1000 cd recorder. This was one of the early 2x recorders, from the time when they only reported themselves as Type 4 devices, unlike most modern ones that report themselves as Type 5 devices which lets them be used as normal cd drives easily. Is there any way to get this drive to work using the cd driver under cam? I don't have any real need to use it as a cd recorder under freebsd, but being able to read from it would be very useful. Running camcontrol devlist shows me: vision# camcontrol devlist at scbus0 target 2 lun 0 (sa0) at scbus0 target 4 lun 0 (cd0) But while booting cd0 is never listed in the boot messages (sa0 is definitely listed there). I also never seem to be able to mount anything on it, getting device not configured errors (yes, I've made the /dev/cd devices). My other question is is there any document describing exactly what things you need to enable in the config file for cam? Obviously I need to enable the driver for my scsi card, the sa driver for the tape drive, and the cd driver for the cd drive, but what about the other ones? Camcontrol seems to require xpt, and there's also a pass device, but what are these and what would you need them for? The lint file doesn't seem to contain any info on them, and there's no man pages for them. Thanks Gary Schrock root@eyelab.msu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 21:41:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15894 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 21:41:17 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15886 for ; Fri, 18 Sep 1998 21:41:15 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id WAA14791; Fri, 18 Sep 1998 22:40:40 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809190440.WAA14791@panzer.plutotech.com> Subject: Re: st0: 262144-byte record too big (reading SGI tar tape) In-Reply-To: <199809190140.UAA04692@nospam.hiwaay.net> from David Kelly at "Sep 18, 98 08:40:51 pm" To: dkelly@hiwaay.net (David Kelly) Date: Fri, 18 Sep 1998 22:40:40 -0600 (MDT) Cc: chris@shenton.org, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 [ dropping -questions from the CC list ] David Kelly wrote... > Chris Shenton writes: > > J Wunsch writes: > > > > > You cannot read SGI tapes (with their default blocksize) on FreeBSD, > > > due to limitations in physio(9) (which have been constrained by older > > > SCSI controllers that cannot handle more than 16 scatter/gather > > > segments). > > > > Any suggestions for blocksize? The "st" man page suggests a maximum of > > 64KB so I was thinking 32K. Should that be OK? > > If your write the tape on the SGI with a 64k or smaller blocksize then > you'll be OK. (tar -cvb 128 file(s)...) > > You can also modify /var/sysgen/*/scsi, then build a new kernel > (autoconfig), and change your SGI's default tape blocksize. (sorry, I > forgot what directory the scsi file is in, you can't miss it. > > I'd love to see FreeBSD break the 64k barrier, at least for controllers > that can handle it. Would hope Adaptec 2940's can as SGI uses AIC7880's > in the O2 on my desk at work. This topic has come up a time or two in > discussion of CAM. In the rewrite for CAM I get the impression the > authors decided it was more important to get CAM working than to add > features such as large tape blocks. I can't blame them. Getting larger blocksizes working involves more than just tweaking the SCSI layer. If the scsi layer were the only bottleneck, it probably would have been implemented under the old SCSI layer long before the CAM work started. To get larger blocksizes we'll need some sort of buffer chaining scheme, scatter gather lists, or something like that. John Dyson talked about doing it at one point, but he's off working on other stuff. CAM can already handle large chunks of data, if you feed the data through in a way that doesn't involve physio. At Pluto, we've got a RAID application that feeds data through the passthrough driver in arbitrarily large chunks using physical memory addresses. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 21:53:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16875 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 21:53:59 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16850 for ; Fri, 18 Sep 1998 21:53:28 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id WAA19548; Fri, 18 Sep 1998 22:52:55 -0600 (MDT) Message-Id: <199809190452.WAA19548@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Louis A. Mamakos" cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG In-reply-to: Your message of "Fri, 18 Sep 1998 21:54:30 EDT." <199809190154.VAA00452@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Sep 1998 22:46:34 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >FYI, with the lastest version of sys/pci/ncr.c, my problem is gone, and >the systems seems to be running just fine. I'll trying running a >'make world' through it to beat on it. > >Looks like a strange situation; it seems that undefining > >#define NCR_GETCC_WITHMSG > >would have the same effect. Probably. My understanding of the NCR script is somewhat limited and I don't know the complete rational behind performing the automatic request sense without an identify message. I hope to leave any further bug fixes to the master of the NCR driver, Stefan. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 18 22:01:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18026 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 22:01:18 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18008 for ; Fri, 18 Sep 1998 22:01:13 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id WAA14878; Fri, 18 Sep 1998 22:59:52 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809190459.WAA14878@panzer.plutotech.com> Subject: Re: using a cd-r as a cd-rom drive, and a general cam question In-Reply-To: <199809190216.WAA21875@eyelab.psy.msu.edu> from Gary Schrock at "Sep 18, 98 10:16:14 pm" To: root@eyelab.psy.msu.edu (Gary Schrock) Date: Fri, 18 Sep 1998 22:59:52 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM906181192-14769-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM906181192-14769-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Gary Schrock wrote... > Ok, I've got two questions here. One is that I've got a machine that I've > got an older Pinnacle Micro rcd-1000 cd recorder. This was one of the > early 2x recorders, from the time when they only reported themselves as > Type 4 devices, unlike most modern ones that report themselves as Type 5 > devices which lets them be used as normal cd drives easily. Is there any > way to get this drive to work using the cd driver under cam? I don't have > any real need to use it as a cd recorder under freebsd, but being able to > read from it would be very useful. Running camcontrol devlist shows me: > vision# camcontrol devlist > at scbus0 target 2 lun 0 (sa0) > at scbus0 target 4 lun 0 (cd0) > But while booting cd0 is never listed in the boot messages (sa0 is > definitely listed there). I also never seem to be able to mount anything > on it, getting device not configured errors (yes, I've made the /dev/cd > devices). Well, it looks like there are several things going on here: - The CAM CD driver attempts to attach to any CD or WORM devices it finds. If the worm device it finds returns errors on probe, the CD driver won't attach to it. It won't print any errors for worm devices, since many of them don't respond properly to CDROM commands. Your drive most likely falls into that category, although there's one way to find out for sure. Apply the attached patch to src/sys/cam/scsi/scsi_cd.c, and send me the output when you boot. - The CD driver isn't getting properly de-registered when it fails to attach to your device. I need to look into that one. - You don't have the passthrough device configured in your kernel. > My other question is is there any document describing exactly what things > you need to enable in the config file for cam? Obviously I need to enable > the driver for my scsi card, the sa driver for the tape drive, and the cd > driver for the cd drive, but what about the other ones? Camcontrol seems > to require xpt, and there's also a pass device, but what are these and what > would you need them for? The lint file doesn't seem to contain any info on > them, and there's no man pages for them. The only documentation is LINT, GENERIC and the camcontrol man page. You've obviously discovered one area where CAM is quite incomplete. Fixing that problem is on my list (and Justin's list) of things to do, but it necessarily comes after fixing code bugs. If things calm down enough between now and the 3.0 release, we'll probably be able to get some of the more important man pages done at least. Here are the list of CAM peripheral drivers you can configure in your kernel: device da0 -- direct access and optical disk driver device cd0 -- CDROM driver (also attaches to WORM drives) device sa0 -- tape driver device ch0 -- changer driver device pt0 -- processor target driver device pass0 -- application passthrough driver device targ0 -- target mode processor target driver (It's probably best to leave this alone for now.) The xpt device is the CAM transport layer device. It allows sending bus and lun rescan commands, device matching commands, and other commands that generally don't make sense to send to an individual passthrough device. The pass device lets you send SCSI CCBs and other CCBs (CAM Control Blocks) to a given device. The passthrough device is used by camcontrol to send SCSI commands. It is also used by tosha, cdrecord, xmcd, SANE, etc. Ken -- Kenneth Merry ken@plutotech.com --ELM906181192-14769-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=scsi_cd.wormerr.diffs Content-Description: scsi_cd.wormerr.diffs Content-Transfer-Encoding: 7bit ==== //depot/cam/sys/cam/scsi/scsi_cd.c#82 - /usr/home/ken/perforce/cam/sys/cam/scsi/scsi_cd.c ==== *** /tmp/tmp.23298.0 Fri Sep 18 22:58:36 1998 --- /usr/home/ken/perforce/cam/sys/cam/scsi/scsi_cd.c Fri Sep 18 22:57:33 1998 *************** *** 1719,1725 **** scsi_sense_key_text[sense_key], scsi_sense_desc(asc,ascq, &cgd.inq_data)); ! else if (cgd.pd_type == T_CDROM) { /* * We only print out an error for * CDROM type devices. For WORM --- 1719,1725 ---- scsi_sense_key_text[sense_key], scsi_sense_desc(asc,ascq, &cgd.inq_data)); ! else { /* * We only print out an error for * CDROM type devices. For WORM *************** *** 1756,1769 **** announce_buf); scsi_sense_print(&done_ccb->csio); - /* - * Free up resources. - */ - cam_extend_release(cdperiphs, - periph->unit_number); - cam_periph_invalidate(periph); - periph = NULL; - } else { /* * Free up resources. */ --- 1756,1761 ---- --ELM906181192-14769-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 19 01:11:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09604 for freebsd-scsi-outgoing; Sat, 19 Sep 1998 01:11:46 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09583 for ; Sat, 19 Sep 1998 01:11:39 -0700 (PDT) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t4o29p73.telia.com [194.236.215.193]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id KAA00240; Sat, 19 Sep 1998 10:11:13 +0200 Received: from pegasys (pegasys.granlund.nu [192.168.0.2]) by phoenix.granlund.nu (8.9.1/8.9.1) with SMTP id JAA22754; Sat, 19 Sep 1998 09:41:55 +0200 (CEST) (envelope-from johan@phoenix.granlund.nu) Message-Id: <199809190741.JAA22754@phoenix.granlund.nu> From: "Johan Granlund" To: "Justin T. Gibbs" Date: Sat, 19 Sep 1998 09:37:53 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: CAM and exabyte EXB-8200 problems CC: scsi@FreeBSD.ORG In-reply-to: <199809181922.NAA15474@narnia.plutotech.com> References: <199809181605.SAA00314@phoenix.granlund.nu> X-mailer: Pegasus Mail for Win32 (v3.01a) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In article <199809181605.SAA00314@phoenix.granlund.nu> you wrote: > > Hi > > > > I got a small problem (TM) after uppgrading to CAM, my tapestation is > > hanging on boot. This is an old Exabyte 8200. When looking at a boot -v > > it hangs when all devices EXCEPT the tapestation has been found. This is > > a fullblown SCSI hang with the busylamp on > > > > The exabyte is doing a lengthy recalibration on a SCSI reset. When > > looking on the output from a preCAM boot i got a couple of busy > > timeouts. SCSI_DELAY=30000 (30sec) > > > > Is appendig two boot -v outputs one precam (beetwen E-Day and C-Day) and > > one without the tape from today at 17:00 CEDT > > > > Any solutions? > > I need a bit more information. This is likely a bug in the handling of > the BUSY status code. A boot with -v with the tape drive hooked up (I > know it will hang...) would help a lot. I could try to set up a serial console, but i dont think it will add anything new. This is from the boot without the tape. If you shut your eyes when reading about target 6 (where the tape is normally) its the same as with the tape:) Sep 18 17:41:05 phoenix /kernel: (noperiph:ahc0:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. Sep 18 17:41:05 phoenix /kernel: ahc0: Selection Timeout on A:2. 1 SCBs aborted Sep 18 17:41:05 phoenix /kernel: ahc0: Selection Timeout on A:3. 1 SCBs aborted Sep 18 17:41:05 phoenix /kernel: ahc0: Selection Timeout on A:4. 1 SCBs aborted Sep 18 17:41:06 phoenix /kernel: ahc0: Selection Timeout on A:5. 1 SCBs aborted Sep 18 17:41:06 phoenix /kernel: ahc0: Selection Timeout on A:6. 1 SCBs aborted Sep 18 17:41:06 phoenix /kernel: ahc0: Selection Timeout on A:9. 1 SCBs aborted Sep 18 17:41:06 phoenix /kernel: ahc0: Selection Timeout on A:10. 1 SCBs aborted Sep 18 17:41:06 phoenix /kernel: ahc0: Selection Timeout on A:11. 1 SCBs aborted Sep 18 17:41:06 phoenix /kernel: ahc0: Selection Timeout on A:12. 1 SCBs aborted Sep 18 17:41:06 phoenix /kernel: ahc0: Selection Timeout on A:13. 1 SCBs aborted Sep 18 17:41:06 phoenix /kernel: ahc0: Selection Timeout on A:14. 1 SCBs aborted Sep 18 17:41:06 phoenix /kernel: ahc0: Selection Timeout on A:15. 1 SCBs aborted Sep 18 17:41:06 phoenix /kernel: ahc0: target 1 synchronous at 10.0M Sep 18 17:41:06 phoenix /kernel: Hz, offset = 0xf Sep 18 17:41:06 phoenix /kernel: ahc0: target 8 using 16bit transfers Sep 18 17:41:06 phoenix /kernel: ahc0: target 8 synchronous at 20.0MHz, offset = 0x8 Sep 18 17:41:06 phoenix /kernel: ahc0: target 0 synchronous at 10.0MHz, offset = 0xf Here its only stops after finding my three disks. No errormessages, timeout or anything. I can still reboot from the keyboard. /Johan > > > /Johan > > -- > Justin > ___________________________________________________________ Internet: johan@granlund.nu I don't even speak for myself To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 19 01:45:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12969 for freebsd-scsi-outgoing; Sat, 19 Sep 1998 01:45:56 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA12962 for ; Sat, 19 Sep 1998 01:45:53 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA14435 (5.67b/IDA-1.5); Sat, 19 Sep 1998 10:43:49 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id KAA11817; Sat, 19 Sep 1998 10:25:50 +0200 (CEST) From: Wilko Bulte Message-Id: <199809190825.KAA11817@yedi.iaf.nl> Subject: Re: CAM and exabyte EXB-8200 problems In-Reply-To: <199809181922.NAA15474@narnia.plutotech.com> from "Justin T. Gibbs" at "Sep 18, 98 01:22:49 pm" To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Sat, 19 Sep 1998 10:25:50 +0200 (CEST) Cc: johan@granlund.nu, scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Justin T. Gibbs wrote... > In article <199809181605.SAA00314@phoenix.granlund.nu> you wrote: > > Hi > > > > I got a small problem (TM) after uppgrading to CAM, my tapestation is > > hanging on boot. This is an old Exabyte 8200. When looking at a boot -v > > it hangs when all devices EXCEPT the tapestation has been found. This is > > a fullblown SCSI hang with the busylamp on > > > > The exabyte is doing a lengthy recalibration on a SCSI reset. When looking > > on the output from a preCAM boot i got a couple of busy timeouts. > > SCSI_DELAY=30000 (30sec) > > > > Is appendig two boot -v outputs one precam (beetwen E-Day and C-Day) and > > one without the tape from today at 17:00 CEDT > > > > Any solutions? > > I need a bit more information. This is likely a bug in the handling of > the BUSY status code. A boot with -v with the tape drive hooked up > (I know it will hang...) would help a lot. Keep in mind that there are a zillion revisions of the 8200 firmware. Something that worked with driver X could well fail with driver Y. So, it could be CAM but don't rule out the 8200 Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 19 05:46:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01944 for freebsd-scsi-outgoing; Sat, 19 Sep 1998 05:46:57 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from asterix.webaffairs.net (port201.bonn.ndh.net [195.94.93.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01936 for ; Sat, 19 Sep 1998 05:46:51 -0700 (PDT) (envelope-from stefhe@gmx.net) Received: from obelix (obelix.webaffairs.net [192.168.10.3]) by asterix.webaffairs.net (8.8.8/8.8.8) with SMTP id OAA26672 for ; Sat, 19 Sep 1998 14:21:43 +0200 (CEST) (envelope-from stefhe@gmx.net) From: "Stefan Herrmann" To: Subject: SCSI Disk runterfahren Date: Sat, 19 Sep 1998 14:16:52 +0200 Message-ID: <000401bde3c7$62a54fc0$030aa8c0@obelix.webaffairs.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'd like to spin down a fast but noicy scsi disk, which is built into my pc. When I need it, it should spin up automatically. Is that possible (I think yes ;-) and what is the scsi command (under FreeBSD-2.2.7) ? A hint to an URL would help me already. Ciao Stefan -- --- Communications powered by FreeBSD --- Stefan Herrmann Löwenburgstr. 81 D-53229 Bonn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 19 19:44:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12311 for freebsd-scsi-outgoing; Sat, 19 Sep 1998 19:44:22 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA12299 for ; Sat, 19 Sep 1998 19:44:18 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 21738 invoked by uid 1000); 20 Sep 1998 03:47:21 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 19 Sep 1998 23:47:21 -0400 (EDT) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-scsi@FreeBSD.ORG Subject: Last known DPT Kerenel Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The last working FreeBSD release I am aware of which will install and run from a DPT controller is the snapshot of 26-Aug-98. As I posted earlier, the CAM version panics during boot and is a totally new and unknown entity in these quarters. Work will commence on said new version in the next few days, emergencies non withstanding... BTW, if there is need/interest in said snapshot, let me know, I'll make it available, if not so already. Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 19 21:52:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22974 for freebsd-scsi-outgoing; Sat, 19 Sep 1998 21:52:59 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22958 for ; Sat, 19 Sep 1998 21:52:47 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id WAA06713; Sat, 19 Sep 1998 22:45:55 -0600 (MDT) Date: Sat, 19 Sep 1998 22:45:55 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809200445.WAA06713@narnia.plutotech.com> To: shimon@simon-shapiro.org cc: scsi@FreeBSD.ORG Subject: Re: Last known DPT Kerenel Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > As I posted earlier, the CAM version panics during boot and is a totally > new and unknown entity in these quarters. Work will commence on said new > version in the next few days, emergencies non withstanding... I must have missed this post. Can you elaborate or tell me which list archive to search? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message