From owner-freebsd-scsi Sun Feb 2 02:06:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA11201 for freebsd-scsi-outgoing; Sun, 2 Feb 1997 02:06:37 -0800 (PST) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA11196 for ; Sun, 2 Feb 1997 02:06:30 -0800 (PST) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id CAA22187; Sun, 2 Feb 1997 02:06:23 -0800 (PST) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id CAA22267; Sun, 2 Feb 1997 02:06:22 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.4/8.8.4) id CAA00193; Sun, 2 Feb 1997 02:06:21 -0800 (PST) From: Don Lewis Message-Id: <199702021006.CAA00193@salsa.gv.tsc.tdk.com> Date: Sun, 2 Feb 1997 02:06:21 -0800 In-Reply-To: j@uriah.heep.sax.de (J Wunsch) "Re: SCSI disk MEDIUM ERROR with a few twists" (Feb 1, 8:31pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Subject: Re: SCSI disk MEDIUM ERROR with a few twists Cc: Don.Lewis@tsc.tdk.com (Don Lewis) Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Feb 1, 8:31pm, J Wunsch wrote: } Subject: Re: SCSI disk MEDIUM ERROR with a few twists } As Peter Dufault wrote: } } > I also put together a defect list dumper for Satoshi when he was } > having some problems, so I'm putting that here too. } } Neat! } } I've combined both, since this is really easier to handle in Perl. Thanks for posting this! I just discovered that my disk has grown 10 defects in a couple months of operation. I guess I'd better replace it. Neither of the other disks on this machine has any grown defects. --- Truck From owner-freebsd-scsi Sun Feb 2 02:50:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA13307 for freebsd-scsi-outgoing; Sun, 2 Feb 1997 02:50:42 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA13289 for ; Sun, 2 Feb 1997 02:50:37 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA13634 for freebsd-scsi@FreeBSD.org; Sun, 2 Feb 1997 11:50:35 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id LAA25938; Sun, 2 Feb 1997 11:28:52 +0100 (MET) Message-ID: Date: Sun, 2 Feb 1997 11:28:52 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Subject: Re: SCSI disk MEDIUM ERROR with a few twists References: <199702021006.CAA00193@salsa.gv.tsc.tdk.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702021006.CAA00193@salsa.gv.tsc.tdk.com>; from Don Lewis on Feb 2, 1997 02:06:21 -0800 Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Don Lewis wrote: > } Neat! > } > } I've combined both, since this is really easier to handle in Perl. > > Thanks for posting this! Peter, do you mind me putting a BSD-style copyright on top of that script, mentioning our names, and stuffing it into the tools/ directory in CVS? What's the most useful name? scsi-defects? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sun Feb 2 03:51:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA15045 for freebsd-scsi-outgoing; Sun, 2 Feb 1997 03:51:29 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA15040 for ; Sun, 2 Feb 1997 03:51:25 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id MAA11518; Sun, 2 Feb 1997 12:46:09 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.5/8.8.2) id MAA04309; Sun, 2 Feb 1997 12:01:44 +0100 (MET) Message-ID: <19970202120143.SE25899@klemm.gtn.com> Date: Sun, 2 Feb 1997 12:01:43 +0100 From: andreas@klemm.gtn.com (Andreas Klemm) To: henrich@crh.cl.msu.edu (Charles Henrich) Cc: j@uriah.heep.sax.de, freebsd-scsi@freebsd.org Subject: Re: SCSI disk MEDIUM ERROR with a few twists References: <5d07hr$l9m@msunews.cl.msu.edu> <199702012326.SAA11001@crh.cl.msu.edu> X-Mailer: Mutt 0.59-PL19 Mime-Version: 1.0 In-Reply-To: <199702012326.SAA11001@crh.cl.msu.edu>; from "Charles Henrich" on Feb 1, 1997 18:26:03 -0500 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Charles Henrich writes: > In lists.freebsd.scsi you write: > > >As Peter Dufault wrote: > > >> I also put together a defect list dumper for Satoshi when he was > >> having some problems, so I'm putting that here too. > > >Neat! > > >I've combined both, since this is really easier to handle in Perl. > > >Maybe we should put this up under tools/? > > This stuff is coolness! Yes indeed. With that I detected, that one of my 3 IBM DORS has over 700 errors more in the Plist than the other two drives. And there are already erors in the Glist ... > Might I suggest strongly that on sysstems where we > have devices with sd0() online that we run this daily and diff the results as > we do with master.passwd ? This gives system administrators early warnings on > failing disks if they start to see the glist grow and grow day after day.. Is a fine idea ! -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-scsi Sun Feb 2 12:39:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA10560 for freebsd-scsi-outgoing; Sun, 2 Feb 1997 12:39:45 -0800 (PST) Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA10552 for ; Sun, 2 Feb 1997 12:39:41 -0800 (PST) Received: from dragon.nuxi.com (reqd-042.ucdavis.edu [128.120.251.162]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id MAA06136; Sun, 2 Feb 1997 12:39:44 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id MAA17678; Sun, 2 Feb 1997 12:39:46 -0800 (PST) Message-ID: <19970202123946.KS47681@dragon.nuxi.com> Date: Sun, 2 Feb 1997 12:39:46 -0800 From: obrien@NUXI.com (David O'Brien) To: andreas@klemm.gtn.com (Andreas Klemm) Cc: j@uriah.heep.sax.de, freebsd-scsi@freebsd.org Subject: Re: SCSI disk MEDIUM ERROR with a few twists References: <5d07hr$l9m@msunews.cl.msu.edu> <199702012326.SAA11001@crh.cl.msu.edu> <19970202120143.SE25899@klemm.gtn.com> X-Mailer: Mutt 0.59-PL19 Mime-Version: 1.0 Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 In-Reply-To: <19970202120143.SE25899@klemm.gtn.com>; from Andreas Klemm on Feb 2, 1997 12:01:43 +0100 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Andreas Klemm writes: > > >Maybe we should put this up under tools/? > > > > This stuff is coolness! > > > Might I suggest strongly that on sysstems where we have devices with > > sd0() online that we run this daily and diff the results as we do > > with master.passwd ? This gives system administrators early warnings > > on failing disks if they start to see the glist grow and grow day > > after day.. If we are to do this, then should it be commited to /usr/sbin (or /sbin) rather than tools? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) From owner-freebsd-scsi Sun Feb 2 12:45:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA11263 for freebsd-scsi-outgoing; Sun, 2 Feb 1997 12:45:43 -0800 (PST) Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA11245 for ; Sun, 2 Feb 1997 12:45:37 -0800 (PST) Received: from dragon.nuxi.com (reqd-042.ucdavis.edu [128.120.251.162]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id MAA06147; Sun, 2 Feb 1997 12:45:44 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id MAA17721; Sun, 2 Feb 1997 12:45:47 -0800 (PST) Message-ID: <19970202124546.AS07107@dragon.nuxi.com> Date: Sun, 2 Feb 1997 12:45:46 -0800 From: obrien@NUXI.com (David O'Brien) To: j@uriah.heep.sax.de Cc: freebsd-scsi@freebsd.org Subject: Re: SCSI disk MEDIUM ERROR with a few twists References: <5d07hr$l9m@msunews.cl.msu.edu> <199702012326.SAA11001@crh.cl.msu.edu> X-Mailer: Mutt 0.59-PL19 Mime-Version: 1.0 Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 In-Reply-To: <199702012326.SAA11001@crh.cl.msu.edu>; from Charles Henrich on Feb 1, 1997 18:26:03 -0500 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Maybe we should put this up under tools/? I've got two ufs tools I got from some list (probably this one) that Giles Lean posted. I was making a port of this. Would it better to commit them to tools/ ? (what type of things are approapiate for tools/ ? Do they get installed in /usr/sbin or anywhere by default?) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) From owner-freebsd-scsi Sun Feb 2 13:09:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA13958 for freebsd-scsi-outgoing; Sun, 2 Feb 1997 13:09:17 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA13946 for ; Sun, 2 Feb 1997 13:09:09 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA02787; Sun, 2 Feb 1997 22:08:58 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id WAA11452; Sun, 2 Feb 1997 22:05:56 +0100 (MET) Message-ID: Date: Sun, 2 Feb 1997 22:05:56 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: obrien@NUXI.com (David O'Brien) Cc: freebsd-scsi@freebsd.org Subject: Re: SCSI disk MEDIUM ERROR with a few twists References: <5d07hr$l9m@msunews.cl.msu.edu> <199702012326.SAA11001@crh.cl.msu.edu> <19970202124546.AS07107@dragon.nuxi.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970202124546.AS07107@dragon.nuxi.com>; from David O'Brien on Feb 2, 1997 12:45:46 -0800 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As David O'Brien wrote: > I was making a port of this. Would it better to commit them to tools/ ? > (what type of things are approapiate for tools/ ? Do they get > installed in /usr/sbin or anywhere by default?) tools/ are only intended for the developers. You're right, scsi-defects is inappropriate there. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Mon Feb 3 02:10:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA19836 for freebsd-scsi-outgoing; Mon, 3 Feb 1997 02:10:21 -0800 (PST) Received: from perki0.connect.com.au (perki0.connect.com.au [192.189.54.85]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19811 for ; Mon, 3 Feb 1997 02:10:09 -0800 (PST) Received: from nemeton.UUCP (Unemeton@localhost) by perki0.connect.com.au with UUCP id VAA27289 (8.7.6h/IDA-1.6); Mon, 3 Feb 1997 21:09:38 +1100 (EST) X-Authentication-Warning: perki0.connect.com.au: Unemeton set sender to giles@nemeton.com.au using -f Received: from localhost.nemeton.com.au (localhost.nemeton.com.au [127.0.0.1]) by nemeton.com.au (8.8.5/8.8.5) with SMTP id TAA09732; Mon, 3 Feb 1997 19:17:49 +1100 (EST) Message-Id: <199702030817.TAA09732@nemeton.com.au> To: obrien@nuxi.com (David O'Brien) cc: freebsd-scsi@freebsd.org Subject: Re: SCSI disk MEDIUM ERROR with a few twists In-reply-to: <19970202124546.AS07107@dragon.nuxi.com> Date: Mon, 03 Feb 1997 19:17:49 +1100 From: Giles Lean Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 2 Feb 1997 12:45:46 -0800 David O'Brien wrote: > I've got two ufs tools I got from some list (probably this one) that > Giles Lean posted. Hmm. I'm not sure these are generally useful enough to warrant any more effort than leaving them in the mail archive. Further, I just checked the 'icat' program -- which is by Tom Christiansen and found it doesn't have an explicit copyright in it. I think Tom should be contacted before it gets added to any source trees. (As an aside, Tom has had lots of his perl writings ripped off and used commercially in books without his consent, so copyright is a sensitive topic with him right now!) Leaving the code in the mailing list archives is presumably harmless, since it can already be found in deja news. A pity I didn't see that it didn't have Tom's name in it when I posted it. Regards, Giles From owner-freebsd-scsi Mon Feb 3 02:53:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA22683 for freebsd-scsi-outgoing; Mon, 3 Feb 1997 02:53:08 -0800 (PST) Received: from mail.futuresouth.com (mail.futuresouth.com [207.141.254.21]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA22652; Mon, 3 Feb 1997 02:52:58 -0800 (PST) Received: from shell.futuresouth.com (shell.futuresouth.com [207.141.254.20]) by mail.futuresouth.com (8.8.5/8.8.5) with ESMTP id EAA02811; Mon, 3 Feb 1997 04:52:22 -0600 (CST) From: Tim Tsai Received: (from tim@localhost) by shell.futuresouth.com (8.8.3/8.8.3) id EAA29026; Mon, 3 Feb 1997 04:52:22 -0600 (CST) Message-Id: <199702031052.EAA29026@shell.futuresouth.com> Subject: Re: tape changer To: thorpej@nas.nasa.gov Date: Mon, 3 Feb 1997 04:52:21 -0600 (CST) Cc: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org In-Reply-To: <199701222308.PAA19327@lestat.nas.nasa.gov> from Jason Thorpe at "Jan 22, 97 03:08:36 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello. I finally got around to installing the chio driver that you had mentioned to me about on 2.1.6.1. After replacing the appropriate files (the only unexpected thing was to copy chio.h to /usr/include/sys) I was able to load/eject tapes on my 4mm DAT changer (Archive Python 24889) correctly. I haven't had time to fool with Amanda to use chio yet but I think everything is easy from here. Thanks for all your help! One question: I am not familiar with the terminology used in the man pages (picker, slot, portal, drive). I can load/eject the tape by moving between slot/drive. Can you tell me what are the purposes of picker/portal? PS: I am sending a copy of this to FreeBSD mailing lists because I've seen the same question asked in the archives but no definitive answers. Thanks again, Tim > You can find the driver I submitted to FreeBSD at: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=1201 > > Hope that helps. > > Jason R. Thorpe thorpej@nas.nasa.gov > NASA Ames Research Center Home: 408.866.1912 > NAS: M/S 258-6 Work: 415.604.0935 > Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-scsi Mon Feb 3 05:33:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA28384 for freebsd-scsi-outgoing; Mon, 3 Feb 1997 05:33:15 -0800 (PST) Received: from deacon.cogsci.ed.ac.uk (deacon.cogsci.ed.ac.uk [129.215.144.7]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA28379 for ; Mon, 3 Feb 1997 05:33:12 -0800 (PST) Received: (from richard@localhost) by deacon.cogsci.ed.ac.uk (8.6.10/8.6.12) id NAA14558; Mon, 3 Feb 1997 13:32:17 GMT Date: Mon, 3 Feb 1997 13:32:17 GMT Message-Id: <199702031332.NAA14558@deacon.cogsci.ed.ac.uk> From: Richard Tobin Subject: Re: Tape Backup Drive Not working. To: Chris Coleman , Richard Tobin In-Reply-To: Chris Coleman's message of Sat, 1 Feb 1997 16:00:21 -0800 (PST) Organization: just say no Cc: Joerg Wunsch , FreeBSD SCSI list Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Looks like Conner's version of the HP T4000s [...] > > Essentially all that was required was setting the PF bit in mode > > select, > It's still not working. I tried the patch that was sent to me, but it > didn't seem to make a diffrence. I am still getting the same errors. I > think is might have somthing to do with this actually being a HP Travin? The HP drive I mentioned is indeed a Travan (TR-4) drive, and so I think is your Conner, but I would be surprised if Conner were selling actual HP drives! I don't have the sources to hand, but I believe the only other error message was caused by the driver trying to lock the tape in drive, which isn't supported by the T4000s. This shouldn't have been reported as an error anyway, and is probably fixed now. Does anything work (even if gives errors)? "mt rew" for example? -- Richard From owner-freebsd-scsi Mon Feb 3 11:12:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA14312 for freebsd-scsi-outgoing; Mon, 3 Feb 1997 11:12:35 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA14297; Mon, 3 Feb 1997 11:12:22 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id MAA01626; Mon, 3 Feb 1997 12:07:37 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199702010403.XAA02913@dyson.iquest.net> Date: Mon, 03 Feb 1997 11:35:38 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: "John S. Dyson" Subject: Re: XXXminpys question Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-scsi@freebsd.org, dyson@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi John S. Dyson; On 01-Jan-97 you wrote: > > > > > > Hi John S. Dyson; On 31-Jan-97 you wrote: > > > It will require some restructuring of the pbuf (physical I/O buffer) > > > code, but isn't that bad to do. It has been in my queue for a while. > > > If the driver-savvy people can work out a way to query the driver for > > > the maximum I/O size, I can/will implement the upper level changes. > > > > > > John Dyson > > > > Is this not the purpose of the xxx_minphys entry point to the driver? > > > > Simon > > > Yes, except is that indeed the *right* way to do it? I am suggesting > that we review that choice first. Coming to think about it, this really describes max_transfer, not min_phys. No? Simon From owner-freebsd-scsi Mon Feb 3 22:56:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA22746 for freebsd-scsi-outgoing; Mon, 3 Feb 1997 22:56:43 -0800 (PST) Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA22738 for ; Mon, 3 Feb 1997 22:56:40 -0800 (PST) Received: from dragon.nuxi.com (reqa-002.ucdavis.edu [128.120.251.2]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id WAA12087; Mon, 3 Feb 1997 22:56:56 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id WAA01037; Mon, 3 Feb 1997 22:56:32 -0800 (PST) Message-ID: <19970203225631.OJ21931@dragon.nuxi.com> Date: Mon, 3 Feb 1997 22:56:31 -0800 From: obrien@NUXI.com (David O'Brien) To: giles@nemeton.com.au (Giles Lean) Cc: obrien@NUXI.com (David O'Brien), freebsd-scsi@freebsd.org Subject: Re: SCSI disk MEDIUM ERROR with a few twists References: <19970202124546.AS07107@dragon.nuxi.com> <199702030817.TAA09732@nemeton.com.au> X-Mailer: Mutt 0.59-PL19 Mime-Version: 1.0 Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 In-Reply-To: <199702030817.TAA09732@nemeton.com.au>; from Giles Lean on Feb 3, 1997 19:17:49 +1100 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Giles Lean writes: > > I've got two ufs tools I got from some list (probably this one) that > > Giles Lean posted. > > (As an aside, Tom has had lots of his perl writings ripped off and > used commercially in books without his consent, so copyright is a > sensitive topic with him right now!) That is quite sad... > Leaving the code in the mailing list archives is presumably harmless, > since it can already be found in deja news. A pity I didn't see that > it didn't have Tom's name in it when I posted it. I've got a URL for a posting he made of it in some newsgroup. So the port was using that as the "dist" file, and then adding your patches. So that probably qualifies to giving him credit. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) From owner-freebsd-scsi Mon Feb 3 22:58:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA22841 for freebsd-scsi-outgoing; Mon, 3 Feb 1997 22:58:59 -0800 (PST) Received: from freebee.tu-graz.ac.at (root@freebee.tu-graz.ac.at [129.27.193.128]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA22818; Mon, 3 Feb 1997 22:58:13 -0800 (PST) Received: from dwarf.tu-graz.ac.at (dialup1.tu-graz.ac.at [129.27.250.2]) by freebee.tu-graz.ac.at (8.6.11/8.6.9) with ESMTP id HAA03099; Tue, 4 Feb 1997 07:57:25 +0100 Received: (from rmike@localhost) by dwarf.tu-graz.ac.at (8.7.5/8.7.3) id HAA00190; Tue, 4 Feb 1997 07:56:06 +0100 (MET) Date: Tue, 4 Feb 1997 07:56:06 +0100 (MET) From: Michael Ranner Reply-To: rmike@sbox.tu-graz.ac.at To: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Subject: AHA2920 / Future Domain TMC 1830 driver for FreeBSD Message-ID: Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Because I have got no answers for my last mail - once again: Is there any interest in an AHA2920 driver for freebsd? Is somebody working on a driver for this card (except me)? Who can give me some technical support to get the code running? /\/\ichael Ranner - rmike@sbox.tu-graz.ac.at _o_ http://www.sbox.tu-graz.ac.at/home/rmike/ / \ ___|o o o|___ AdamsCII / \ /--(_)-(_)-(_)--\ From owner-freebsd-scsi Mon Feb 3 23:05:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA23181 for freebsd-scsi-outgoing; Mon, 3 Feb 1997 23:05:37 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA23172 for ; Mon, 3 Feb 1997 23:05:30 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.4/8.6.12) with SMTP id XAA14722 for ; Mon, 3 Feb 1997 23:05:29 -0800 (PST) Date: Mon, 3 Feb 1997 23:05:28 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: freebsd-scsi@freebsd.org Subject: Re: Device Drivers (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This may be interesting to you guys. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major ---------- Forwarded message ---------- Date: Fri, 31 Jan 1997 23:05:47 -0800 From: "Reginald S. Perry" To: Snob Art Genre Cc: "Jay S. Barlis" , freebsd-questions@FreeBSD.ORG Subject: Re: Device Drivers > > Apparently Buslogic hasn't been forthcoming with the necessary > information for someone to write a device driver. But they're offering > fairly inexpensive ($60-$70) "Linux upgrades" (hmph) to the BT-948 or > BT-958, depending which Flashpoint model you have. I think the quick > route to that is to contact . This is rather curious. I went to http://www.dandelion.com/Linux/ and saw this: Linux BusLogic Driver -- FlashPoint Support Now Available Mylex/BusLogic recently issued a press release announcing support for the FlashPoint SCSI Host Adapters on Linux. BusLogic has provided me with the FlashPoint Driver Developer's Kit, which comprises documentation and freely redistributable source code for the FlashPoint SCCB Manager. The SCCB Manager is the library of code that runs on the host CPU and performs functions analogous to the firmware on the MultiMaster host adapters. Thanks to BusLogic's release of the SCCB Manager, the Linux BusLogic driver now supports the FlashPoint Host Adapters as well. ---- You can download the source for the Linux driver from this site. So someone is getting info from Buslogic. I am concerned about this because I have a Buslogic card in my 486 and I planning to upgrade my setup this summer. Now I wasnt planning to get a FlashPoint card, but I could take the above statments as meaning that the FreeBSD group does not have a very good relationship with Buslogic. Of course I am not taking it that way. What I am thinking is that the Adaptec drivers might be better supported on FreeBSD than the Buslogic drivers. BTW, this _will not_ make me buy an Adaptec board when I upgrade my system. :-) -Reggie ----------------------------------------------------------------- Reginald S. Perry reggie@aa.net From owner-freebsd-scsi Mon Feb 3 23:27:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA24347 for freebsd-scsi-outgoing; Mon, 3 Feb 1997 23:27:51 -0800 (PST) Received: from hydrogen.nike.efn.org (metriclient-11.uoregon.edu [128.223.172.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA24341 for ; Mon, 3 Feb 1997 23:27:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hydrogen.nike.efn.org (8.8.4/8.8.4) with SMTP id XAA22650; Mon, 3 Feb 1997 23:26:51 -0800 (PST) Date: Mon, 3 Feb 1997 23:26:49 -0800 (PST) From: John-Mark Gurney Reply-To: John-Mark Gurney To: Michael Ranner cc: freebsd-scsi@freebsd.org Subject: Re: AHA2920 / Future Domain TMC 1830 driver for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 4 Feb 1997, Michael Ranner wrote: > > Because I have got no answers for my last mail - once again: > > Is there any interest in an AHA2920 driver for freebsd? actually... I am... I have a TMC-1610MER that has the Future Domain 18C30 chip on it... > Is somebody working on a driver for this card (except me)? I'm not... > Who can give me some technical support to get the code running? well... I haven't really done much with the kernel... but as soon as I get a development machine up and running (should be soon now)... I can help... ttyl... John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix) From owner-freebsd-scsi Mon Feb 3 23:41:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA25294 for freebsd-scsi-outgoing; Mon, 3 Feb 1997 23:41:34 -0800 (PST) Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA25279; Mon, 3 Feb 1997 23:41:30 -0800 (PST) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id QAA05519; Tue, 4 Feb 1997 16:35:15 +0900 Date: Tue, 4 Feb 1997 16:35:15 +0900 Message-Id: <199702040735.QAA05519@frig.mt.cs.keio.ac.jp> To: rmike@sbox.tu-graz.ac.at Cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org, hosokawa@mt.cs.keio.ac.jp Subject: Re: AHA2920 / Future Domain TMC 1830 driver for FreeBSD In-Reply-To: Your message of Tue, 4 Feb 1997 07:56:06 +0100 (MET). From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article rmike@sbox.tu-graz.ac.at writes: >> Because I have got no answers for my last mail - once again: >> Is there any interest in an AHA2920 driver for freebsd? >> Is somebody working on a driver for this card (except me)? >> Who can give me some technical support to get the code running? Do you mean AHA2920 uses Future Domain TMC1830 chipset? TMC18C30 driver for PC-card SCSI can be found in newest PAO package ported from NetBSD/pc98 (based on NetBSD 1.2). Possibly it can be used for ISA cards. See "http://www.jp.FreeBSD.org/PAO/". -- HOSOKAWA, Tatsumi E-mail: hosokawa@mt.cs.keio.ac.jp WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html Department of Computer Science, Keio University, Yokohama, Japan From owner-freebsd-scsi Tue Feb 4 03:33:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA11224 for freebsd-scsi-outgoing; Tue, 4 Feb 1997 03:33:15 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA11215; Tue, 4 Feb 1997 03:33:04 -0800 (PST) Received: by sovcom.kiae.su id AA16535 (5.65.kiae-1 ); Tue, 4 Feb 1997 14:01:39 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Tue, 4 Feb 97 14:01:38 +0300 Received: (from ache@localhost) by nagual.ru (8.8.5/8.8.5) id OAA02105; Tue, 4 Feb 1997 14:00:47 +0300 (MSK) Date: Tue, 4 Feb 1997 14:00:44 +0300 (MSK) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: wpaul@freebsd.org, FreeBSD-current , FreeBSD-SCSI List Subject: Nice SCSI probe diagnostic is very broken for other cases Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bill, you better restore sc_print_addr() to old variant and make new variant of this function especially for probe stage printing. With your changes I have sd0: Direct-Access 516MB (1057616 512 byte sectors)sd0 at scbus0 target 0 lun 0: with 2740 cyls, 4 heads, and an average 96 sectors/track ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sc_print_addr output Moreover, many error diagnostics call sc_print_addr at the beginnig, so now some scsi error will looks like sd0 at scbus0 target 0 lun 0: cannot allocate scsi xs ^ this part can be MUCH longer for some cases What looks nice for probe stage looks very ugly for error messages. Please fix it. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-scsi Tue Feb 4 11:08:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA05772 for freebsd-scsi-outgoing; Tue, 4 Feb 1997 11:08:30 -0800 (PST) Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA05762; Tue, 4 Feb 1997 11:08:25 -0800 (PST) Received: from dragon.nuxi.com (reqb-095.ucdavis.edu [128.120.254.95]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id LAA13804; Tue, 4 Feb 1997 11:08:31 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id LAA22378; Tue, 4 Feb 1997 11:08:22 -0800 (PST) Message-ID: <19970204110821.OU09781@dragon.nuxi.com> Date: Tue, 4 Feb 1997 11:08:21 -0800 From: obrien@NUXI.com (David O'Brien) To: wpaul@freebsd.org Cc: current@freebsd.org (FreeBSD-current), scsi@freebsd.org (FreeBSD-SCSI List) Subject: Re: Nice SCSI probe diagnostic is very broken for other cases References: X-Mailer: Mutt 0.59-PL19 Mime-Version: 1.0 Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 In-Reply-To: ; from ??????????????? on Feb 4, 1997 14:00:44 +0300 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ??????????????? writes: > Bill, you better restore sc_print_addr() to old variant and make > new variant of this function especially for probe stage printing. ..snip.. > What looks nice for probe stage looks very ugly for error messages. > Please fix it. Agreed. I believe, the new form will just cause problems in bug reports. But for the probeing, the new form is quite nice. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) From owner-freebsd-scsi Tue Feb 4 23:50:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA11827 for freebsd-scsi-outgoing; Tue, 4 Feb 1997 23:50:15 -0800 (PST) Received: from freebee.tu-graz.ac.at (root@freebee.tu-graz.ac.at [129.27.193.128]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA11794 for ; Tue, 4 Feb 1997 23:50:07 -0800 (PST) Received: from dwarf.tu-graz.ac.at (dialup4.tu-graz.ac.at [129.27.250.5]) by freebee.tu-graz.ac.at (8.6.11/8.6.9) with ESMTP id IAA27207; Wed, 5 Feb 1997 08:49:34 +0100 Received: (from rmike@localhost) by dwarf.tu-graz.ac.at (8.7.5/8.7.3) id IAA00216; Wed, 5 Feb 1997 08:40:12 +0100 (MET) Date: Wed, 5 Feb 1997 08:40:11 +0100 (MET) From: Michael Ranner Reply-To: rmike@sbox.tu-graz.ac.at To: John-Mark Gurney cc: freebsd-scsi@freebsd.org Subject: Re: AHA2920 / Future Domain TMC 1830 driver for FreeBSD In-Reply-To: Message-ID: Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 3 Feb 1997, John-Mark Gurney wrote: > On Tue, 4 Feb 1997, Michael Ranner wrote: > > > > > Because I have got no answers for my last mail - once again: > > > > Is there any interest in an AHA2920 driver for freebsd? > > actually... I am... I have a TMC-1610MER that has the Future Domain 18C30 > chip on it... > > > Is somebody working on a driver for this card (except me)? > > I'm not... > > > Who can give me some technical support to get the code running? > > well... I haven't really done much with the kernel... but as soon as I get > a development machine up and running (should be soon now)... I can help... > ttyl... I will inform you about the progress! If we have a working AHA2920 driver a port to your card should be no problem. Is the TMC-1610 a PCI card? /\/\ichael Ranner - rmike@sbox.tu-graz.ac.at _o_ http://www.sbox.tu-graz.ac.at/home/rmike/ / \ ___|o o o|___ AdamsCII / \ /--(_)-(_)-(_)--\ From owner-freebsd-scsi Tue Feb 4 23:53:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA12249 for freebsd-scsi-outgoing; Tue, 4 Feb 1997 23:53:03 -0800 (PST) Received: from freebee.tu-graz.ac.at (root@freebee.tu-graz.ac.at [129.27.193.128]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA12193; Tue, 4 Feb 1997 23:52:28 -0800 (PST) Received: from dwarf.tu-graz.ac.at (dialup4.tu-graz.ac.at [129.27.250.5]) by freebee.tu-graz.ac.at (8.6.11/8.6.9) with ESMTP id IAA27212; Wed, 5 Feb 1997 08:49:48 +0100 Received: (from rmike@localhost) by dwarf.tu-graz.ac.at (8.7.5/8.7.3) id IAA00197; Wed, 5 Feb 1997 08:29:12 +0100 (MET) Date: Wed, 5 Feb 1997 08:29:12 +0100 (MET) From: Michael Ranner Reply-To: rmike@sbox.tu-graz.ac.at To: HOSOKAWA Tatsumi cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org, hosokawa@mt.cs.keio.ac.jp Subject: Re: AHA2920 / Future Domain TMC 1830 driver for FreeBSD In-Reply-To: <199702040735.QAA05519@frig.mt.cs.keio.ac.jp> Message-ID: Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 4 Feb 1997, HOSOKAWA Tatsumi wrote: > Do you mean AHA2920 uses Future Domain TMC1830 chipset? > > TMC18C30 driver for PC-card SCSI can be found in newest PAO package > ported from NetBSD/pc98 (based on NetBSD 1.2). Possibly it can be > used for ISA cards. > > See "http://www.jp.FreeBSD.org/PAO/". I tried the URL yesterday, and it seems to be interesting for me. It is possible to get parts of the source from the PAO package. Is there any person, that I can contact? Michael From owner-freebsd-scsi Wed Feb 5 00:09:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA14025 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 00:09:43 -0800 (PST) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA14013 for ; Wed, 5 Feb 1997 00:09:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hydrogen.nike.efn.org (8.8.4/8.8.4) with SMTP id AAA02500; Wed, 5 Feb 1997 00:09:12 -0800 (PST) Date: Wed, 5 Feb 1997 00:09:12 -0800 (PST) From: John-Mark Gurney Reply-To: John-Mark Gurney To: Michael Ranner cc: freebsd-scsi@freebsd.org Subject: Re: AHA2920 / Future Domain TMC 1830 driver for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 5 Feb 1997, Michael Ranner wrote: > On Mon, 3 Feb 1997, John-Mark Gurney wrote: > > > On Tue, 4 Feb 1997, Michael Ranner wrote: > > > > > Is there any interest in an AHA2920 driver for freebsd? > > > > actually... I am... I have a TMC-1610MER that has the Future Domain 18C30 > > chip on it... > > > > > Who can give me some technical support to get the code running? > > > > well... I haven't really done much with the kernel... but as soon as I get > > a development machine up and running (should be soon now)... I can help... > > ttyl... > > I will inform you about the progress! If we have a working AHA2920 driver > a port to your card should be no problem. Is the TMC-1610 a PCI card? no.. the TMC-1610 is a 16bit isa card... with a blank socket... which I would guess can house a bios... it looks like the PAO group has a working driver for the Future Domain 18C30... probably what needs to happen is possibly port the interface logic to the different busses (isa,pci,pccard)... ttyl... John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix) From owner-freebsd-scsi Wed Feb 5 01:47:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA02865 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 01:47:49 -0800 (PST) Received: from freebee.tu-graz.ac.at (freebee.tu-graz.ac.at [129.27.193.128]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA02823 for ; Wed, 5 Feb 1997 01:47:33 -0800 (PST) Received: from dwarf.tu-graz.ac.at (dialup10.tu-graz.ac.at [129.27.250.11]) by freebee.tu-graz.ac.at (8.6.11/8.6.9) with ESMTP id KAA29140; Wed, 5 Feb 1997 10:46:49 +0100 Received: (from rmike@localhost) by dwarf.tu-graz.ac.at (8.7.5/8.7.3) id JAA00559; Wed, 5 Feb 1997 09:28:30 +0100 (MET) Date: Wed, 5 Feb 1997 09:28:30 +0100 (MET) From: Michael Ranner Reply-To: rmike@sbox.tu-graz.ac.at To: John-Mark Gurney cc: freebsd-scsi@freebsd.org Subject: Re: AHA2920 / Future Domain TMC 1830 driver for FreeBSD In-Reply-To: Message-ID: Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 5 Feb 1997, John-Mark Gurney wrote: > > I will inform you about the progress! If we have a working AHA2920 driver > > a port to your card should be no problem. Is the TMC-1610 a PCI card? > > no.. the TMC-1610 is a 16bit isa card... with a blank socket... which I > would guess can house a bios... > > it looks like the PAO group has a working driver for the Future Domain > 18C30... probably what needs to happen is possibly port the interface > logic to the different busses (isa,pci,pccard)... ttyl... Yes I know! I try to contact the PAO group via Hosokawa Tatsumi, hoping that I could get some parts of the source. The PCI interface is currently working for my AHA2920 driver, but I have some other problems with the low level source! /\/\ichael Ranner - rmike@sbox.tu-graz.ac.at http://www.sbox.tu-graz.ac.at/home/rmike/ . . + + . - - - - - ----* . . + Where there's foo, there's fire! From owner-freebsd-scsi Wed Feb 5 11:08:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA02413 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 11:08:00 -0800 (PST) Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA02404 for ; Wed, 5 Feb 1997 11:07:51 -0800 (PST) Received: from dragon.nuxi.com (reqf-022.ucdavis.edu [128.120.253.142]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id LAA25425; Wed, 5 Feb 1997 11:07:51 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id LAA07155; Wed, 5 Feb 1997 11:07:40 -0800 (PST) Message-ID: <19970205110739.CM38559@dragon.nuxi.com> Date: Wed, 5 Feb 1997 11:07:39 -0800 From: obrien@NUXI.com (David O'Brien) To: freebsd-scsi@freebsd.org Cc: CVS-committers@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/dev/aic7xxx aic7xxx.seq src/sys/i386/scsi aic7xxx.c aic7xxx.h References: <199702030216.SAA01223@freefall.freebsd.org> X-Mailer: Mutt 0.59-PL19 Mime-Version: 1.0 Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 In-Reply-To: <199702030216.SAA01223@freefall.freebsd.org>; from Justin T. Gibbs on Feb 2, 1997 18:16:18 -0800 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs writes: > gibbs 97/02/02 18:16:17 > > Modified: sys/dev/aic7xxx aic7xxx.seq > Revision Changes Path > 1.57 +3 -6 src/sys/dev/aic7xxx/aic7xxx.seq > > Modified: sys/i386/scsi aic7xxx.c aic7xxx.h > Revision Changes Path > 1.93 +49 -24 src/sys/i386/scsi/aic7xxx.c > 1.36 +13 -1 src/sys/i386/scsi/aic7xxx.h YES!!! :-)))))))))))))))))))))))) I've been running these bits for three days now, and NOT a single panic. Which I was getting quite often with the last commit. NOT a single SCB or reset console error message, which I was getting somewhat often with two commits ago. These bits have let FreeBSD regain a level of stability above MS-DOS on my machine. Others? Thanks Justin. :-) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) From owner-freebsd-scsi Wed Feb 5 14:50:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA19121 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 14:50:26 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA19106 for ; Wed, 5 Feb 1997 14:50:20 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id XAA04701; Wed, 5 Feb 1997 23:16:28 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.5/8.8.2) id WAA12832; Wed, 5 Feb 1997 22:52:56 +0100 (MET) Message-ID: <19970205225255.CI12150@klemm.gtn.com> Date: Wed, 5 Feb 1997 22:52:55 +0100 From: andreas@klemm.gtn.com (Andreas Klemm) To: obrien@NUXI.com (David O'Brien) Cc: freebsd-scsi@FreeBSD.org, CVS-committers@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/dev/aic7xxx aic7xxx.seq src/sys/i386/scsi aic7xxx.c aic7xxx.h References: <199702030216.SAA01223@freefall.freebsd.org> <19970205110739.CM38559@dragon.nuxi.com> X-Mailer: Mutt 0.60-PL0 Mime-Version: 1.0 In-Reply-To: <19970205110739.CM38559@dragon.nuxi.com>; from "David O'Brien" on Feb 5, 1997 11:07:39 -0800 Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I still get these messages when using this kernel config ... options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO Hardware: AHA 2940 1.16 sd0: type 0 fixed SCSI 2 sd1: type 0 fixed SCSI 2 Feb 5 19:56:49 klemm /kernel: sd1 at scbus0 target 1 lun 0: data overrun of 510 bytes detected. Forcing a retry. David O'Brien writes: > Justin T. Gibbs writes: > > gibbs 97/02/02 18:16:17 > > > > Modified: sys/dev/aic7xxx aic7xxx.seq > > Revision Changes Path > > 1.57 +3 -6 src/sys/dev/aic7xxx/aic7xxx.seq > > > > Modified: sys/i386/scsi aic7xxx.c aic7xxx.h > > Revision Changes Path > > 1.93 +49 -24 src/sys/i386/scsi/aic7xxx.c > > 1.36 +13 -1 src/sys/i386/scsi/aic7xxx.h > > > YES!!! :-)))))))))))))))))))))))) > > I've been running these bits for three days now, and NOT a single panic. > Which I was getting quite often with the last commit. NOT a single SCB > or reset console error message, which I was getting somewhat often with > two commits ago. > > These bits have let FreeBSD regain a level of stability above MS-DOS on > my machine. Others? -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-scsi Wed Feb 5 14:55:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA19577 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 14:55:04 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA19566 for ; Wed, 5 Feb 1997 14:54:59 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id PAA05822 for freebsd-scsi@freebsd.org; Wed, 5 Feb 1997 15:54:15 -0800 (PST) Resent-Message-Id: <199702052354.PAA05822@sendero.i-connect.net> Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Resent-Date: Wed, 05 Feb 1997 15:20:28 -0800 (PST) Resent-From: Simon Shapiro Resent-To: freebsd-scsi@freebsd.org Date: Wed, 05 Feb 1997 15:53:40 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: freebsd-scsi@freebsd.org Subject: FW: Some SCSI Questions... Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ----- Forwarded Message ----: Some SCSI Questions...----- Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 05 Feb 1997 15:20:28 -0800 (PST) Organization: iConnect Corp. XFMstatus: 0610 From: Simon Shapiro To: freebsd-scsi@freebsd.org Subject: Some SCSI Questions... Hi Y'all, Me again, with more questions: 1. I want to port cdwrite 2.0 from Linux (and get rid but have no clue what the userland API to the generic device (userland SCB) is. Can someone please help me with: a. What is the /dev entry? b. What options in config do I need to turn on? c. (At least) header file pathname to API 2. In writing a SCSI device driver, how does one differentiate a device reset from bus reset from HBA reset? I can guess, that an HBA reset may come as a device reset flag in the xs struct, destined for the HBA's target ID. But on which bus? We have an HBA which has three busses. We can have multiple of these HBA's in the system. We set the HBA softc struct as an array (linked list, actually) of softc structures. In each softc we have an array of scsi_link structures to manage that. But question #2 is not answered by that, to my understanding. Thanx! Simon -------------End of forwarding message------------------------- From owner-freebsd-scsi Wed Feb 5 14:55:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA19610 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 14:55:14 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA19597 for ; Wed, 5 Feb 1997 14:55:10 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id PAA05831 for freebsd-scsi@freebsd.org; Wed, 5 Feb 1997 15:54:19 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 05 Feb 1997 15:44:31 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: freebsd-scsi@freebsd.org Subject: RE: Some SCSI Questions... Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, Me again, with more questions: 1. I want to port cdwrite 2.0 from Linux (and get rid but have no clue what the userland API to the generic device (userland SCB) is. Can someone please help me with: a. What is the /dev entry? b. What options in config do I need to turn on? c. (At least) header file pathname to API 2. In writing a SCSI device driver, how does one differentiate a device reset from bus reset from HBA reset? I can guess, that an HBA reset may come as a device reset flag in the xs struct, destined for the HBA's target ID. But on which bus? Based on the Unit number? We have an HBA which has three busses. We can have multiple of these HBA's in the system. We set the HBA softc struct as an array (linked list, actually) of softc structures. In each softc we have an array of scsi_link structures to manage that. But question #2 is not answered by that, to my understanding. In other words; We need to differentiate (in the case of an HBA reset) between resetting the HBA itself, resetting any given bus attached to the HBA and resetting a device attached. If the HBA does target mode, we could argue, that the device reset, applies to the HBA as a target, not to the HBA as a controller. Right? Thanx! Simon From owner-freebsd-scsi Wed Feb 5 14:55:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA19659 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 14:55:56 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA19652 for ; Wed, 5 Feb 1997 14:55:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id OAA12048; Wed, 5 Feb 1997 14:55:34 -0800 (PST) Message-Id: <199702052255.OAA12048@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: andreas@klemm.gtn.com (Andreas Klemm) cc: obrien@NUXI.com (David O'Brien), freebsd-scsi@FreeBSD.org, CVS-committers@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/dev/aic7xxx aic7xxx.seq src/sys/i386/scsi aic7xxx.c aic7xxx.h In-reply-to: Your message of "Wed, 05 Feb 1997 22:52:55 +0100." <19970205225255.CI12150@klemm.gtn.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 05 Feb 1997 14:55:34 -0800 Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I still get these messages when using this kernel config ... > >options AHC_TAGENABLE >options AHC_SCBPAGING_ENABLE >options AHC_ALLOW_MEMIO > >Hardware: AHA 2940 1.16 >sd0: type 0 fixed SCSI 2 >sd1: type 0 fixed SCSI 2 > >Feb 5 19:56:49 klemm /kernel: sd1 at scbus0 target 1 lun 0: data overrun of 510 bytes detected. Forcing a retry. ...and wcarchive falls over dead a couple of times a day with all sorts of interesting data phase timeouts and "Unexpected busfrees". Justin's working on it, though, and I'm sure this will get resolved shortly. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-scsi Wed Feb 5 15:27:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA22546 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 15:27:21 -0800 (PST) Received: from hda.hda.com (ip78-max1-fitch.ziplink.net [199.232.245.78]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA22539 for ; Wed, 5 Feb 1997 15:27:16 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id SAA01744; Wed, 5 Feb 1997 18:21:25 -0500 From: Peter Dufault Message-Id: <199702052321.SAA01744@hda.hda.com> Subject: Re: Some SCSI Questions... In-Reply-To: from Simon Shapiro at "Feb 5, 97 03:44:31 pm" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Wed, 5 Feb 1997 18:21:24 -0500 (EST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [Charset iso-8859-8 unsupported, filtering to ASCII...] > Hi Y'all, > > Me again, with more questions: > > 1. I want to port cdwrite 2.0 from Linux (and get rid but have no clue > what the userland API to the generic device (userland SCB) is. > Can someone > please help me with: > > a. What is the /dev entry? The .ctl entry, e.g., /dev/rcd0a.ctl > b. What options in config do I need to turn on? None. > c. (At least) header file pathname to API sys/scsiio.h and scsi.h for the library. Try "man 3 scsi" and "man 8 scsi". Also, I'm sending a new test release under separate mail for your input. I don't know how well developed the reset code is. I'd expect that an xs will target a given bus. The "scsiop" escapes were in there to support, e.g., resetting a specific device versus the bus. See the aha code. Probably Justin has to explain it from here. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-scsi Wed Feb 5 15:51:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA24494 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 15:51:55 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA24476 for ; Wed, 5 Feb 1997 15:51:49 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA21611; Thu, 6 Feb 1997 00:51:38 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id AAA14921; Thu, 6 Feb 1997 00:43:15 +0100 (MET) Message-ID: Date: Thu, 6 Feb 1997 00:43:14 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: Shimon@i-Connect.Net (Simon Shapiro) Cc: freebsd-scsi@freebsd.org Subject: Re: Some SCSI Questions... References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Simon Shapiro on Feb 5, 1997 15:44:31 -0800 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Simon Shapiro wrote: > 1. I want to port cdwrite 2.0 from Linux Is there a particular reason why you're not satisfied with worm(4)? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Wed Feb 5 18:36:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA06078 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 18:36:47 -0800 (PST) Received: from mail-relay.ubc.ca (mail-relay.ubc.ca [137.82.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA06073 for ; Wed, 5 Feb 1997 18:36:42 -0800 (PST) Received: from ubc.ca (gafs.geop.ubc.ca [137.82.49.1]) by mail-relay.ubc.ca (8.7.6/1.14) with SMTP id SAA11212 for ; Wed, 5 Feb 1997 18:36:28 -0800 (PST) Received: from moho.ubc.ca (moho.ARPA) by ubc.ca (4.1/1.14) id AA18597; Wed, 5 Feb 97 18:36:26 PST Received: by moho.ubc.ca (SMI-8.6/SMI-SVR4) id SAA01750; Wed, 5 Feb 1997 18:36:23 -0800 Date: Wed, 5 Feb 1997 18:36:23 -0800 From: amor@geop.ubc.ca (John Amor) Message-Id: <199702060236.SAA01750@moho.ubc.ca> To: freebsd-scsi@freebsd.org Subject: HP6020i CDR fails on fixation X-Sun-Charset: US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am having problems sending the fixate command to a HP6020i CDR. The worm.c code burns the file system but dies when the final fixate command is given. Resulting in a useless CD. Doing a dry run with the dummy option is fine. The only changes I have made was; 1) add the following to the scsiconf.c code to identify the device at boot time. { T_READONLY, T_WORM, T_REMOV, "HP", "CD-Writer 6020", "*", "worm", SC_ONE_LU }, 2) commented out the two calls "scsi_stop_unit" and "scsi_prevent" in the worm_close function in worm.c. These lines seemed to casued the drive to report "Not Ready" for any command after the "wormcontrol select HP 4020i" was run. Opening and closing the CDR clears the message. Here is the run that failed # wormcontrol select HP 4020i # wormcontrol prepdisk double # wormcontrol track data # rtprio 5 team -v 1m 5 < cnsn8.cd | rtprio 5 dd of=/dev/rworm0 obs=20k 631938 kilobytes, 2099 seconds 1263876+0 records in 31596+1 records out 647104512 bytes transferred in 2109.314342 secs (306784 bytes/sec) # wormcontrol fixate 1 wormcontrol: ioctl(WORMIOFIXATION): Input/output error # Note: 3-5 second delay from fixate command and error message (as I recall). >From the worm.c code hp4020i_finalize_disk(struct scsi_link *sc_link, int toc_type, int onp) { struct scsi_fixation cmd; SC_DEBUG(sc_link, SDEV_DB2, ("hp4020i_finalize_disk")); if (toc_type < 0 || toc_type > WORM_TOC_TYPE_CDI) return EINVAL; /* * Fixate this session. Mark the next one as opened if onp * is true. Otherwise, the disk will be finalized once and * for all. ONP stands for "open next program area". */ bzero(&cmd, sizeof(cmd)); cmd.op_code = FIXATION; cmd.action = (onp? WORM_FIXATION_ONP: 0) + toc_type; return scsi_scsi_cmd(sc_link, (struct scsi_generic *) &cmd, sizeof(cmd), 0, /* no data transfer */ 0, 1, 20*60*1000, /* takes a huge amount of time */ NULL, 0); } It would appear that scsi_scsi_cmd is returning EIO ??? If I am way off base perhaps someone could suggest a more likely location for the problem. I hate to create more coasters for my coffee cup. Thanks, John ---------------------------------------------------------------------------- John Amor -- Systems Manager -- Geophysical Research Processing Facility amor@eos.ubc.ca (604) 822-6933 Department of Earth and Ocean Sciences http://www.geop.ubc.ca/~amor/amor.html University of British Columbia, Canada ------------------------------------------------------------------------------ F.Y.I. More background... The HP-4020i scsi command info is in the http://www.hp.com/isgsupport/cdr under product info. ----------------------------------------------------------------------- According to various people, the philips cdd2600 is the same unit as the HP6020. From the philips site they have a manual for the 2600 which gives the scsi command set used. .... from philips online manual for the CDD2600 ... The following lists the supported SCSI commands. An extensive description of the total command set is avaliable on request. Messages in = Target to Initiator out = Initiator to Target 00h command complete in 02h save data pointer in 04h disconnect in 06h abort out 07h message reject in out 08h no operation out 0ch bus device reset out 80h+ identify in out Recorder group 0 commands 00 Test unit ready 01 Rezero Unit 03 Request Sense 08 Read 0a write 0b Seek 12 Inquiry 15 Mode Select 16 Reserve 17 Release 18 Copy 1a Mode Sense 1b Start/Stop Unit 1c Recieve Diagnostic Results 1d send Diagnostics 1e prevent/Allow medium removal Group 1& 2 - ten byte commands 25 Read Capacity 28 Read 2a write 2b Seek 2f Verify 35 Flush Cashe 3b Write Buffer 3c Read Buffer 42 Read Sub Channel 43 Read Disk info 45 Play Audio 47 Play Audio MSF 48 Play Audio Track / Index 4b Pause Resume 55 mode select 5a mode sense Vendor Unique commands d1 Read Disc ID d2 READ OPC d3 write OPC e2 First writable address e3 format track e4 reserve track e5 read track info e6 write track e7 medium load/unload e8 finish track e9 fixation (write leadin and leadout) eb send absorption control errors ec recover ed write ee read session info From owner-freebsd-scsi Wed Feb 5 19:54:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA02809 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 19:54:51 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA02789; Wed, 5 Feb 1997 19:54:42 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id UAA06804; Wed, 5 Feb 1997 20:53:54 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 05 Feb 1997 19:33:54 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org Subject: Contigious (spelling?) allocation in kernel Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I need to allocate a contigious (one piece :-) block of memory for a DMA scatter/gather list. The HBA knows how to do scatter gather, but wants a single pointer to a single block of memory that hoslds the entire list. The SG structure is very plain, 32bits for length and 32bits for physical address; 8 bytes. The thing is capable of up to 8192 entries, which give us a possible list of 64KB per request list. As each HBA can have up to 256 concurrent requests, with who knows how many more in the driver's queue, the list can grow quite impressively. Since most requests are smaller, it seems very wasteful to allocate all this memory upfront. So malloc is in order, but what are the options? Thanx, Simon From owner-freebsd-scsi Wed Feb 5 20:54:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA06921 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 20:54:21 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA06893; Wed, 5 Feb 1997 20:54:15 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id PAA00702; Thu, 6 Feb 1997 15:23:45 +1030 (CST) From: Michael Smith Message-Id: <199702060453.PAA00702@genesis.atrad.adelaide.edu.au> Subject: Re: Contigious (spelling?) allocation in kernel In-Reply-To: from Simon Shapiro at "Feb 5, 97 07:33:54 pm" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Thu, 6 Feb 1997 15:23:45 +1030 (CST) Cc: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro stands accused of saying: > I need to allocate a contigious (one piece :-) block of memory for a DMA > scatter/gather list. The HBA knows how to do scatter gather, but wants a > single pointer to a single block of memory that hoslds the entire list. That's a bit icky 8) > The SG structure is very plain, 32bits for length and 32bits for physical > address; 8 bytes. The thing is capable of up to 8192 entries, which give > us a possible list of 64KB per request list. You might want to check on the s/g limit for block I/O for FreeBSD; it's quite possible that something like that is far beyond anything that it's likely to do. In most cases, I/O is likely to be in page-sized (4K) chunks, with a limit of 64K (MAXPHYS). You'd have to ask Bruce or possibly Justin about that; I don't know where to look to confirm such a limit. > As each HBA can have up to 256 concurrent requests, with who knows how > many more in the driver's queue, the list can grow quite impressively. > Since most requests are smaller, it seems very wasteful to allocate all > this memory upfront. So malloc is in order, but what are the options? I'd start with a small pool of permanently-allocated (get them at driver startup time) S/G lists of some empirically determined "adequate" size. Keep enough of these around so that you can cover the maximum number of concurrent outstanding transactions (or possibly just grow your pool as required). Use the BSD queue macros to efficiently manage your buffer lists. If you get a request bigger than will fit in your "normal" S/G block, allocate one temporarily, and throw it away when you're done. As far as actually allocating the suckers goes, contigmalloc() is probably what you're after; call it contigmalloc(size, M_DEVBUF, M_NOWAIT, low, high, align), where low and high are the lowest and highest legal physical addresses, and align is the alignment size for the structure. It sounds like you're talking to a PCI device, so 0, ULONG_MAX and sizeof(u_long) respectively should do the trick. > Simon -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-scsi Wed Feb 5 21:12:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA08588 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 21:12:27 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA08524; Wed, 5 Feb 1997 21:12:09 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id AAA10010; Thu, 6 Feb 1997 00:12:02 -0500 (EST) From: "John S. Dyson" Message-Id: <199702060512.AAA10010@dyson.iquest.net> Subject: Re: Contigious (spelling?) allocation in kernel To: Shimon@i-Connect.Net (Simon Shapiro) Date: Thu, 6 Feb 1997 00:12:02 -0500 (EST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Simon Shapiro" at Feb 5, 97 07:33:54 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Take a look at contigmalloc() or vm_page_alloc_contig() as defined in /sys/vm/vm_page.c. These are almost guaranteed NOT to work after the system is fully up. John From owner-freebsd-scsi Wed Feb 5 21:34:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA11867 for freebsd-scsi-outgoing; Wed, 5 Feb 1997 21:34:05 -0800 (PST) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA11824; Wed, 5 Feb 1997 21:33:54 -0800 (PST) Received: from narnia (localhost [127.0.0.1]) by narnia.plutotech.com (8.8.5/8.7.3) with ESMTP id VAA00624; Wed, 5 Feb 1997 21:33:58 -0800 (PST) Message-Id: <199702060533.VAA00624@narnia.plutotech.com> To: Simon Shapiro cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Contigious (spelling?) allocation in kernel In-reply-to: Your message of "Wed, 05 Feb 1997 19:33:54 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Feb 1997 21:33:57 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I need to allocate a contigious (one piece :-) block of memory for a DMA >scatter/gather list. If it is more than a page, you must use contigmalloc. contigmalloc may only be used close to boot time if you want to ensure it will work. >The HBA knows how to do scatter gather, but wants a >single pointer to a single block of memory that holds the entire list. >The SG structure is very plain, 32bits for length and 32bits for physical >address; 8 bytes. The thing is capable of up to 8192 entries, which give >us a possible list of 64KB per request list. You really think you're going to ever transfer a full 32MB of data in a single transaction? Even if you were, you'd have to do something special to the kernel since it currently only generates requests of at most 64k (its a silly restriction and it should die a horrible death). Assuming you did have a way to stuff 32MB through all of the layers, you'd probably be better off chopping that I/O into smaller chunks so as to reduce the amount of SG space you must allocate. At anything over 8k, the transaction overhead starts to become an increasingly small percentage of your I/O time, so dropping even down as low as 1MB per transaction may better utilize your resources. >As each HBA can have up to 256 concurrent requests, with who knows how >many more in the driver's queue, the list can grow quite impressively. >Since most requests are smaller, it seems very wasteful to allocate all >this memory upfront. So malloc is in order, but what are the options? You don't want to continuously malloc your SG list. This will kill your performance. If it is acceptable for the system to run with all 256 requests active at once, you have to be able to deal with all of the requests being allocated anyway, so you might as well pool them. >Thanx, > >Simon -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Thu Feb 6 01:10:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA23823 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 01:10:04 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA23793 for ; Thu, 6 Feb 1997 01:09:58 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA00937; Thu, 6 Feb 1997 10:09:52 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id KAA08112; Thu, 6 Feb 1997 10:05:50 +0100 (MET) Message-ID: Date: Thu, 6 Feb 1997 10:05:50 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: amor@geop.ubc.ca (John Amor) Cc: freebsd-scsi@freebsd.org Subject: Re: HP6020i CDR fails on fixation References: <199702060236.SAA01750@moho.ubc.ca> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702060236.SAA01750@moho.ubc.ca>; from John Amor on Feb 5, 1997 18:36:23 -0800 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As John Amor wrote: > # wormcontrol fixate 1 > wormcontrol: ioctl(WORMIOFIXATION): Input/output error Well, the SCSI error is important here. It translates into an EIO in the driver level -- that's the only thing the driver could do. The SCSI error itself will be syslogged. > F.Y.I. More background... > > The HP-4020i scsi command info is in the http://www.hp.com/isgsupport/cdr > under product info. > The following lists the supported SCSI commands. An extensive description > of the total command set is avaliable on request. Hmm, but sure, we did already send a SCSI command, so this list is not of much use. :-) What's more important is looking up the ASC/ASCQ combination in that docs (additional sense code, additional sense code qualifier). IIRC, it was a vendor-specific one in your case, so it could not be found in the generic SCSI-2 specs. Btw., i just remember somebody reporting me a similar event (SCSI error in fixation phase), and it turned out to be overheating in his case. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Thu Feb 6 06:44:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA13714 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 06:44:29 -0800 (PST) Received: from hda.hda.com (ip3-max1-fitch.ziplink.net [199.232.245.3]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA13691 for ; Thu, 6 Feb 1997 06:44:21 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id JAA00390 for scsi@freebsd.org; Thu, 6 Feb 1997 09:39:32 -0500 From: Peter Dufault Message-Id: <199702061439.JAA00390@hda.hda.com> Subject: new scsi(8) To: scsi@freebsd.org Date: Thu, 6 Feb 1997 09:39:32 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk All the talk about defects, etc, convinced me to dust off something I started way back and release it for comments. I've put a new scsi(8) and scsi(3) on freefall in ~ftp/incoming for review and feedback: > scsinew.tgz Here is the README: This is a feedback release of a rewrite of scsi(8) to add commands to the equivalent of the modes data base and to be better suited for being driven by external programs. It includes a sample Tk application that attempts to display the cylinder zones and defects on a disk drive. Note that Joerg reports the defect reading hangs one of his drives, so be careful. The new scsi(8) program adds these switches: > scsi [-S style] -I # To enter commands interactively > "style" can be "tcl" for tcl list oriented output > scsi -C capfile # To load a cap file > "-C capfile" can occur as often as you want. The program now tries to load both scsi_modes and scsi_caps. These files can have entries such as: > # ndefects plist glist > ndefects "37 0 0:3 {plist} v:1 {vlist} v:1 5:3 0 0 0 0 4:i2 0" \ > -i 4 "*i2 {Defect list length} i2" > > # defects plist glist size > defects "37 0 0:3 {plist} v:1 {vlist} v:1 5:3 0 0 0 0 {xfer} v:i2 0" \ > -i v "s4 ( {Cylinder} i3 {Head} i1 {Sector} i4)" (Note: infinite loops are added in formats with parenthesis that will loop until data is exhausted) Using the TCL style these will work like this: > rt# ./scsinew -f sd0 -S tcl -C caps -I > scsi> ndefects 1 1 > 80 > scsi> defects 80 1 1 80 > {771 0 18} {771 0 19} {1671 4 87} {1703 3 80} {1704 3 80} {1704 3 81} {1866 1 95} {1922 0 47} {1932 3 33} {2184 3 0} > scsi> and the verbose TCL style: > rt# !! -v > ./scsinew -f sd0 -S tcl -C caps -I -v > scsi> ndefects 1 1 > { {Defect list length} 80} > scsi> defects 80 1 1 80 > {{ {Cylinder} 771} { {Head} 0} { {Sector} 18} } {{ {Cylinder} 771} { {Head} 0} { {Sector} 19} } {{ {Cylinder} 1671} { {Head} 4} { {Sector} 87} } {{ {Cylinder} 1703} { {Head} 3} { {Sector} 80} } {{ {Cylinder} 1704} { {Head} 3} { {Sector} 80} } {{ {Cylinder} 1704} { {Head} 3} { {Sector} 81} } {{ {Cylinder} 1866} { {Head} 1} { {Sector} 95} } {{ {Cylinder} 1922} { {Head} 0} { {Sector} 47} } {{ {Cylinder} 1932} { {Head} 3} { {Sector} 33} } {{ {Cylinder} 2184} { {Head} 3} { {Sector} 0} } > scsi> (the line wrap is artificial) Some things to look at: 1. In cmd.c I turned off the noise that echoed arguments back in verbose mode. I don't think this is needed. Look for "if 0" 2. Loops shouldn't have to be infinite. 3. I should decide how to handle errors in non-default style. The current setup is not appropriate for begin driven by another program. For example, for a TCL style output we may want to go to: 0 { ... } Where the 0 is the error result and the { ... } is the current decoded output. Then on error you may have: 64 { sense } or something -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-scsi Thu Feb 6 11:22:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA23531 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 11:22:09 -0800 (PST) Received: from mail-relay.ubc.ca (mail-relay.ubc.ca [137.82.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA23524 for ; Thu, 6 Feb 1997 11:22:02 -0800 (PST) Received: from ubc.ca (gafs.geop.ubc.ca [137.82.49.1]) by mail-relay.ubc.ca (8.7.6/1.14) with SMTP id LAA29646; Thu, 6 Feb 1997 11:21:50 -0800 (PST) Received: from moho.ubc.ca (moho.ARPA) by ubc.ca (4.1/1.14) id AA21186; Thu, 6 Feb 97 11:21:49 PST Received: by moho.ubc.ca (SMI-8.6/SMI-SVR4) id LAA01863; Thu, 6 Feb 1997 11:21:48 -0800 Date: Thu, 6 Feb 1997 11:21:48 -0800 From: amor@geop.ubc.ca (John Amor) Message-Id: <199702061921.LAA01863@moho.ubc.ca> To: joerg_wunsch@uriah.heep.sax.de Subject: Re: HP6020i CDR fails on fixation Cc: freebsd-scsi@freebsd.org X-Sun-Charset: US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for all your help joerg! I have burned a successfull CD! I moved the CDR down in the box to give it more cooling it was right under an IDE cdrom. I guess the added air flow may have made the difference?? Is the burning of the fixation as time dependent? Last time I ran the commands by hand, this time I used the script. Thanks again! John From owner-freebsd-scsi Thu Feb 6 12:18:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA01905 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 12:18:02 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA01890; Thu, 6 Feb 1997 12:17:57 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id NAA09330; Thu, 6 Feb 1997 13:17:01 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199702060512.AAA10010@dyson.iquest.net> Date: Thu, 06 Feb 1997 09:55:40 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: "John S. Dyson" Subject: Re: Contigious (spelling?) allocation in kernel Cc: freebsd-hackers@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi John S. Dyson; On 06-Feb-97 you wrote: > Take a look at contigmalloc() or vm_page_alloc_contig() > as defined in /sys/vm/vm_page.c. These are almost > guaranteed NOT to work after the system is fully up. Thanx. If you (or someone else) please elaborate on the last sentence, please... I can re-structure the driver a bit (make it more risky), to avoid the need for large contigious blocks, but the (obvious) question is: Does the kernel malloc guarantee that allocations smaller than (or equal to) a page are in the same page? Having a page or less, limits the Scatter/Gather operations in the kernel, for most hardware, to 512 entries (segments). Under high fragmentation, this can result in 256KB-2MB floating limit. While not a problem for most applications (mine included), it is still a limit that is not absolutely necessary. Any opposing opinions (before I re-code the darn thing :-)? BACKGROUND: One of my engineers, who is heavily involved in Linux SCSI development is strongly opposed to calling malloc on demand in a device driver. He quotes heavy performance penalties, and worse; Failure (under heavy load) to obtain the memory when needed. Thanx, Simon From owner-freebsd-scsi Thu Feb 6 12:18:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA02090 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 12:18:44 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA02050 for ; Thu, 6 Feb 1997 12:18:34 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id NAA09331; Thu, 6 Feb 1997 13:17:01 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199702052321.SAA01744@hda.hda.com> Date: Thu, 06 Feb 1997 11:10:41 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: Peter Dufault Subject: Re: Some SCSI Questions... Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Peter Dufault; On 05-Feb-97 you wrote: ... > > a. What is the /dev entry? > > The .ctl entry, e.g., /dev/rcd0a.ctl Ah! Almost Plan9 :-) > > b. What options in config do I need to turn on? > None. Good! No mistakes possible here :-) > > c. (At least) header file pathname to API > > sys/scsiio.h and scsi.h for the library. Try "man 3 scsi" and "man 8 scsi". Aha! This is where they went. Thanx. > Also, I'm sending a new test release under separate mail for your input. > > I don't know how well developed the reset code is. I'd expect > that an xs will target a given bus. The "scsiop" escapes were > in there to support, e.g., resetting a specific device versus > the bus. See the aha code. Probably Justin has to explain it from here. A device is not my problem. The code i have seen appears to synonym an HBA with its bus, and reset both. Even the Adaptec 39xx are really a single bus device, so resetting one resets the other. I am dealing with an HBA that has three distinct busses on the same controller. When and if a reset is necessary, I need a way to know what to reset: The HBA itself or its SCSI busses (which one?). These are not the same. consider an HBA with 3 SCSI wide busses, each having only 15 devices. Now, a SCSI_RESET command comes from above (why?). Say why = bus timeout (the easiest case). Do I reset the HBA, taking down 30 disk drives that have no problem, along with several hundreds of queued commands? Just trying to detangle the queued, tagged, in-driver queued, etc. commands will make you grey in the head quickly. Now, add to this a multi-initiator, where each SCSI bus has at least TWO HBA's on it. each running from a separate host, maybe not FreeBSD on the other side. Maybe NT. We don't know. This is why I am trying to understand the reset policy. The question of differentiating driver/HBA/bus/device reset is just an opener, to get me somewhat familiar with the surroundings. Once we solve this problem, we will have a very interesting set of I/O capabilities. Thanx for all your patience... Simon From owner-freebsd-scsi Thu Feb 6 12:18:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA02126 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 12:18:52 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA02112 for ; Thu, 6 Feb 1997 12:18:49 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id NAA09333; Thu, 6 Feb 1997 13:17:01 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 06 Feb 1997 11:41:18 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: (Joerg Wunsch) Subject: Re: Some SCSI Questions... Cc: freebsd-scsi@freebsd.org, (J Wunsch) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi J Wunsch; On 05-Feb-97 you wrote: > As Simon Shapiro wrote: > > > 1. I want to port cdwrite 2.0 from Linux > > Is there a particular reason why you're not satisfied with worm(4)? What you do not know can (and usually will) hurt you :-) The next question is about Yamaha CDR-100 support. Will I have to provide it? Simon From owner-freebsd-scsi Thu Feb 6 12:36:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA03460 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 12:36:56 -0800 (PST) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA03452; Thu, 6 Feb 1997 12:36:53 -0800 (PST) Received: from narnia (localhost [127.0.0.1]) by narnia.plutotech.com (8.8.5/8.7.3) with ESMTP id MAA01871; Thu, 6 Feb 1997 12:36:53 -0800 (PST) Message-Id: <199702062036.MAA01871@narnia.plutotech.com> To: Simon Shapiro cc: "Justin T. Gibbs" , freebsd-hackers@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Contigious (spelling?) allocation in kernel In-reply-to: Your message of "Thu, 06 Feb 1997 10:35:32 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Feb 1997 12:36:53 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Agree. The board vendor would like to see these large transfers. But a 1MB >limit is not unreasonable. > Okay, so if you can live with 2MB or less per transaction, you'll have at most a page worth of SG list per transaction, and you can use regular malloc to pool them as you like. The aic7xxx driver does this for its SG list already, allocating a page worth of SG lists each time. I used to have the SG list maxed out at 256 (the limit of these controllers), but recently dropped it down to 32 until the 64k limit goes away (17 would be sufficient for anything that the kernel does, but I wanted it to be a power of 2 for efficient pooling). >All this brings me to another question. How can I create another kernel >thread? > You have a couple choices. One is to make another in-kernel process like the page daemon. Another is to add software interrupt handlers for your tasks. This can work well if your workload has clean interdependencies. For example, the CAM SCSI code will add another software interrupt handler that deals with work provided by the controller's interrupt routine at a lower priority then the hardware interrupts themselves. This ensures that your controller interrupt handler is as short as possible (they curently call up into the mid layer at raised SPL blocking other interrupts) as the current scheme can be really nasty if you are sharing an interrupt with a device that requires fast response times (like a Fibre Channel or ethernet card). >Thanx, > >Simon > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Thu Feb 6 15:17:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA13931 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 15:17:55 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA13913; Thu, 6 Feb 1997 15:17:48 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id PAA06651; Thu, 6 Feb 1997 15:14:48 -0800 (PST) Message-ID: <32FA657D.446B9B3D@whistle.com> Date: Thu, 06 Feb 1997 15:13:01 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Simon Shapiro CC: "Justin T. Gibbs" , freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Contigious (spelling?) allocation in kernel References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro wrote: > > All this brings me to another question. How can I create another kernel > thread? What I am trying to do is have several execution threads in the > kernel, each responsible for a given task. All I see in the drivers I > read so far is a single thread, associated wit hthe calling user process. > Another thread is invoked by the interrupt handler. I want a couple more. > > One ugly way to do it is to have a ``daemon'' which makes a known system > call (ioctl) which is never returned. Aside from being ugly, it has a > problem at boot time; The daemon is not there until way after init has > started. you can use timeouts to get schedules kernel activity.. it's not a thread though. We don't really have kernl threads in a totally separate context however. > > What I am after is something that could resemble the swapper. > Linux has few of them and they become very handy. Especially on an SMP > machine. well you could do what the swap daemon does.. it's started from the kernel.. it's more a kernel PROCESS than a kernel thread. From owner-freebsd-scsi Thu Feb 6 15:30:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA14813 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 15:30:58 -0800 (PST) Received: from www.destek.net (ns2.destek.net [192.156.97.61]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA14802 for ; Thu, 6 Feb 1997 15:30:45 -0800 (PST) Received: from synergy.Destek.Net (root@synergy.destek.net [199.125.115.161]) by www.destek.net (8.8.5/8.8.4) with ESMTP id SAA14916 for ; Thu, 6 Feb 1997 18:30:23 -0500 (EST) Received: from [[UNIX: localhost]] ([[UNIX: localhost]]) by synergy.Destek.Net (8.8.4/8.7.3) with SMTP id SAA19941 for ; Thu, 6 Feb 1997 18:30:18 -0500 (EST) Message-Id: <199702062330.SAA19941@synergy.Destek.Net> X-Authentication-Warning: synergy.Destek.Net: [[UNIX: localhost]] didn't use HELO protocol X-Mailer: exmh version 2.0gamma 1/24/96 X-Uri: X-Face: ">4>,~~_HqlZ,c;!7K60$oLXj\whr`|V-}}cog.gO2Q^/CC[E>,Ez*N0C#)CYY8J\]APjp6 ~)]fwuyFuTXe{7z'Zgt,=+chm*DPh([b^SBn.^jXxI/oT=_L:ws!rF{y[99PV$-~#@dhtc3Y*fK!so 4g:PM0)hs0*9)TsHWfN)=d0P_| From: Marc Evans To: freebsd-scsi@freebsd.org Subject: SCSI related system hangs (3.0-SNAP) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Feb 1997 18:30:15 -0500 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi - I have a P133 with a 2940 controller hooked to 3 Seagate Baracuda's (4G). I have loaded 3.0-970124-SNAP onto one fo the drives, and the others I am *attempting* to "newfs" without success. The system as currently configured has worked under BSDI-2.1 previously, and hence hardware is not suspected, though I have retraced SCSI termination. The problem in more detail is that I issue the following: newfs -m 1 -i 1024 /dev/sd1c The controller light is observed flashing dimly for abotu 30 seconds, as does the drive light. After this, both go out and the system is wedged. Nothing short of a reset results in controll being regained. Any suggestions? Please E-MAIL TO ME your response, as I am not a list subscriber. Thanks in advance - Marc =============================================================================== Marc Evans WB1GRH The Destek Networking Group E-Mail: Marc@Destek.NET One Indian Head Plaza URL: http://WWW.Destek.NET/~marc Nashua, NH, USA 03060 MIME-1.0 & Enriched-Text mail accepted 603 594 9630 (V) 598 8864 (F) PGP-2.6 key available upon request WAN & Internet Services PGP-2.6 Fingerprint: 20 7C A2 DB 17 B2 21 80 47 AA B9 CD D9 DE 31 CC The XFree86[tm] Project, Inc. Industry Liason =============================================================================== From owner-freebsd-scsi Thu Feb 6 15:40:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA15396 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 15:40:35 -0800 (PST) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA15388; Thu, 6 Feb 1997 15:40:30 -0800 (PST) Received: from narnia (localhost [127.0.0.1]) by narnia.plutotech.com (8.8.5/8.7.3) with ESMTP id PAA02385; Thu, 6 Feb 1997 15:40:13 -0800 (PST) Message-Id: <199702062340.PAA02385@narnia.plutotech.com> To: Simon Shapiro cc: "John S. Dyson" , freebsd-hackers@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Contigious (spelling?) allocation in kernel In-reply-to: Your message of "Thu, 06 Feb 1997 09:55:40 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Feb 1997 15:40:13 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Hi John S. Dyson; On 06-Feb-97 you wrote: > >> Take a look at contigmalloc() or vm_page_alloc_contig() >> as defined in /sys/vm/vm_page.c. These are almost >> guaranteed NOT to work after the system is fully up. > >Thanx. > >If you (or someone else) please elaborate on the last sentence, >please... Contigmalloc is only guaranteed to work when lots of physical memory is availible to allocate. It works a little bit to try to kick stuff around to make contiguous regions, but to rely on it working all the time to satisfy your allocation would be deadly. >I can re-structure the driver a bit (make it more risky), to >avoid the need for large contigious blocks, but the (obvious) >question is: Does the kernel malloc guarantee that allocations >smaller than (or equal to) a page are in the same page? Yes. A single virtual page always maps to a single physical page. You must use contigmalloc if you cross page boundaries. >Having a page or less, limits the Scatter/Gather operations in >the kernel, for most hardware, to 512 entries (segments). >Under high fragmentation, this can result in 256KB-2MB floating >limit. Actually, it gives you a floating limit between 2MB->2048GB unless you are talking about sending things that are not contiguous in the virtual address space and the granualiry of discontinuity is smaller than a page size. >While not a problem for most applications (mine >included), it is still a limit that is not absolutely necessary. If you need the space, allocate it up front with contigmalloc. Contigmalloc may someday be enhanced to succeed always if physical memory isn't exhausted, but the cost of such an operation under heavy load is extremely high, so you wouldn't want to use it often anyway (especially not if you had even lose real-time constraints). >Any opposing opinions (before I re-code the darn thing :-)? You should talk to John Dyson about anything you want to do to contigmalloc. The VM system is not your standard meat and potatoes and since John has already done some work on enhancing contigmalloc, he's the expert in this area. >BACKGROUND: One of my engineers, who is heavily involved in >Linux SCSI development is strongly opposed to calling malloc on >demand in a device driver. He quotes heavy performance >penalties, and worse; Failure (under heavy load) to obtain the >memory when needed. Malloc will always succeed in FreeBSD if you can sleep and have not run out of physical memory. The problem is that you don't always have a process context to sleep on (say your in an interrupt handler). In the new CAM based architecture, this isn't a problem since instead of sleeping in the driver when you run out of resources for some reason, you simply put the request back into the queue for a retry later. That retry will either use a resource that was freed by another transaction completing or its malloc call will succeed without any waiting involved. This assumes, of course, that you have pre-filled your pool with enough resources for the minimal level of performance so that a failure to malloc every once in a while isn't that big of a deal. Malloc in the FreeBSD kernel is fairly fast too. >Thanx, Simon -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Thu Feb 6 17:07:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA19623 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 17:07:04 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA19616; Thu, 6 Feb 1997 17:07:00 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id JAA06777; Fri, 7 Feb 1997 09:45:47 +1100 Date: Fri, 7 Feb 1997 09:45:47 +1100 From: Bruce Evans Message-Id: <199702062245.JAA06777@godzilla.zeta.org.au> To: Shimon@i-Connect.Net, toor@dyson.iquest.net Subject: Re: Contigious (spelling?) allocation in kernel Cc: freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Take a look at contigmalloc() or vm_page_alloc_contig() >> as defined in /sys/vm/vm_page.c. These are almost >> guaranteed NOT to work after the system is fully up. >... >If you (or someone else) please elaborate on the last sentence, >please... Physical memory gets fragmented after the system has been running for a little while, so the chance of finding N physically contiguous is small if N > 1. >question is: Does the kernel malloc guarantee that allocations >smaller than (or equal to) a page are in the same page? Yes. >BACKGROUND: One of my engineers, who is heavily involved in >Linux SCSI development is strongly opposed to calling malloc on >demand in a device driver. He quotes heavy performance >penalties, and worse; Failure (under heavy load) to obtain the >memory when needed. Good advice. The performance penalties for nonblocking mallocs aren't large under FreeBSD, except when you allocate pages that would be better used for something else, but failure (under not so heavy load) is likely if you attempt to allocate more than a page or two. Bruce From owner-freebsd-scsi Thu Feb 6 17:45:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA21852 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 17:45:14 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA21826 for ; Thu, 6 Feb 1997 17:45:09 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id RAA19592 for ; Thu, 6 Feb 1997 17:21:04 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id CAA14570; Fri, 7 Feb 1997 02:20:54 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id CAA13445; Fri, 7 Feb 1997 02:06:55 +0100 (MET) Message-ID: Date: Fri, 7 Feb 1997 02:06:55 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: amor@geop.ubc.ca (John Amor) Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: HP6020i CDR fails on fixation References: <199702061921.LAA01863@moho.ubc.ca> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702061921.LAA01863@moho.ubc.ca>; from John Amor on Feb 6, 1997 11:21:48 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As John Amor wrote: > I have burned a successfull CD! I moved the CDR down in the box to give > it more cooling it was right under an IDE cdrom. I guess the added air > flow may have made the difference?? Glad to hear. Btw., my today's commit should also cleanup the hassles in the wormclose() code some people used to have. > Is the burning of the fixation as time dependent? Last time I ran the > commands by hand, this time I used the script. All the ioctl's are not time-critical. Time-critical actions are deferred until they actually could be done, and are in tight sequence. The only time-critical operation apart from the successive calls to write(2) itself is to send a SYNCHRONIZE CACHE in time once the write data stream is supposed to be finished. Therefore, this is done from inside wormclose(), so you only need to care to close the device in time after doing all the writes. I figured this was a simple and natural condition. You could also burn multiple tracks before fixating. The fixation only recalculates and writes the new TOC for this session. If you spcifiy the flag (``open next program area''), you can write further sessions later, although that's of little use by now. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Thu Feb 6 17:51:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA22139 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 17:51:03 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA22123 for ; Thu, 6 Feb 1997 17:50:50 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id CAA14944; Fri, 7 Feb 1997 02:50:29 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id CAA13508; Fri, 7 Feb 1997 02:32:11 +0100 (MET) Message-ID: Date: Fri, 7 Feb 1997 02:32:11 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: Shimon@i-Connect.Net (Simon Shapiro) Cc: freebsd-scsi@freebsd.org Subject: Re: Some SCSI Questions... References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Simon Shapiro on Feb 6, 1997 11:41:18 -0800 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Simon Shapiro wrote: > > Is there a particular reason why you're not satisfied with worm(4)? > > What you do not know can (and usually will) hurt you :-) ;-) > The next question is about Yamaha CDR-100 support. > Will I have to provide it? Yes please. Yamaha is known to be very conservative about giving out documentation (NDA and such). This was one of my points to decide against them when the question came for which CD-R to buy (by a time when there was no working support at all for them in FreeBSD, only Peter Dufault's stub driver). Getting the Yamaha to work should not be a major piece of work, judging from Linux' cdwrite. I think it will fit into the existing model, it's just that they use some different mode pages to do the work. However, i was hesitant to play this game without the chance of getting docs. (Mind you, the recipe for the correct write sequence of my Plasmon is almost one page, in 10 pt letters. ;) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Thu Feb 6 19:04:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA25905 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 19:04:16 -0800 (PST) Received: from pooh.cdrom.com (pooh.cdrom.com [204.216.28.222]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA25894 for ; Thu, 6 Feb 1997 19:04:08 -0800 (PST) Received: from www.destek.net (ns2.destek.net [192.156.97.61]) by pooh.cdrom.com (8.7.5/8.7.3) with ESMTP id SAA18312 for ; Thu, 6 Feb 1997 18:16:42 -0800 (PST) Received: from synergy.Destek.Net (root@synergy.destek.net [199.125.115.161]) by www.destek.net (8.8.5/8.8.4) with ESMTP id VAA11129 for ; Thu, 6 Feb 1997 21:17:28 -0500 (EST) Received: from [[UNIX: localhost]] ([[UNIX: localhost]]) by synergy.Destek.Net (8.8.4/8.7.3) with SMTP id VAA20541 for ; Thu, 6 Feb 1997 21:17:25 -0500 (EST) Message-Id: <199702070217.VAA20541@synergy.Destek.Net> X-Authentication-Warning: synergy.Destek.Net: [[UNIX: localhost]] didn't use HELO protocol X-Mailer: exmh version 2.0gamma 1/24/96 X-Uri: X-Face: ">4>,~~_HqlZ,c;!7K60$oLXj\whr`|V-}}cog.gO2Q^/CC[E>,Ez*N0C#)CYY8J\]APjp6 ~)]fwuyFuTXe{7z'Zgt,=+chm*DPh([b^SBn.^jXxI/oT=_L:ws!rF{y[99PV$-~#@dhtc3Y*fK!so 4g:PM0)hs0*9)TsHWfN)=d0P_| From: Marc Evans To: freebsd-scsi@freebsd.com Subject: 3.0-SNAP SCSI (2940) followup Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Feb 1997 21:17:24 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi - Just a followup to my previous message. I have through experimentation determined that the problem I have seen on 3.0-SNAP does not occur under 2.2-GAMMA. I don't know yet what all may have changed in the SCSI code (most best-guessed area of problem), but there does definitely seem to be a bug lurking down there someplace... - Marc =============================================================================== Marc Evans WB1GRH The Destek Networking Group E-Mail: Marc@Destek.NET One Indian Head Plaza URL: http://WWW.Destek.NET/~marc Nashua, NH, USA 03060 MIME-1.0 & Enriched-Text mail accepted 603 594 9630 (V) 598 8864 (F) PGP-2.6 key available upon request WAN & Internet Services PGP-2.6 Fingerprint: 20 7C A2 DB 17 B2 21 80 47 AA B9 CD D9 DE 31 CC The XFree86[tm] Project, Inc. Industry Liason =============================================================================== From owner-freebsd-scsi Thu Feb 6 19:16:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA26794 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 19:16:17 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA26748; Thu, 6 Feb 1997 19:16:07 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id SAA19884 ; Thu, 6 Feb 1997 18:39:06 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA09135; Fri, 7 Feb 1997 13:08:13 +1030 (CST) From: Michael Smith Message-Id: <199702070238.NAA09135@genesis.atrad.adelaide.edu.au> Subject: Re: Contigious (spelling?) allocation in kernel In-Reply-To: from Simon Shapiro at "Feb 6, 97 09:55:40 am" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Fri, 7 Feb 1997 13:08:12 +1030 (CST) Cc: toor@dyson.iquest.net, freebsd-hackers@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro stands accused of saying: > > > Take a look at contigmalloc() or vm_page_alloc_contig() > > as defined in /sys/vm/vm_page.c. These are almost > > guaranteed NOT to work after the system is fully up. > > Thanx. > > If you (or someone else) please elaborate on the last sentence, > please... Er, from my understanding the kva space tends to become fragmented, and your chances of being able to allocate contiguous memory tend to be reduced. > I can re-structure the driver a bit (make it more risky), to > avoid the need for large contigious blocks, but the (obvious) > question is: Does the kernel malloc guarantee that allocations > smaller than (or equal to) a page are in the same page? Can't answer that, sorry. Look at the source 8) > Having a page or less, limits the Scatter/Gather operations in > the kernel, for most hardware, to 512 entries (segments). > Under high fragmentation, this can result in 256KB-2MB floating > limit. While not a problem for most applications (mine > included), it is still a limit that is not absolutely necessary. TBH, a 256K I/O is likely to be bigger than most peripherals can do anything useful with. I would be inclined to say that the overhead of splitting that into seperate transactions is likely to be small compared with the size of the transaction. > BACKGROUND: One of my engineers, who is heavily involved in > Linux SCSI development is strongly opposed to calling malloc on > demand in a device driver. He quotes heavy performance > penalties, and worse; Failure (under heavy load) to obtain the > memory when needed. They're right on the ball; avoid allocating memory on the fly wherever possible. 8) > Thanx, Simon -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-scsi Thu Feb 6 19:35:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA28184 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 19:35:24 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA28178; Thu, 6 Feb 1997 19:35:19 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id TAA20083 ; Thu, 6 Feb 1997 19:35:16 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id UAA15805; Thu, 6 Feb 1997 20:34:41 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199702062036.MAA01871@narnia.plutotech.com> Date: Thu, 06 Feb 1997 18:34:44 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: "Justin T. Gibbs" Subject: Re: Contigious (spelling?) allocation in kernel Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Justin T. Gibbs; On 06-Feb-97 you wrote: ... > Okay, so if you can live with 2MB or less per transaction, you'll have at most > a page worth of SG list per transaction, and you can use regular malloc to pool > them as you like. The aic7xxx driver does this for its SG list already, > allocating a page worth of SG lists each time. I used to have the SG list > maxed out at 256 (the limit of these controllers), but recently dropped it > down to 32 until the 64k limit goes away (17 would be sufficient for anything > that the kernel does, but I wanted it to be a power of 2 for efficient pooling). I have noticed that. This driver (aic7xxx) has been very helpful in writing this beast. I have pretty much adopted most of what you say. Except that we pre-allocate an SG list for every CCB. It works better for this HBA, even if it costs more in memory. I allow the size of the list to be tunable. Which brings me to the next question :-)) How do i pass parameters to a driver at boot time? Similar to the Linux lilo/insmod stuff. ... > You have a couple choices. One is to make another in-kernel process like > the page daemon. Another is to add software interrupt handlers for your > tasks. This can work well if your workload has clean interdependencies. > For example, the CAM SCSI code will add another software interrupt handler that > deals with work provided by the controller's interrupt routine at a lower > priority then the hardware interrupts themselves. This ensures that your > controller interrupt handler is as short as possible (they curently call up > into the mid layer at raised SPL blocking other interrupts) as the current > scheme can be really nasty if you are sharing an interrupt with a device that > requires fast response times (like a Fibre Channel or ethernet card). This is EXACTLY what I am after! For the same reasons. The DPT can handle a cache hit in less than a microsecond. I want to be able to get out of the interrupt routine as fast as possible, and hand the rest of the processing to some other thread. How do I do that? Looks to me as if the software interrupt route is the simplest/best, but what are the semantics for its calling, etc. ? Thanx! Hope I could return these favors one day... Simon From owner-freebsd-scsi Thu Feb 6 20:18:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA01985 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 20:18:27 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA01960; Thu, 6 Feb 1997 20:18:21 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id TAA20108 ; Thu, 6 Feb 1997 19:36:23 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id UAA15807; Thu, 6 Feb 1997 20:34:41 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <32FA657D.446B9B3D@whistle.com> Date: Thu, 06 Feb 1997 18:46:20 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: Julian Elischer Subject: Re: Contigious (spelling?) allocation in kernel Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Julian Elischer; On 06-Feb-97 you wrote: ... > well you could do what the swap daemon does.. it's started from the > kernel.. > it's more a kernel PROCESS than a kernel thread. I really do not care. All I need is something that will allow me to break the execution thread and resume it in a different time. A mechanism, like another interrupt handler, software interrupts, etc. I want to be able to accomplish two things: 1. Return from xxx_scsi_cmd as fast as possible. 2. Return from xxx_intr as fast as possible. 3. Hand over the hardware processing implied by xxx_scsi_cmd to another entity so that this routine does not have to block on inb, outb and such. IOW, I want to de-couple the scsi_cmd from the hardware. 4. Hand over the logical (and error) processing implied by xxx_intr to another entity. IOW, de-couple hardware issues (done in the intr routine) form logic, error processing, strategy and such. Much of this work may appear meaningless on a uniprocessor, but on an SMP system it has many advantages, as it allows partitioning of the workload and running the three layers asynchronously from each other. Three Layers: 1. Accept SCSI command, prepare for execution and queue. 2. a. Submit to hardware b. Receive completion notification form hardware 3. Analyze result, plan response and execute, reply to original caller. Thanx! Simon From owner-freebsd-scsi Thu Feb 6 21:53:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA06776 for freebsd-scsi-outgoing; Thu, 6 Feb 1997 21:53:25 -0800 (PST) Received: from mayu.hal.t.u-tokyo.ac.jp (mayu.hal.t.u-tokyo.ac.jp [133.11.98.131]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA06771 for ; Thu, 6 Feb 1997 21:53:17 -0800 (PST) Received: by mayu.hal.t.u-tokyo.ac.jp (8.6.9+2.4Wb/3.2W5/HAL) id OAA14506; Fri, 7 Feb 1997 14:52:24 +0900 Date: Fri, 7 Feb 1997 14:52:24 +0900 From: Ajith Pasqual Message-Id: <199702070552.OAA14506@mayu.hal.t.u-tokyo.ac.jp> To: scsi@freebsd.org Subject: HELP!! ST32155W - Not detected during probing!! Cc: pasqual@hal.t.u-tokyo.ac.jp Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi!, I've been trying to install FreeBSD 2.1.6 from Walnut Creek CD (For the first time!!). I've a major problem. Probing does not detect my Hard Disk (Seagate ST32155W) when I boot from boot floppy (Floppyless installation failed). Any help would be greatly appreciated. I've tried the 2.2-BETA, 2.2-GAMMA bootfloppies. I get similar results. Seems I'm ignoring some simple things -:( Please enlighten me!! Here are my system configuration and the boot messages I got : Gateway Pentium Pro 200 (AMI BIOS) 32MB RAM with 256KB L2 Cache Adaptec AHA 2940UW PCI SCSI host adapter (Ultra Wide) Seagate ST32155W (Hawk 2XL 2GB Ultra Wide) Matsushita 8X SCSI CDROM CR-506 Matrox Millenium 4MB - PCI card US Robotics Sportster 33.6 PnP modem (ISA) Ensoniq Soundscape VIVO90 PnP Sound Card (with Sound Blaster Emulation) I've partitioned the disk for Win95 (C:) and for FreeBSD (D:). At this momment I cannot have the luxury of FreeBSD in full disk!! During a normal boot SCSI BIOS identifies the SCSI devices correctly : SCSI ID #0 : CDROM CR-506 SCSI ID #15 : Seagate ST32155W Drive C : (80h) Boot Messages : chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 mapreg[20] type 1 addr=0000ffa0 size=0010 ahc0 rev 0 int a irq10 on pci0:11 mapreg[10] type=1 addr=0000fc00 size=0100 mapreg[14] type=0 addr=ffbeb000 size=1000 ahc0: Reading SEEPROM ... done. ahc0: aic7880 Wide Channel, SCSI ID=7, 16 SCB's ahc0: Reseeting Channel A ahc0: Probing Channel A ahc0 waiting for SCSI devices to settle ahc0:A:0 refuses WIDE negotiation. USing 8 bit transfers <*** This message disappeared when I set "Initiate Wide Negotiation" to "no" SCSI Dev. ID ## 0 (CDROM) in SCSI Select **> ahc0: target 0 sysnchronous at 10.0 MHz, offset=0xf (ahc0:0:0) : "MATSHITA CD ROM CR-506 8S05" type 5 removable SCSI 2 cd0(ahc0:0:0): CD-ROM cd present [259826 x 2048 byte records] . . . BIOS Geometrics 0:0104fe3f 0..260=261 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for I've played with various settings in SCSI Select, but I keep getting the same messages. If this information matters : (SCSI Select settings) Host Adapter SCSI ID ..... 7 SCSI Parity Checking Enable Host Adapter SCSI termination Automatic Boot Target ID ....... 15 (This was 0 earlier - but NO change at all!) Initiate WIDE negotiation .. no for SCSI ID #0 Extended BIOS Translation (>1GB) .. Enabled Support for Ultra SCSI speed .. Enable (Earlier it was disabled - default - But no change again!!) In the Visual Configuration Mode : Storage - Disabled ALL except fdc0 Network - Disabled ALL Communication : Enabled ALL PCI : No Conflicts Hope I've included ALL relevant information. (if NOT pls let me know) Thank you very much in advance for your precious time. Regards, Ajith. ------------------------------------------------------------------------------ Ajith Pasqual - Dept of Info. & Comm. Eng., Univ. of Tokyo. Email:pasqual@hal.t.u-tokyo.ac.jp (WWW)http://www.hal.t.u-tokyo.ac.jp/~pasqual/ ------------------------------------------------------------------------------- From owner-freebsd-scsi Fri Feb 7 02:50:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA18708 for freebsd-scsi-outgoing; Fri, 7 Feb 1997 02:50:05 -0800 (PST) Received: from hda.hda.com (ip52-max1-fitch.ziplink.net [199.232.245.52]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA18661 for ; Fri, 7 Feb 1997 02:49:58 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id FAA02287 for scsi@freebsd.org; Fri, 7 Feb 1997 05:45:11 -0500 From: Peter Dufault Message-Id: <199702071045.FAA02287@hda.hda.com> Subject: newer scsi(8) To: scsi@freebsd.org Date: Fri, 7 Feb 1997 05:45:10 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The newer gcc doesn't like my debugging macros. I've removed ftp://freefall.freebsd.org/incoming/scsinew.tgz and replaced it with ftp://freefall.freebsd.org/incoming/scsinew2.tgz Peter -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-scsi Fri Feb 7 05:45:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA26520 for freebsd-scsi-outgoing; Fri, 7 Feb 1997 05:45:17 -0800 (PST) Received: from mercury.ukc.ac.uk (mercury.ukc.ac.uk [129.12.21.10]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA26510 for ; Fri, 7 Feb 1997 05:45:09 -0800 (PST) Received: from crane.ukc.ac.uk by mercury.ukc.ac.uk with SMTP (PP); Fri, 7 Feb 1997 13:44:44 +0000 Received: from localhost by crane.ukc.ac.uk (SMI-8.6/UKC-2.14) id NAA06357; Fri, 7 Feb 1997 13:44:38 GMT Date: Fri, 7 Feb 1997 13:44:38 +0000 (GMT) From: "K.R.Marshall" X-Sender: krm2@crane To: scsi@freebsd.org Subject: Nakamichi 4-disk changers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I don't know if anyone is interested in this, but I've recently purchased a 7-drive tower full of 4-disk 8x Nakamichi CD-ROM changers. These units each take up the space of a standard 5 1/4" half slot, but are 4-disk changers so you can get effectively 28 disks into one normal tower unit. Anyhow, I had to add the following lines to scsiconf.c - I hope this diff is useable - I'm not too experienced at such things. It is relative to 3.0-SNAP of 18/01 but it should be easy enough to adapt for other releases too I think. This server won't go online for a couple of weeks so if anyone wants me to test out CD-ROM changer code I'll be happy to oblige. The drives are connected to an Adaptec 2940 SCSI II card. The machine is an Opus Pentium P75, 24Mb RAM, with an SMC 8216T ethernet card, 1.2 Gb IDE hard disk on one channel and an 8x IDE MATSHITA CD-ROM drive as primary on the other IDE channel. The hard disk is partitioned into to 600Mb chunks, the idea being I can run an experimental 3.0 system on one chunk and a more stable 2.2 system on the other - I'm waiting for 2.2R for the second chunk. Access to the CDs will be via NFS and Samba as we have a mixture of older PCs running PC-NFS and newer machines running NT 4.0. I already have two networked CD-ROM servers running 2.1R with this kind of access so I know what I'm doing (famous last words...). 8<----------------- cut here ------------------------------------------ *** scsiconf.c Tue Feb 4 17:55:20 1997 --- scsiconf.old Fri Feb 7 12:10:23 1997 *************** *** 328,337 **** "cd", SC_MORE_LUS }, { - T_READONLY, T_READONLY, T_REMOV, "NAKAMICH", "MJ-4*", "*", - "cd", SC_MORE_LUS - }, - { T_READONLY, T_READONLY, T_REMOV, "CHINON", "CD-ROM CDS-535","*", "cd", SC_ONE_LU }, --- 328,333 ---- # diff -c scsiconf.old scsiconf.c *** scsiconf.old Fri Feb 7 12:10:23 1997 --- scsiconf.c Tue Feb 4 17:55:20 1997 *************** *** 328,333 **** --- 328,337 ---- "cd", SC_MORE_LUS }, { + T_READONLY, T_READONLY, T_REMOV, "NAKAMICH", "MJ-4*", "*", + "cd", SC_MORE_LUS + }, + { T_READONLY, T_READONLY, T_REMOV, "CHINON", "CD-ROM CDS-535","*", "cd", SC_ONE_LU }, 8<------------------ cut here --------------------------------- Keith. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Mummy was an asteroid, Daddy was a | Keith Marshall small, non-stick kitchen utensil..." | Computing Officer, Templeman Library - Quiet Sun, 1975 | University of Kent at Canterbury. From owner-freebsd-scsi Fri Feb 7 06:06:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA28034 for freebsd-scsi-outgoing; Fri, 7 Feb 1997 06:06:05 -0800 (PST) Received: from mercury.ukc.ac.uk (mercury.ukc.ac.uk [129.12.21.10]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA28019 for ; Fri, 7 Feb 1997 06:05:57 -0800 (PST) Received: from crane.ukc.ac.uk by mercury.ukc.ac.uk with SMTP (PP); Fri, 7 Feb 1997 14:05:02 +0000 Received: from localhost by crane.ukc.ac.uk (SMI-8.6/UKC-2.14) id OAA08475; Fri, 7 Feb 1997 14:04:56 GMT Date: Fri, 7 Feb 1997 14:04:56 +0000 (GMT) From: "K.R.Marshall" X-Sender: krm2@crane To: scsi@freebsd.org Subject: Re: Nakamichi 4-disk changers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 7 Feb 1997, K.R.Marshall wrote: *sigh* I hate cut-and-paste ;) - corrected diff: > > 8<----------------- cut here ------------------------------------------ > *** scsiconf.old Fri Feb 7 12:10:23 1997 > --- scsiconf.c Tue Feb 4 17:55:20 1997 > *************** > *** 328,333 **** > --- 328,337 ---- > "cd", SC_MORE_LUS > }, > { > + T_READONLY, T_READONLY, T_REMOV, "NAKAMICH", "MJ-4*", "*", > + "cd", SC_MORE_LUS > + }, > + { > T_READONLY, T_READONLY, T_REMOV, "CHINON", "CD-ROM > CDS-535","*", > "cd", SC_ONE_LU > }, > 8<------------------ cut here --------------------------------- > Sorry! Keith. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Mummy was an asteroid, Daddy was a | Keith Marshall small, non-stick kitchen utensil..." | Computing Officer, Templeman Library - Quiet Sun, 1975 | University of Kent at Canterbury. From owner-freebsd-scsi Fri Feb 7 09:14:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA07502 for freebsd-scsi-outgoing; Fri, 7 Feb 1997 09:14:18 -0800 (PST) Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA07496 for ; Fri, 7 Feb 1997 09:14:14 -0800 (PST) Received: from seabass.progroup.com (seabass.progroup.com [206.24.122.1]) by seabass.progroup.com (8.7.5/8.7.3) with SMTP id JAA25199; Fri, 7 Feb 1997 09:13:14 -0800 (PST) Message-ID: <32FB62AA.62319AC4@progroup.com> Date: Fri, 07 Feb 1997 09:13:14 -0800 From: Craig Shaver Organization: Productivity Group, Inc. X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: "" CC: scsi@freebsd.org Subject: Re: ST32155W - Not detected during probing!! HELP!! References: <199702070515.VAA28054@seabass.progroup.com> <199702070550.OAA07467@madoka.hal.t.u-tokyo.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Thu, 6 Feb 1997 21:15:28 -0800 (PST), "Craig Shaver" said: > > >> I've partitioned the disk for Win95 (C:) and for FreeBSD (D:). At this momment > > > How did you do the partition? Did you use some utility on the controller? > > Using fdsik. (1 Primary DOS and the other Extended - I plan to delete it for > freebsd but I could not go that far -:() > The question is "which fdisk did you use?"? Did you boot dos, and then use the dos fdisk program, or did you use a utility from the 2940 bios? I.e., did dos see the disk? (probably did since the controller is accessed through the bios from dos, right?) > > > Hmmmm, first thing I would do, would be to set the target on the seagate > > to id#0, and the target on the cdrom to id#6. Is this cdrom a wide device? > > Or do you have the connector to do wide->scsi II? I have a 2940uw on the > > shelf, and it can do scsi 2 and wide on different cables. hmmmmm. > > No!! It is not wide. When I boot for the first time it gave that message : > Cannot initaie WIDE negotiation. So I set the WIDE negotiation to "no" > When I boot from 2.2-GAMMA it displays the message that internal50 and > internal68 cable is present. (I guess this is for non wide and wide) > > > ok, anyway, the reason I would move the id# to 0 would be because I have > > run into problems with the ncr driver. In spots the ncr driver does a > > target mask using hex 0x07, instead of hex 0x0f. That meant that targets > > 8 - 15 were unusable. I am guessing here. > Can you detail the physical setup? What cables are attached and how? What jumpers do you have on the hard disk? ------------------------------------------------------------------------------ > Ajith Pasqual - Dept of Info. & Comm. Eng., Univ. of Tokyo. > Email:pasqual@hal.t.u-tokyo.ac.jp (WWW)http://www.hal.t.u-tokyo.ac.jp/~pasqual/ > ------------------------------------------------------------------------------- -- Craig Shaver (craig@progroup.com) (415)390-0654 Productivity Group POB 60458 Sunnyvale, CA 94088 From owner-freebsd-scsi Fri Feb 7 12:17:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA16989 for freebsd-scsi-outgoing; Fri, 7 Feb 1997 12:17:20 -0800 (PST) Received: from gate.fidata.fi (gate.fidata.fi [193.64.102.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA16984 for ; Fri, 7 Feb 1997 12:17:16 -0800 (PST) Received: from zeta.fidata.fi (zeta.fidata.fi [193.64.102.5]) by gate.fidata.fi (8.8.3/8.8.0) with ESMTP id WAA16155 for ; Fri, 7 Feb 1997 22:17:10 +0200 (EET) Received: (from tomppa@localhost) by zeta.fidata.fi (8.8.5/8.8.0) id WAA20779; Fri, 7 Feb 1997 22:17:09 +0200 (EET) Date: Fri, 7 Feb 1997 22:17:09 +0200 (EET) Message-Id: <199702072017.WAA20779@zeta.fidata.fi> From: Tomi Vainio MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-scsi@freebsd.org Subject: Re: Some SCSI Questions... In-Reply-To: References: Reply-To: tomppa@fidata.fi Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J. Wunsch writes: > As Simon Shapiro wrote: > > > The next question is about Yamaha CDR-100 support. > > Will I have to provide it? > > Yes please. Yamaha is known to be very conservative about giving out > documentation (NDA and such). This was one of my points to decide > against them when the question came for which CD-R to buy (by a time > when there was no working support at all for them in FreeBSD, only > Peter Dufault's stub driver). > You should check out cdrecord software that works under Solaris. Author of this software also has many SCSI command reference manuals including Yamaha CDR-100/102. Tomppa -- Tomi Vainio, Fimeko-Data Oy Phone: +358 (0)9 4582421 Mail: tomppa@iki.fi tomppa@fidata.fi Telefax: +358 (0)9 4582425 From owner-freebsd-scsi Fri Feb 7 12:41:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA18348 for freebsd-scsi-outgoing; Fri, 7 Feb 1997 12:41:32 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA18325; Fri, 7 Feb 1997 12:41:26 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id NAA20750; Fri, 7 Feb 1997 13:40:32 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199702070238.NAA09135@genesis.atrad.adelaide.edu.au> Date: Fri, 07 Feb 1997 12:24:52 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: Michael Smith Subject: Re: Contigious (spelling?) allocation in kernel Cc: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org, toor@dyson.iquest.net Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Michael Smith; On 07-Feb-97 you wrote: ... > Er, from my understanding the kva space tends to become fragmented, and > your chances of being able to allocate contiguous memory tend to > be reduced. So failure is defined here as ``refusal to provide resource requested'', but not ``crash the system or other unexpected result''. This we can live with. > > I can re-structure the driver a bit (make it more risky), to > > avoid the need for large contigious blocks, but the (obvious) > > question is: Does the kernel malloc guarantee that allocations > > smaller than (or equal to) a page are in the same page? > > Can't answer that, sorry. Look at the source 8) I think the answer is yes. > > Having a page or less, limits the Scatter/Gather operations in > > the kernel, for most hardware, to 512 entries (segments). > > Under high fragmentation, this can result in 256KB-2MB floating > > limit. While not a problem for most applications (mine > > included), it is still a limit that is not absolutely necessary. > > TBH, a 256K I/O is likely to be bigger than most peripherals can do > anything useful with. I would be inclined to say that the > overhead of splitting that into seperate transactions is likely > to be small compared with the size of the transaction. It all depends on the device. Some high speed tapes, printers, CD Writers, can use large blocks. Most O/S's do not know what to do with large blocks, though... > > BACKGROUND: One of my engineers, who is heavily involved in > > Linux SCSI development is strongly opposed to calling malloc on > > demand in a device driver. He quotes heavy performance > > penalties, and worse; Failure (under heavy load) to obtain the > > memory when needed. > > They're right on the ball; avoid allocating memory on the fly wherever > possible. 8) I know, I know... :-) thanx, Simon From owner-freebsd-scsi Fri Feb 7 13:35:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA21133 for freebsd-scsi-outgoing; Fri, 7 Feb 1997 13:35:10 -0800 (PST) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA21124 for ; Fri, 7 Feb 1997 13:35:02 -0800 (PST) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.4/8.7.3) id NAA29174; Fri, 7 Feb 1997 13:34:48 -0800 (PST) Date: Fri, 7 Feb 1997 13:34:48 -0800 (PST) Message-Id: <199702072134.NAA29174@vader.cs.berkeley.edu> To: pasqual@hal.t.u-tokyo.ac.jp CC: scsi@freebsd.org, pasqual@hal.t.u-tokyo.ac.jp In-reply-to: <199702070552.OAA14506@mayu.hal.t.u-tokyo.ac.jp> (message from Ajith Pasqual on Fri, 7 Feb 1997 14:52:24 +0900) Subject: Re: HELP!! ST32155W - Not detected during probing!! From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * SCSI ID #0 : CDROM CR-506 * SCSI ID #15 : Seagate ST32155W Drive C : (80h) * BIOS Geometrics * 0:0104fe3f 0..260=261 cylinders, 0..254=255 heads, 1..63=63 sectors * 0 accounted for It's getting the geometry of your drive correctly from the BIOS. * Boot Target ID ....... 15 (This was 0 earlier - but NO change at all!) You mean you had the Hawk it ID 0 and boot target ID 0, or Hawk at 15 and boot target ID 0? If you haven't tried actually putting the Hawk at 0, please try that. I have installed 2.1.5 successfully on a very similar configuration (2940UW, wide Hawk 1GB). So I don't see why the SCSI driver would be a problem. Satoshi From owner-freebsd-scsi Fri Feb 7 13:40:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA21427 for freebsd-scsi-outgoing; Fri, 7 Feb 1997 13:40:34 -0800 (PST) Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA21420 for ; Fri, 7 Feb 1997 13:40:32 -0800 (PST) Received: from bitch.Melmac.org (ulf@Bitch.Melmac.org [207.90.181.42]) by DNS.Lamb.net (8.8.5/20.74.3.14) with ESMTP id NAA16716; Fri, 7 Feb 1997 13:40:41 -0800 (PST) Received: (from ulf@localhost) by bitch.Melmac.org (8.8.5/8.7.6) id NAA26280; Fri, 7 Feb 1997 13:40:24 -0800 (PST) From: Ulf Zimmermann Message-Id: <199702072140.NAA26280@bitch.Melmac.org> Subject: Re: HELP!! ST32155W - Not detected during probing!! In-Reply-To: <199702072134.NAA29174@vader.cs.berkeley.edu> from Satoshi Asami at "Feb 7, 97 01:34:48 pm" To: asami@vader.cs.berkeley.edu (Satoshi Asami) Date: Fri, 7 Feb 1997 13:40:24 -0800 (PST) Cc: pasqual@hal.t.u-tokyo.ac.jp, scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > * SCSI ID #0 : CDROM CR-506 > * SCSI ID #15 : Seagate ST32155W Drive C : (80h) > > * BIOS Geometrics > * 0:0104fe3f 0..260=261 cylinders, 0..254=255 heads, 1..63=63 sectors > * 0 accounted for > > It's getting the geometry of your drive correctly from the BIOS. > > * Boot Target ID ....... 15 (This was 0 earlier - but NO change at all!) > > You mean you had the Hawk it ID 0 and boot target ID 0, or Hawk at 15 > and boot target ID 0? If you haven't tried actually putting the Hawk > at 0, please try that. > > I have installed 2.1.5 successfully on a very similar configuration > (2940UW, wide Hawk 1GB). So I don't see why the SCSI driver would be > a problem. > > Satoshi > Aehm, the Adaptec is normaly on ID 7 for narrow and ID 15 for wide. You can't put the disk on that ID. Ulf. -------------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net From owner-freebsd-scsi Fri Feb 7 13:56:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA22346 for freebsd-scsi-outgoing; Fri, 7 Feb 1997 13:56:53 -0800 (PST) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA22333 for ; Fri, 7 Feb 1997 13:56:50 -0800 (PST) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.4/8.7.3) id NAA29244; Fri, 7 Feb 1997 13:56:07 -0800 (PST) Date: Fri, 7 Feb 1997 13:56:07 -0800 (PST) Message-Id: <199702072156.NAA29244@vader.cs.berkeley.edu> To: ulf@Alameda.net CC: pasqual@hal.t.u-tokyo.ac.jp, scsi@freebsd.org In-reply-to: <199702072140.NAA26280@bitch.Melmac.org> (message from Ulf Zimmermann on Fri, 7 Feb 1997 13:40:24 -0800 (PST)) Subject: Re: HELP!! ST32155W - Not detected during probing!! From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Aehm, the Adaptec is normaly on ID 7 for narrow and ID 15 for wide. ^^^^^^^^^^^^^^ I'm sorry, but that can't possibly be true. How is a wide adapter supposed to talk to narrow devices then? (Hint: narrow devices won't even see data lines 8-15, see http://scitexdv.com:8080/SCSI2/ for more.) Satoshi From owner-freebsd-scsi Fri Feb 7 23:37:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA28595 for freebsd-scsi-outgoing; Fri, 7 Feb 1997 23:37:07 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA28590 for ; Fri, 7 Feb 1997 23:37:05 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id AAA26864; Sat, 8 Feb 1997 00:35:35 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 07 Feb 1997 22:39:03 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: (Joerg Wunsch) Subject: Re: Some SCSI Questions... Cc: freebsd-scsi@freebsd.org, (J Wunsch) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi J Wunsch; On 07-Feb-97 you wrote: > As Simon Shapiro wrote: > > > > Is there a particular reason why you're not satisfied with worm(4)? > > > > What you do not know can (and usually will) hurt you :-) > > ;-) > > > The next question is about Yamaha CDR-100 support. > > Will I have to provide it? > > Yes please. Yamaha is known to be very conservative about giving out > documentation (NDA and such). This was one of my points to decide > against them when the question came for which CD-R to buy (by a time > when there was no working support at all for them in FreeBSD, only > Peter Dufault's stub driver). > > Getting the Yamaha to work should not be a major piece of work, > judging from Linux' cdwrite. I think it will fit into the existing > model, it's just that they use some different mode pages to do the > work. However, i was hesitant to play this game without the chance of > getting docs. (Mind you, the recipe for the correct write sequence of > my Plasmon is almost one page, in 10 pt letters. ;) I received the documentation without much problem. Have to find where I stuffed it. Looked easy enough. Real soon any day now :-) Simon From owner-freebsd-scsi Sat Feb 8 03:21:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA06502 for freebsd-scsi-outgoing; Sat, 8 Feb 1997 03:21:44 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA06497 for ; Sat, 8 Feb 1997 03:21:41 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA24566; Sat, 8 Feb 1997 12:21:37 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id MAA25737; Sat, 8 Feb 1997 12:19:37 +0100 (MET) Message-ID: Date: Sat, 8 Feb 1997 12:19:37 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: K.R.Marshall@ukc.ac.uk (K.R.Marshall) Cc: scsi@freebsd.org Subject: Re: Nakamichi 4-disk changers References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from K.R.Marshall on Feb 7, 1997 13:44:38 +0000 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As K.R.Marshall wrote: > Anyhow, I had to add the following lines to scsiconf.c - I hope this diff > is useable - I'm not too experienced at such things. It is relative to > 3.0-SNAP of 18/01 but it should be easy enough to adapt for other releases > too I think. Thanks, i'll include it. > This server won't go online for a couple of weeks so if anyone wants me to > test out CD-ROM changer code I'll be happy to oblige. I've got a Nakamichi 7-disk changer here for testing. The biggest problem i found (after fixing the ``Logical unit is in the process of becoming ready'' problem) is that the drives are likely to go thrashing on concurrent access, since the kernel doesn't lock one medium in a device for long enough, so the drives will finally be very busy constantly swapping their media. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sat Feb 8 03:50:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA07286 for freebsd-scsi-outgoing; Sat, 8 Feb 1997 03:50:41 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA07274 for ; Sat, 8 Feb 1997 03:50:36 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA24857 for freebsd-scsi@freebsd.org; Sat, 8 Feb 1997 12:50:35 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id MAA25803; Sat, 8 Feb 1997 12:38:48 +0100 (MET) Message-ID: Date: Sat, 8 Feb 1997 12:38:48 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@freebsd.org Subject: Re: Some SCSI Questions... References: <199702072017.WAA20779@zeta.fidata.fi> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702072017.WAA20779@zeta.fidata.fi>; from Tomi Vainio on Feb 7, 1997 22:17:09 +0200 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Tomi Vainio wrote: > You should check out cdrecord software that works under Solaris. > Author of this software also has many SCSI command reference manuals > including Yamaha CDR-100/102. Where could i find it? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sat Feb 8 05:46:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA13045 for freebsd-scsi-outgoing; Sat, 8 Feb 1997 05:46:36 -0800 (PST) Received: from freebee.tu-graz.ac.at (root@freebee.tu-graz.ac.at [129.27.193.128]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA13040 for ; Sat, 8 Feb 1997 05:46:24 -0800 (PST) Received: from dwarf.tu-graz.ac.at (isdn034.tu-graz.ac.at [129.27.240.34]) by freebee.tu-graz.ac.at (8.6.11/8.6.9) with ESMTP id OAA02778 for ; Sat, 8 Feb 1997 14:46:12 +0100 Received: (from rmike@localhost) by dwarf.tu-graz.ac.at (8.7.5/8.7.3) id KAA00293; Sat, 8 Feb 1997 10:41:57 +0100 (MET) Date: Sat, 8 Feb 1997 10:41:55 +0100 (MET) From: Michael Ranner Reply-To: rmike@sbox.tu-graz.ac.at To: freebsd-scsi@freebsd.org Subject: AHA2920, TMC1830 - need help - need PAO (pccard-test) source! Message-ID: Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I need some source excerpts from the PAO distribution to make it easier for me to port the Linux Future Domain SCSI driver code to FreeBSD, beacuse I like to run my Adaptec 2920 with FreeBSD. I have ported the whole code, but I have problems with xxx_scsi_cmd and xxx_intr, beacause I have done no work before on SCSI for FreeBSD. I had contact with Hosokawa Tatsumi, and he told me that I should take a look on PAO (http:/www.jp.freebsd.org/PAO), because there is a driver for the TMC1830 chip. It would be nice, if someone can tell me, where I can find the source for PAO, or which person I should contact! Thanks, /\/\ike /\/\ichael Ranner - rmike@sbox.tu-graz.ac.at http://www.sbox.tu.graz.ac.at/home/rmike/ --- end of message - non-sense follows --- ________ .' `. / \ |_____ _____| (_____><_____) \ /\ / \ oo / Grey-type ASCII encounter ... \ __ / `----' From owner-freebsd-scsi Sat Feb 8 05:50:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA13183 for freebsd-scsi-outgoing; Sat, 8 Feb 1997 05:50:51 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA13178 for ; Sat, 8 Feb 1997 05:50:49 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA26996; Sat, 8 Feb 1997 14:50:40 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id OAA26208; Sat, 8 Feb 1997 14:23:38 +0100 (MET) Message-ID: Date: Sat, 8 Feb 1997 14:23:38 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: dufault@hda.com (Peter Dufault) Cc: scsi@FreeBSD.ORG Subject: Re: newer scsi(8) References: <199702071045.FAA02287@hda.hda.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702071045.FAA02287@hda.hda.com>; from Peter Dufault on Feb 7, 1997 05:45:10 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Peter Dufault wrote: > ftp://freefall.freebsd.org/incoming/scsinew2.tgz I moved it to ftp://freefall.freebsd.org/pub/dufault/scsinew2.tgz. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sat Feb 8 13:07:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA29644 for freebsd-scsi-outgoing; Sat, 8 Feb 1997 13:07:40 -0800 (PST) Received: from caliban.dihelix.com (caliban.mrtc.org [199.4.33.251]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA29626 for ; Sat, 8 Feb 1997 13:07:16 -0800 (PST) Received: (from langfod@localhost) by caliban.dihelix.com (8.8.4/8.8.3) id LAA10146 for scsi@freebsd.org; Sat, 8 Feb 1997 11:09:54 -1000 (HST) Message-Id: <199702082109.LAA10146@caliban.dihelix.com> Subject: how to use tape changer ch0 To: scsi@freebsd.org Date: Sat, 8 Feb 1997 11:09:54 -1000 (HST) From: "David Langford" X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is their any documention about how one uses the tape changer device ch0? I have a Seagate/Conner/Archive 4586NP that I would like to get working with Amanda. Shows as ether st0 or ch0 but never both. It works great as st0 if I feel like manully flipping through the tapes. I would like to get it working for automated backups but I cant seem to figure out how one would go about using the ch0 driver. Thanks, David Langford langfod@dihelix.com From owner-freebsd-scsi Sat Feb 8 15:21:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA06680 for freebsd-scsi-outgoing; Sat, 8 Feb 1997 15:21:38 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA06544 for ; Sat, 8 Feb 1997 15:19:21 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA08111; Sun, 9 Feb 1997 00:18:53 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id XAA29672; Sat, 8 Feb 1997 23:52:02 +0100 (MET) Message-ID: Date: Sat, 8 Feb 1997 23:52:02 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: langfod@dihelix.com (David Langford) Cc: scsi@freebsd.org Subject: Re: how to use tape changer ch0 References: <199702082109.LAA10146@caliban.dihelix.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702082109.LAA10146@caliban.dihelix.com>; from David Langford on Feb 8, 1997 11:09:54 -1000 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As David Langford wrote: > Is their any documention about how one uses the tape changer > device ch0? There's a new changer driver submitted by Jason Thorpe which includes a control program. It's in PR # kern/1201. Justin was going to deal with it, but later got a little busy in more important tasks. Perhaps we should import the submission now into the mainstream code. -- 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. ;-)