From owner-freebsd-scsi Sun Aug 25 13:21:23 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA01879 for freebsd-scsi-outgoing; Sun, 25 Aug 1996 13:21:23 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA01852 for ; Sun, 25 Aug 1996 13:21:18 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id KAA25482 for ; Sun, 25 Aug 1996 10:25:18 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id TAA32674 for ; Sun, 25 Aug 1996 19:14:26 +0200 Received: by uni4nn.iaf.nl with UUCP id AA12842 (5.67b/IDA-1.5 for freebsd-scsi@freebsd.org); Sun, 25 Aug 1996 19:13:59 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA22992 (5.67b/IDA-1.5 for freebsd-scsi@freebsd.org); Sun, 25 Aug 1996 19:08:01 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.12) id QAA08622 for freebsd-scsi@freebsd.org; Sun, 25 Aug 1996 16:42:10 +0200 From: Wilko Bulte Message-Id: <199608251442.QAA08622@yedi.iaf.nl> Subject: donating Pioneer WORM? To: freebsd-scsi@FreeBSD.ORG (FreeBSD SCSI hackers) Date: Sun, 25 Aug 1996 16:42:09 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi there Is there anybody out there interested in owning a _real_ SCSI WORM drive? So, not a CD-R but a 5.25" affair that uses the cartridge type media. It's a Pioneer BTW. I bought it once in the hope it was a MO type drive, but alas it turned out to be a WORM, Wilko _ ____________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------- From owner-freebsd-scsi Sun Aug 25 13:22:50 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA02261 for freebsd-scsi-outgoing; Sun, 25 Aug 1996 13:22:50 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA02132 for ; Sun, 25 Aug 1996 13:22:25 -0700 (PDT) Received: from jdowdal.erols.com (someone@jdowdal.erols.com [207.96.124.56]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id JAA25369 for ; Sun, 25 Aug 1996 09:27:08 -0700 (PDT) Received: from localhost (jdowdal@localhost) by jdowdal.erols.com (8.7.5/8.6.12) with SMTP id MAA29843; Sun, 25 Aug 1996 12:24:30 -0400 (EDT) X-Authentication-Warning: jdowdal.erols.com: jdowdal owned process doing -bs Date: Sun, 25 Aug 1996 12:24:29 -0400 (EDT) From: John Dowdal To: Torbjorn Granlund cc: scsi@FreeBSD.ORG Subject: Re: Booting from sd0 when wd0 is also present In-Reply-To: <199608232316.BAA24325@insanus.matematik.su.se> 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 Sat, 24 Aug 1996, Torbjorn Granlund wrote: > I got a cheap IDE drive for use as a DOS/Windoze disk. > Thus, I can use the entire SCSI disk for FreeBSD. > > Unfortunately, this makes autoboot fail, with a message that reads something > like "Unable to change root to sd1". The SCSI drive is, of course, sd0. > But it seems that the FreeBSD boot loader incorrectly counts wd0 as if it > were the first SCSI device in this case. > > To me, this seems like a bug. But maybe it is a feature...? Is there a > workaround (less get a dummy SCSI disk with a lower SCSI id :-) ? > > I can get things to work in the way indicated by the text early in the boot > process, but such a manual boot method is not acceptable in the long run. > > I am using FreeBSD 2.1 and am now moving to 2.1.5. This problem occured for me with 2.0.5, I beleive. I solved it as follows: 1) Remove the IDE disk from the BIOS config (or physically remove the disk if your BIOS runs on an automatic transmission) 2) Boot your system. Since the SCSI disk is the only one available, it will boot correctly. 3) Look at the man page for 'sd'. You will want to put a line like: disk sd1 target 6 lun 0 in your kernel config, and rebuild and install the kernel. 4) Turn on IDE disk again. This will simply "hardcode" your SCSI disk as sd1 (change the target # to the real SCSI ID of the disk). When the boot code looks for root on /dev/sd1a, it will find it and not panic :). This would give you your "dummie" sd0 without having to sacrifice another drive. John From owner-freebsd-scsi Sun Aug 25 17:09:17 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA26900 for freebsd-scsi-outgoing; Sun, 25 Aug 1996 17:09:17 -0700 (PDT) Received: from xochi.tezcat.com (ray@xochi.tezcat.com [204.128.247.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA26889 for ; Sun, 25 Aug 1996 17:09:14 -0700 (PDT) Received: (from ray@localhost) by xochi.tezcat.com (Local/tezcat-pb-patch) id TAA15083; Sun, 25 Aug 1996 19:09:07 -0500 (CDT) Date: Sun, 25 Aug 1996 19:09:07 -0500 (CDT) From: Rahim Azizarab To: Wilko Bulte cc: FreeBSD SCSI hackers Subject: Re: donating Pioneer WORM? In-Reply-To: <199608251442.QAA08622@yedi.iaf.nl> 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 I have one these beasts , it is the wintage of 1986 or so, I tried installing it it messed up my video. On Sun, 25 Aug 1996, Wilko Bulte wrote: > Date: Sun, 25 Aug 1996 16:42:09 +0200 (MET DST) > From: Wilko Bulte > To: FreeBSD SCSI hackers > Subject: donating Pioneer WORM? > > Hi there > > Is there anybody out there interested in owning a _real_ SCSI WORM > drive? So, not a CD-R but a 5.25" affair that uses the cartridge > type media. It's a Pioneer BTW. > > I bought it once in the hope it was a MO type drive, but alas it > turned out to be a WORM, > > Wilko > _ ____________________________________________________________________ > | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl > |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands > -------------------------------------------------------------------------- > **************************************************************************** .--. __ .--------- Rahim Azizarab / / \( )/ ---- 1925 S. 3rd Ave //// ' \/ ` --- Maywood, IL 60153 // / / : :-- 708-344-6994 // //..\\ =UU====UU= ray@tezcat.com http://www.tezcat.com/users/ray *************************************************************************** From owner-freebsd-scsi Mon Aug 26 02:47:01 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA00521 for freebsd-scsi-outgoing; Mon, 26 Aug 1996 02:47:01 -0700 (PDT) Received: from iaehv.IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA00515; Mon, 26 Aug 1996 02:46:56 -0700 (PDT) Received: from LOCAL (wjw@localhost) by iaehv.IAEhv.nl (8.6.13/1.63); pid 7273 on Mon, 26 Aug 1996 11:46:52 +0200; id LAA07273 efrom: wjw; eto: UNKOWN From: wjw@IAEhv.nl (Willem Jan Withagen) Message-Id: <199608260946.LAA07273@iaehv.IAEhv.nl> Subject: SCSI disks To: hardware@freebsd.org Date: Mon, 26 Aug 1996 11:46:52 +0200 (MET DST) Cc: scsi@freebsd.org, admin@IAEhv.nl X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Until recently we as an ISP were using Micropolis disk with pleasure. But since several 4.3Gb started crashing, we've changed our view. So I'm now looking for new disks. I've got 2 offerings: Seagate Barracuda 4.3 GB Quantum XP34300S The need to run on FreeBSD 2.0.5 and up. Long agood I tested the quantum with an NCR 53810 and an Adaptec 1542B and in both case it did not seem to work. Now things might have changed, but I'm interrested in the opinion of other fellow FreeBSD-ers. Please also respond in personal Email, since I read may FreeBSD lists but not all of them. Thanx, WjW -- Internet Access Eindhoven BV., voice: +31-40-2438330, data: +31-40-2439436 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. From owner-freebsd-scsi Mon Aug 26 12:14:53 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA07081 for freebsd-scsi-outgoing; Mon, 26 Aug 1996 12:14:53 -0700 (PDT) Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA07072; Mon, 26 Aug 1996 12:14:49 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-38.slip.Uni-Koeln.DE) by FileServ1.MI.Uni-Koeln.DE with SMTP id AA14905 (5.67b/IDA-1.5); Mon, 26 Aug 1996 21:14:45 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA00920; Mon, 26 Aug 1996 21:09:38 +0200 (MET DST) Date: Mon, 26 Aug 1996 21:09:38 +0200 (MET DST) Message-Id: <199608261909.VAA00920@x14.mi.uni-koeln.de> From: Stefan Esser To: wjw@IAEhv.nl (Willem Jan Withagen) Cc: hardware@freebsd.org, scsi@freebsd.org, admin@IAEhv.nl Subject: Re: SCSI disks In-Reply-To: <199608260946.LAA07273@iaehv.IAEhv.nl> References: <199608260946.LAA07273@iaehv.IAEhv.nl> Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Willem Jan Withagen writes: > > Hi, > > Until recently we as an ISP were using Micropolis disk with pleasure. > But since several 4.3Gb started crashing, we've changed our view. > > So I'm now looking for new disks. I've got 2 offerings: > Seagate Barracuda 4.3 GB > Quantum XP34300S > The need to run on FreeBSD 2.0.5 and up. > Long agood I tested the quantum with an NCR 53810 and an Adaptec 1542B > and in both case it did not seem to work. Now things might have changed, but Hmmm, that's surprising, since my current development system uses a Quantum Atlas (though its the XP32150S, the 2GB version). This drive worked with the NCR driver of Spring 1995 at least, when I first tested it. I'm quite sure that the Adaptec 1542 supported it as well, since it is hard to find a device that doesn't work on the Adpatec, and the Atlas is really well designed (IMHO). The Quantum Grand-Prix (XP34301S) is a different beast. It has got bad press because of many failed (or DOA) drives, and it is noisy and significantly slower than the Atlas, though both are 7200RPM drives. You may also want to have a look at the IBM DHFS series, which is also very fast and AFAIK reliable. Can't comment on recent Seagate drives. Regards, STefan From owner-freebsd-scsi Mon Aug 26 13:23:23 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13394 for freebsd-scsi-outgoing; Mon, 26 Aug 1996 13:23:23 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA13389; Mon, 26 Aug 1996 13:23:20 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.7.5/8.7.5) with SMTP id PAA29629; Mon, 26 Aug 1996 15:23:11 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Mon, 26 Aug 96 15:23 CDT Received: (from karl@localhost) by Jupiter.mcs.net (8.7.5/8.7.5) id PAA15285; Mon, 26 Aug 1996 15:22:59 -0500 (CDT) From: Karl Denninger Message-Id: <199608262022.PAA15285@Jupiter.mcs.net> Subject: Re: SCSI disks To: se@ZPR.Uni-Koeln.DE (Stefan Esser) Date: Mon, 26 Aug 1996 15:22:58 -0500 (CDT) Cc: wjw@IAEhv.nl, hardware@freebsd.org, scsi@freebsd.org, admin@IAEhv.nl In-Reply-To: <199608261909.VAA00920@x14.mi.uni-koeln.de> from "Stefan Esser" at Aug 26, 96 09:09:38 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hmmm, that's surprising, since my current development system uses > a Quantum Atlas (though its the XP32150S, the 2GB version). This > drive worked with the NCR driver of Spring 1995 at least, when I > first tested it. > > I'm quite sure that the Adaptec 1542 supported it as well, since > it is hard to find a device that doesn't work on the Adpatec, and > the Atlas is really well designed (IMHO). > > The Quantum Grand-Prix (XP34301S) is a different beast. It has got > bad press because of many failed (or DOA) drives, and it is noisy > and significantly slower than the Atlas, though both are 7200RPM > drives. > > You may also want to have a look at the IBM DHFS series, which is > also very fast and AFAIK reliable. > > Can't comment on recent Seagate drives. > > Regards, STefan The Quantum Atlas 4.3GB disks outperform Seagate Hawks in our news configuration by *at least* 2:1. I highly recommend them. 2MB internal cache buffer, read-ahead, tagged queueing, the whole 9 yards. Fast as hell and full Fast/Wide support to boot. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-scsi Mon Aug 26 18:06:47 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA02074 for freebsd-scsi-outgoing; Mon, 26 Aug 1996 18:06:47 -0700 (PDT) Received: from relay.hp.com (relay.hp.com [15.255.152.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA02060; Mon, 26 Aug 1996 18:06:44 -0700 (PDT) Received: from srmail.sr.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA184558000; Mon, 26 Aug 1996 18:06:40 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA240607996; Mon, 26 Aug 1996 18:06:36 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA238537995; Mon, 26 Aug 1996 18:06:35 -0700 Message-Id: <199608270106.AA238537995@hpnmhjw.sr.hp.com> To: Stefan Esser Cc: wjw@IAEhv.nl (Willem Jan Withagen), hardware@freebsd.org, scsi@freebsd.org, admin@IAEhv.nl Subject: Re: SCSI disks In-Reply-To: Your message of "Mon, 26 Aug 1996 21:09:38 +0200." <199608261909.VAA00920@x14.mi.uni-koeln.de> Date: Mon, 26 Aug 1996 18:06:35 -0700 From: Darryl Okahata Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > So I'm now looking for new disks. I've got 2 offerings: > > Seagate Barracuda 4.3 GB > > Quantum XP34300S > > The need to run on FreeBSD 2.0.5 and up. > > Long agood I tested the quantum with an NCR 53810 and an Adaptec 1542B > > and in both case it did not seem to work. Now things might have changed, b > ut > > Hmmm, that's surprising, since my current development system uses > a Quantum Atlas (though its the XP32150S, the 2GB version). This > drive worked with the NCR driver of Spring 1995 at least, when I > first tested it. I'm using a Quantum Atlas 34300S and an NCR-815-based SCSI controller, and they're working great. I've used it under 2.1R, and I'm now using it under 2.2-snap-960801. The block write performance (~3.3MB/s) isn't as good as I thought it would be, but it's good enough. I could always mount the drive async. > The Quantum Grand-Prix (XP34301S) is a different beast. It has got > bad press because of many failed (or DOA) drives, and it is noisy > and significantly slower than the Atlas, though both are 7200RPM > drives. The Grand Prix must be really noisy, as my Atlas has a constant ear-annoying whine (I think I'm going to go deaf in my right ear, listening to it ;-(), and perhaps makes the loudest seek noises that I've ever heard. -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-scsi Mon Aug 26 23:59:37 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA18456 for freebsd-scsi-outgoing; Mon, 26 Aug 1996 23:59:37 -0700 (PDT) Received: from odie.physik2.uni-rostock.de (odie.physik2.uni-rostock.de [139.30.40.28]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA18435; Mon, 26 Aug 1996 23:59:33 -0700 (PDT) Received: (from lkoeller@localhost) by odie.physik2.uni-rostock.de (8.7.5/8.7.3) id IAA20672; Tue, 27 Aug 1996 08:59:25 +0200 (MET DST) Date: Tue, 27 Aug 1996 08:59:25 +0200 (MET DST) From: Lars Koeller Message-Id: <199608270659.IAA20672@odie.physik2.uni-rostock.de> X-Face: nLQGe[[K51[{{[C\,BiQm[7]u1m{N>_\%nLBo4t@)CoZ}hK[W7DwX&V=}Wf#Qb,j:Jpj[(12r=b~:dYmh]fDf\, ]_frt6eM' dated: Mon, 26 Aug 1996 21:09:38 +0200 (MET DST) Cc: hardware@freebsd.org, scsi@freebsd.org, admin@IAEhv.nl Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! Stefan Esser writes: > Willem Jan Withagen writes: > > > > Hi, > > > > Until recently we as an ISP were using Micropolis disk with pleasure. > > But since several 4.3Gb started crashing, we've changed our view. > > > > So I'm now looking for new disks. I've got 2 offerings: > > Seagate Barracuda 4.3 GB > > Quantum XP34300S > > The need to run on FreeBSD 2.0.5 and up. > > Long agood I tested the quantum with an NCR 53810 and an Adaptec 1542B > > and in both case it did not seem to work. Now things might have changed, but > > Hmmm, that's surprising, since my current development system uses > a Quantum Atlas (though its the XP32150S, the 2GB version). This > drive worked with the NCR driver of Spring 1995 at least, when I > first tested it. > > I'm quite sure that the Adaptec 1542 supported it as well, since > it is hard to find a device that doesn't work on the Adpatec, and > the Atlas is really well designed (IMHO). > > The Quantum Grand-Prix (XP34301S) is a different beast. It has got > bad press because of many failed (or DOA) drives, and it is noisy > and significantly slower than the Atlas, though both are 7200RPM > drives. > > You may also want to have a look at the IBM DHFS series, which is > also very fast and AFAIK reliable. > > Can't comment on recent Seagate drives. > > Regards, STefan Perhaps it's the same phenomena I have with the Quantum and the Adaptec 1742 EISA SCSI controller. Every time the disc reads out of the cache, the response is so quick that a lot of controllers aren't ready to receive the first bytes. As a matter of fact the whole SCSI-bus is locked! The solution is to edit the modepage of the Quantum Atlas so that the disc inserts a delay of 15 micro seconds when a block is transfered out of the cache. If you need any information how to do this, don't hesitate to contact me again. Regards Lars -- ________________________________________________________________________ Lars Köller Phone: +49 381/498-1665, Fax: -1667 University of Rostock E-Mail: Department of Physics Lars_Koeller@odie.physik2.Uni-Rostock.DE Universitätsplatz 3 Anonymous ftp: D-18051 Rostock (Germany) ftp://odie.physik2.uni-rostock.de/pub From owner-freebsd-scsi Tue Aug 27 03:05:16 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA26965 for freebsd-scsi-outgoing; Tue, 27 Aug 1996 03:05:16 -0700 (PDT) Received: from iaehv.IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA26952; Tue, 27 Aug 1996 03:05:01 -0700 (PDT) Received: from LOCAL (wjw@localhost) by iaehv.IAEhv.nl (8.6.13/1.63); pid 27696 on Tue, 27 Aug 1996 12:03:45 +0200; id MAA27696 efrom: wjw; eto: UNKNOWN From: wjw@IAEhv.nl (Willem Jan Withagen) Message-Id: <199608271003.MAA27696@iaehv.IAEhv.nl> Subject: Re: SCSI disks To: admin@IAEhv.nl Date: Tue, 27 Aug 1996 12:03:45 +0200 (MET DST) Cc: wjw@IAEhv.nl, hardware@freebsd.org, scsi@freebsd.org In-Reply-To: <199608261909.VAA00920@x14.mi.uni-koeln.de> from "Stefan Esser" at Aug 26, 96 09:09:38 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I asked about SCSI drives and was going to summerise, but all questions have also been posted to both lists. So I'll forgo that exercise. You ( Stefan Esser ) write: => Hmmm, that's surprising, since my current development system uses => a Quantum Atlas (though its the XP32150S, the 2GB version). This => drive worked with the NCR driver of Spring 1995 at least, when I => first tested it. This was summer 1995, and I was still running 2.0 at home. On all systems did it work under DOS and OS/2, but not FreeBSD. I also had problems connecting it to a SGI system, and there I'd need to switch communication with the drive to async mode. Sunday I upgraded to 2.1.5 on my gateway, and 2.2-SNAP CD on my personal box, so there's plenty of toys to play with. Also note that I have a $250 difference in the offer. The Seagate Barracuda is the more expensive one. Thanx for all the info sofar, --WjW -- Internet Access Eindhoven BV., voice: +31-40-2438330, data: +31-40-2439436 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. From owner-freebsd-scsi Tue Aug 27 07:00:14 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA06511 for freebsd-scsi-outgoing; Tue, 27 Aug 1996 07:00:14 -0700 (PDT) Received: from heathers.stdio.com (risner@heathers.stdio.com [204.152.114.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA06501; Tue, 27 Aug 1996 07:00:07 -0700 (PDT) Received: (from risner@localhost) by heathers.stdio.com (8.6.12/8.6.13) id JAA02300; Tue, 27 Aug 1996 09:59:07 -0400 Date: Tue, 27 Aug 1996 09:59:07 -0400 From: James Risner Message-Id: <199608271359.JAA02300@heathers.stdio.com> To: freebsd-hackers@freebsd.org Subject: SCSI ncr.c assertion fail due to S_QUEUE_FULL error. Cc: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a 3.5 GIG drive: ncrcontrol -u 1 T:L Vendor Device Rev Speed Max Wide Tags 1:0 DEC RZ74 (C) DEC 427H 10.0 10.0 8 4 on heavy disk seeking I get: sd1(ncr1:1:0): COMMAND FAILED (4 28) @f09fb000. assertion "cp" failed: file "../../pci/ncr.c", line 5563 I looked up the COMMAND.FAILED code and found that 4 28 means: COND_MET or HS_COMPLETE and QUEUE_FULL I looked up the code about QUEUE_FULL which it does not run and it sets tags to 0 to fix. I set tags to 1 with ncrcontrol -u 1 -t 1 -w -stags=1 The problem went away. Now it is: ncrcontrol -u 1 T:L Vendor Device Rev Speed Max Wide Tags 1:0 DEC RZ74 (C) DEC 427H 10.0 10.0 8 1 Who's problem was present? SCSI system for not probing the drive and setting the tags lower somehow? ncr.c for not properly reseting after a QUEUE_FULL from a disk? Or both? Risner From owner-freebsd-scsi Tue Aug 27 08:45:50 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA10702 for freebsd-scsi-outgoing; Tue, 27 Aug 1996 08:45:50 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA10679; Tue, 27 Aug 1996 08:45:40 -0700 (PDT) Message-Id: <199608271545.IAA10679@freefall.freebsd.org> To: James Risner cc: freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: SCSI ncr.c assertion fail due to S_QUEUE_FULL error. In-reply-to: Your message of "Tue, 27 Aug 1996 09:59:07 EDT." <199608271359.JAA02300@heathers.stdio.com> Date: Tue, 27 Aug 1996 08:45:40 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I looked up the code about QUEUE_FULL which it does not run and it sets >tags to 0 to fix. Ouch. Pretty soon, the upper level SCSI layer will be controlling this, but until then, you'll have to ask Stefan why this happens. >Or both? > >Risner > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Tue Aug 27 09:38:05 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA14169 for freebsd-scsi-outgoing; Tue, 27 Aug 1996 09:38:05 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA14162 for ; Tue, 27 Aug 1996 09:37:59 -0700 (PDT) Received: from srmail.sr.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA142533864; Tue, 27 Aug 1996 09:37:45 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA256643856; Tue, 27 Aug 1996 09:37:37 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA000723856; Tue, 27 Aug 1996 09:37:36 -0700 Message-Id: <199608271637.AA000723856@hpnmhjw.sr.hp.com> To: Lars Koeller Cc: se@ZPR.Uni-Koeln.DE, wjw@IAEhv.nl (Willem Jan Withagen), scsi@freebsd.org, admin@IAEhv.nl Subject: Re: SCSI disks In-Reply-To: Your message of "Tue, 27 Aug 1996 08:59:25 +0200." <199608270659.IAA20672@odie.physik2.uni-rostock.de> Date: Tue, 27 Aug 1996 09:37:35 -0700 From: Darryl Okahata Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ FreeBSD-hardware removed from the reply list. ] > > Willem Jan Withagen writes: > > > > Long agood I tested the quantum with an NCR 53810 and an Adaptec 1542B > > > and in both case it did not seem to work. Now things might have changed, > > Perhaps it's the same phenomena I have with the Quantum and the > Adaptec 1742 EISA SCSI controller. Every time the disc reads out of the > cache, the response is so quick that a lot of controllers aren't ready > to receive the first bytes. As a matter of fact the whole SCSI-bus is The original poster had problems with an NCR-based controller, and so the "too fast Quantum" problem probably isn't the cause. People are using Atlas drives with NCR-based controllers without any problems (me, for one). I think it's more likely that the original poster was using a buggy release of FreeBSD (I think he mentioned 2.0). -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-scsi Tue Aug 27 13:58:27 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA29367 for freebsd-scsi-outgoing; Tue, 27 Aug 1996 13:58:27 -0700 (PDT) Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA29362; Tue, 27 Aug 1996 13:58:22 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-45.slip.Uni-Koeln.DE) by FileServ1.MI.Uni-Koeln.DE with SMTP id AA03457 (5.67b/IDA-1.5); Tue, 27 Aug 1996 22:58:17 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id WAA04283; Tue, 27 Aug 1996 22:35:11 +0200 (MET DST) Date: Tue, 27 Aug 1996 22:35:11 +0200 (MET DST) Message-Id: <199608272035.WAA04283@x14.mi.uni-koeln.de> From: Stefan Esser To: James Risner Cc: freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: SCSI ncr.c assertion fail due to S_QUEUE_FULL error. In-Reply-To: <199608271359.JAA02300@heathers.stdio.com> References: <199608271359.JAA02300@heathers.stdio.com> Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk James Risner writes: > > I have a 3.5 GIG drive: > ncrcontrol -u 1 > T:L Vendor Device Rev Speed Max Wide Tags > 1:0 DEC RZ74 (C) DEC 427H 10.0 10.0 8 4 > > on heavy disk seeking I get: > sd1(ncr1:1:0): COMMAND FAILED (4 28) @f09fb000. > assertion "cp" failed: file "../../pci/ncr.c", line 5563 > > I looked up the COMMAND.FAILED code and found that 4 28 means: > COND_MET or HS_COMPLETE and QUEUE_FULL Yes, true. Sorry, I'm too busy and didn't immediatlely remmeber those codes, but that kind of problem has also been noticed by an user of the SEQUEL 5200 (?) drive, which is a DEC 5.25" designed drive with 2GB or 3GB capacity. I'll have to scan my mail archive for details ... > I looked up the code about QUEUE_FULL which it does not run and it sets > tags to 0 to fix. Hmmm, that code was there as a precaution in case a device supported only a very small number of tags. But I never had access to a device that actually triggered this code, and it really never has been tested for that reason. > I set tags to 1 with > ncrcontrol -u 1 -t 1 -w -stags=1 (You don't need the -w in this case. If there is only one NCR card in the system, then you may also ommit the -u 1 option.) Just use 0 as the number of tags. This may slightly reduce the overhead (I'm not sure whether there is a test for more than ONE or more than ZERO tags. ONE tag obviously doesn't make much sense :) > The problem went away. > Now it is: > ncrcontrol -u 1 > T:L Vendor Device Rev Speed Max Wide Tags > 1:0 DEC RZ74 (C) DEC 427H 10.0 10.0 8 1 > > Who's problem was present? Since tags work with just about every current drive (the HP 3724 and 3725 being the (un)famous exception), I guess it is the drive's fault. I'm using my Quantum Atlas with tags for more than a year now, and though I rebuild the world (FreeBSD-current) nearly each night as kind of a regression test, it never failed. It does work with 4 tags (the default) as reliable as with 16. > SCSI system for not probing the drive and setting the tags lower somehow? No, the drive announces support of tags in its INQUIRY response. Most drives seem to support at least a few tens of tags, I never hit the limit in my tests :) > ncr.c for not properly reseting after a QUEUE_FULL from a disk? Well, as I said, this code should not actually be necessary, and it has not been tested. The new generic SCSI code that is currently developed by Justin Gibbs will move most of the complexity of tag support into the controller independent layer, and I'm sure his code will be better tested and will do the right thing :) For now just disable tags. I'd be interested to know, whether it works reliably with tags if driven by some other host adapter, but I guess you don't have the equipment to test this. It would be especially interesting to see whether it fails if too many commands are active simultanously, or whether it does not like to many different tag numbers to be used over time. (The NCR driver tries to always use the same tag numbers over and over, except if a command fails, when it will choose a new driver in certain situations.) BTW: A firmware upgrade might solve your problem, too. If you still got warranty on the drive, you may even be able to get it for free. I'm not sure at all, whether this drive is still supported in some way, and by whom (since DEC sold its Storage Division to Quantum some two years ago), but getting the latest firmware that was released might help. (It did for some other drives, that had problems with tags!) Regards, STefan From owner-freebsd-scsi Wed Aug 28 03:47:23 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA18676 for freebsd-scsi-outgoing; Wed, 28 Aug 1996 03:47:23 -0700 (PDT) Received: from unicorn.uk1.vbc.net (unicorn.uk1.vbc.net [204.137.194.11]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA18671 for ; Wed, 28 Aug 1996 03:47:20 -0700 (PDT) Received: (from gordon@localhost) by unicorn.uk1.vbc.net (8.7.3/8.7.3) id LAA17638; Wed, 28 Aug 1996 11:47:14 +0100 Date: Wed, 28 Aug 1996 11:47:13 +0100 (BST) From: Gordon Henderson X-Sender: gordon@unicorn To: freebsd-scsi@freebsd.org Subject: HP SCSI drives - Jumper settings? Message-ID: Distribution: world Organization: Home for lost Drogons MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a pair of HP C3325A 2GB SCSI drives, whch I'm about to add into a FreeBSD news machine, but, alas, no manual for them. I need to connect them on the same bus - I've worked out SCSI ID, but there are 2 other jumpers, I'm presuming one is parity, the other termination enable. With both of them on the same bus, they verify ok from the BIOS (Adaptec PCI card), but I'm woried that under heavy load, if both are terminated then I may see problems. The jumpers are set as below: 012 34 56789 *** ** ***** || | | *** ** ***** This being ID 3, the ID jumpers being the leftmost block of 3. Anyone any clues what the other jumpers do, or which one of 4 or 5 is the terminator enable jumper? (Or prehaps one of the others is a terminator disable..) Thanks for any input ... Gordon From owner-freebsd-scsi Wed Aug 28 04:06:24 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA19587 for freebsd-scsi-outgoing; Wed, 28 Aug 1996 04:06:24 -0700 (PDT) Received: from bigpuppy.newell.arlington.va.us (mcnsisdn.newell.arlington.va.us [206.27.237.14]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA19570 for ; Wed, 28 Aug 1996 04:06:19 -0700 (PDT) Received: (from mnewell@localhost) by bigpuppy.newell.arlington.va.us (8.6.12/8.6.9) id HAA26143; Wed, 28 Aug 1996 07:02:46 -0400 Date: Wed, 28 Aug 1996 07:02:45 -0400 (EDT) From: Mike Newell To: Gordon Henderson cc: freebsd-scsi@freebsd.org Subject: Re: HP SCSI drives - Jumper settings? 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 Many manufacturers have the spec sheets, including jumper settings, on their Web pages. Have you checked out HP's? Mike On Wed, 28 Aug 1996, Gordon Henderson wrote: > Date: Wed, 28 Aug 1996 11:47:13 +0100 (BST) > From: Gordon Henderson > To: freebsd-scsi@freebsd.org > Subject: HP SCSI drives - Jumper settings? > > > I have a pair of HP C3325A 2GB SCSI drives, whch I'm about to add into a > FreeBSD news machine, but, alas, no manual for them. I need to connect > them on the same bus - I've worked out SCSI ID, but there are 2 other > jumpers, I'm presuming one is parity, the other termination enable. With > both of them on the same bus, they verify ok from the BIOS (Adaptec PCI > card), but I'm woried that under heavy load, if both are terminated then I > may see problems. The jumpers are set as below: > > 012 34 56789 > *** ** ***** > || | | > *** ** ***** > > This being ID 3, the ID jumpers being the leftmost block of 3. > > Anyone any clues what the other jumpers do, or which one of 4 or 5 is the > terminator enable jumper? (Or prehaps one of the others is a terminator > disable..) > > Thanks for any input ... > > Gordon > Much obliged, Mike +--------------------------------------+------------------------------------+ | Mike Newell | The opinions expressed herein | | Affiliation: | are mine. You can take them or | | Address: | leave them. Flames to /dev/null. | +--------------------------------------+------------------------------------+ | Mike@Newell.arlington.va.us | http://www.newell.arlington.va.us | +--------------------------------------+------------------------------------+ | "Peace. It's wonderful!" Father Divine. | +---------------------------------------------------------------------------+ From owner-freebsd-scsi Wed Aug 28 12:13:08 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA21470 for freebsd-scsi-outgoing; Wed, 28 Aug 1996 12:13:08 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA21426; Wed, 28 Aug 1996 12:12:55 -0700 (PDT) Received: from uni4nn.iaf.nl (uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id VAA13620; Wed, 28 Aug 1996 21:17:06 +0200 Received: by uni4nn.iaf.nl with UUCP id AA27035 (5.67b/IDA-1.5); Wed, 28 Aug 1996 21:16:39 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA15258 (5.67b/IDA-1.5); Wed, 28 Aug 1996 20:52:28 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.12) id UAA01088; Wed, 28 Aug 1996 20:41:44 +0200 From: Wilko Bulte Message-Id: <199608281841.UAA01088@yedi.iaf.nl> Subject: Re: SCSI ncr.c assertion fail due to S_QUEUE_FULL error. To: se@zpr.uni-koeln.de (Stefan Esser) Date: Wed, 28 Aug 1996 20:41:44 +0200 (MET DST) Cc: risner@heathers.stdio.com, freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org In-Reply-To: <199608272035.WAA04283@x14.mi.uni-koeln.de> from "Stefan Esser" at Aug 27, 96 10:35:11 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Stefan Esser wrote... > James Risner writes: > > > > I have a 3.5 GIG drive: > > ncrcontrol -u 1 > > T:L Vendor Device Rev Speed Max Wide Tags > > 1:0 DEC RZ74 (C) DEC 427H 10.0 10.0 8 4 > > > > on heavy disk seeking I get: > > sd1(ncr1:1:0): COMMAND FAILED (4 28) @f09fb000. > > assertion "cp" failed: file "../../pci/ncr.c", line 5563 > > > > I looked up the COMMAND.FAILED code and found that 4 28 means: > > COND_MET or HS_COMPLETE and QUEUE_FULL > > Yes, true. Sorry, I'm too busy and didn't immediatlely > remmeber those codes, but that kind of problem has also > been noticed by an user of the SEQUEL 5200 (?) drive, > which is a DEC 5.25" designed drive with 2GB or 3GB > capacity. I'll have to scan my mail archive for details ... Like: bash# ncrcontrol T:L Vendor Device Rev Speed Max Wide Tags 0:0 DEC RZ28 (C) DEC 442C 10.0 10.0 8 4 In my case TCQ started working after I upgraded the firmware in the drive. (RZ28 is 3.5" so you might have another example in mind) > BTW: A firmware upgrade might solve your problem, too. If you > still got warranty on the drive, you may even be able to get > it for free. I'm not sure at all, whether this drive is still > supported in some way, and by whom (since DEC sold its Storage > Division to Quantum some two years ago), but getting the latest > firmware that was released might help. (It did for some other > drives, that had problems with tags!) My fw ref guide says the latest firmware for the RZ74 is either T427N or T436A. Which one is dependent on the rev of the drive's electronics. Downloading the wrong fw results in a paperweight!! Wilko _ ____________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------- From owner-freebsd-scsi Wed Aug 28 12:39:15 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA22624 for freebsd-scsi-outgoing; Wed, 28 Aug 1996 12:39:15 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA22617; Wed, 28 Aug 1996 12:39:13 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id PAA04015; Wed, 28 Aug 1996 15:39:11 -0400 (EDT) Date: Wed, 28 Aug 1996 15:39:11 -0400 (EDT) From: Brian Tao To: FREEBSD-HACKERS-L , FREEBSD-SCSI-L Subject: Streamlogic RAIDION drive arrays 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 Has anyone tried Streamlogic's RAIDION drive arrays? Apparently they can do RAID 1 and 5 in hardware... all your host sees is one very large, very fast disk. I'm thinking of tossing one of those with a dozen 2GB drives or so in for a news server. I may not need special drivers, but I can see some hurdles with disktab-related stuff. Maybe I can get an eval unit from them to play with. :) -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-scsi Wed Aug 28 13:11:53 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA24236 for freebsd-scsi-outgoing; Wed, 28 Aug 1996 13:11:53 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA24204; Wed, 28 Aug 1996 13:11:34 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id XAA29587; Wed, 28 Aug 1996 23:12:09 +0300 Date: Wed, 28 Aug 1996 23:12:08 +0300 (EET DST) From: Narvi To: Brian Tao cc: FREEBSD-HACKERS-L , FREEBSD-SCSI-L Subject: Re: Streamlogic RAIDION drive arrays 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, 28 Aug 1996, Brian Tao wrote: > Has anyone tried Streamlogic's RAIDION drive arrays? Apparently > they can do RAID 1 and 5 in hardware... all your host sees is one very > large, very fast disk. I'm thinking of tossing one of those with a > dozen 2GB drives or so in for a news server. I may not need special > drivers, but I can see some hurdles with disktab-related stuff. > Maybe I can get an eval unit from them to play with. :) Could you give back any views you have on it? I have my I on the CMDs external cabinet with 4/6 slots (depends on the drive size). I'll echo back when we have acquired one and tested it out... Sander > -- > Brian Tao (BT300, taob@io.org, taob@ican.net) > Senior Systems and Network Administrator, Internet Canada Corp. > "Though this be madness, yet there is method in't" > > From owner-freebsd-scsi Wed Aug 28 15:43:47 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA04246 for freebsd-scsi-outgoing; Wed, 28 Aug 1996 15:43:47 -0700 (PDT) Received: from gordius.gordian.com (gordius.gordian.com [192.73.220.81]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA04225; Wed, 28 Aug 1996 15:43:43 -0700 (PDT) Received: from delphi.gordian.com (delphi.gordian.com [192.73.220.125]) by gordius.gordian.com (8.7.5/8.6.5) with ESMTP id PAA05413; Wed, 28 Aug 1996 15:43:44 -0700 (PDT) Received: (from steve@localhost) by delphi.gordian.com (8.7.2/8.6.9) id PAA19057; Wed, 28 Aug 1996 15:43:40 -0700 (PDT) Date: Wed, 28 Aug 1996 15:43:40 -0700 (PDT) Message-Id: <199608282243.PAA19057@delphi.gordian.com> From: Steve Khoo To: freebsd-current@freebsd.org CC: freebsd-scsi@freebsd.org, se@ZPR.Uni-Koeln.DE In-reply-to: Steve Khoo's message of Mon, 26 Aug 1996 12:15:09 -0700 (PDT) Subject: Re: problems booting with 2 drives on NCR8251D References: <199608261915.MAA10702@delphi.gordian.com> Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk FYI: Well, I didn't get any response on this, but finally tracked down the problem to a flaky pin on one of the 68pin FWD SCSI connectors. SEK >>>>> "Steve" == Steve Khoo writes: Steve> setup: Steve> Asus MB(P55TP4XEG) 512K Cache Steve> 32MB RAM Steve> Fast Wide Differential SCSI Controller (NCR8251D) Steve> Seagate ST12550WD on SCSI ID #0 Steve> Seagate ST15150WD on SCSI ID #1 Steve> The system is running FreeBSD 2.2-CURRENT sup'd on 8/17/96. Steve> The system boots and runs find with just the first(Seagate Steve> ST12550WD) drive. When I added the second(Seagate Steve> ST15150WD) drive I get the following errors. I can boot Steve> dos and do fdisk/format and stuff on the second drive Steve> without any problems. Any ideas what the errors mean? Steve> I'd appreciate any help. Steve> Thanks! Steve> SEK Steve> FreeBSD 2.2-CURRENT #0: Mon Aug 19 12:48:53 PDT 1996 Steve> steve@metis.gordian.com:/usr/src/sys/compile/metis Steve> Calibrating clock(s) relative to mc146818A clock... Steve> i586 clock: 99465569 Hz, i8254 clock: 1193086 Hz Steve> CPU: Pentium (99.47-MHz 586-class CPU) Steve> Origin = "GenuineIntel" Id = 0x525 Stepping=5 Steve> Features=0x1bf Steve> real memory = 33554432 (32768K bytes) Steve> avail memory = 30695424 (29976K bytes) Steve> Probing for devices on PCI bus 0: Steve> chip0 rev 2 on pci0:0 Steve> chip1 rev 2 on pci0:7:0 Steve> pci0:7:1: Intel Corporation, device=0x1230, class=storage (ide) [no driver assigned] Steve> de0 rev 18 int a irq 12 on pci0:9 Steve> de0: SMC 9332 DC21140 [10-100Mb/s] pass 1.2 Steve> de0: address 00:00:c0:58:c3:e4 Steve> de0: enabling 10baseT port Steve> ncr0 rev 2 int a irq 10 on pci0:10 Steve> ncr0 waiting for scsi devices to settle Steve> (ncr0:0:0): "SEAGATE ST12550W 0004" type 0 fixed SCSI 2 Steve> sd0(ncr0:0:0): Direct-Access Steve> sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled. Steve> sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Steve> 2040MB (4178874 512 byte sectors) Steve> (ncr0:1:0): "SEAGATE ST15150W 0023" type 0 fixed SCSI 2 Steve> sd1(ncr0:1:0): Direct-Access Steve> sd1(ncr0:1:0): WIDE SCSI (16 bit) enabled. Steve> ncr0:1: ERROR (80:91) (9-ae-0) (0/1b) @ (d8c:19000004). Steve> script cmd = 89030000 Steve> reg: da 10 80 1b 47 00 01 07 23 09 81 ae 80 00 0e 08. Steve> ncr0: restart (fatal error). Steve> sd1(ncr0:1:0): COMMAND FAILED (9 ff) @f109b400. Steve> ncr0: aborting job ... Steve> ncr0:0: ERROR (90:0) (8-a6-0) (0/13) @ (418:43000060). Steve> script cmd = 878b0000 Steve> reg: da 00 00 13 47 00 01 07 31 08 01 a6 80 00 0e 0a. Steve> ncr0: restart (fatal error). Steve> sd1(ncr0:1:0): COMMAND FAILED (9 ff) @f109b400. Steve> ncr0: aborting job ... Steve> ncr0:0: ERROR (90:0) (8-a6-0) (0/13) @ (418:43000060). Steve> script cmd = 878b0000 Steve> reg: da 00 00 13 47 00 01 07 31 08 01 a6 80 00 0e 0a. Steve> ncr0: restart (fatal error). Steve> sd1(ncr0:1:0): COMMAND FAILED (9 ff) @f109b400. Steve> ncr0: aborting job ... Steve> ncr0:0: ERROR (90:0) (8-a6-0) (0/13) @ (418:43000060). Steve> script cmd = 878b0000 Steve> reg: da 00 00 13 47 00 01 07 31 08 01 a6 80 00 0e 0a. Steve> ncr0: restart (fatal error). Steve> sd1(ncr0:1:0): COMMAND FAILED (9 ff) @f109b400. Steve> ncr0: aborting job ... Steve> ncr0:0: ERROR (90:0) (8-a6-0) (0/13) @ (418:43000060). Steve> script cmd = 878b0000 Steve> reg: da 00 00 13 47 00 01 07 31 08 01 a6 80 00 0e 0a. Steve> ncr0: restart (fatal error). Steve> sd1(ncr0:1:0): COMMAND FAILED (9 ff) @f109b400. Steve> sd1 could not mode sense (4). Using ficticious geometry Steve> ncr0: aborting job ... Steve> ncr0:0: ERROR (90:0) (8-a6-0) (0/13) @ (418:43000060). Steve> script cmd = 878b0000 Steve> reg: da 00 00 13 47 00 01 07 31 08 01 a6 80 00 0e 0a. Steve> ncr0: restart (fatal error). Steve> sd1(ncr0:1:0): COMMAND FAILED (9 ff) @f109b400. Steve> ncr0: aborting job ... Steve> ncr0:0: ERROR (90:0) (8-a6-0) (0/13) @ (418:43000060). Steve> script cmd = 878b0000 Steve> reg: da 00 00 13 47 00 01 07 31 08 01 a6 80 00 0e 0a. Steve> ncr0: restart (fatal error). Steve> sd1(ncr0:1:0): COMMAND FAILED (9 ff) @f109b400. Steve> ncr0: aborting job ... Steve> ncr0:0: ERROR (90:0) (8-a6-0) (0/13) @ (418:43000060). Steve> script cmd = 878b0000 Steve> reg: da 00 00 13 47 00 01 07 31 08 01 a6 80 00 0e 0a. Steve> ncr0: restart (fatal error). Steve> sd1(ncr0:1:0): COMMAND FAILED (9 ff) @f109b400. Steve> ncr0: aborting job ... Steve> ncr0:0: ERROR (90:0) (8-a6-0) (0/13) @ (418:43000060). Steve> script cmd = 878b0000 Steve> reg: da 00 00 13 47 00 01 07 31 08 01 a6 80 00 0e 0a. Steve> ncr0: restart (fatal error). Steve> sd1(ncr0:1:0): COMMAND FAILED (9 ff) @f109b400. Steve> ncr0: aborting job ... Steve> ncr0:0: ERROR (90:0) (8-a6-0) (0/13) @ (418:43000060). Steve> script cmd = 878b0000 Steve> reg: da 00 00 13 47 00 01 07 31 08 01 a6 80 00 0e 0a. Steve> ncr0: restart (fatal error). Steve> sd1(ncr0:1:0): COMMAND FAILED (9 ff) @f109b400. Steve> sd1: could not get size Steve> 0MB (0 512 byte sectors) From owner-freebsd-scsi Wed Aug 28 17:28:34 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA18046 for freebsd-scsi-outgoing; Wed, 28 Aug 1996 17:28:34 -0700 (PDT) Received: from sumter.awod.com (awod.com [198.81.225.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA17981; Wed, 28 Aug 1996 17:28:18 -0700 (PDT) Received: from tsunami..awod.com (chsm003.awod.com [206.31.146.203]) by sumter.awod.com (8.6.12/8.6.12) with SMTP id UAA26682; Wed, 28 Aug 1996 20:28:17 -0400 Message-Id: <1.5.4.32.19960829002801.00913104@awod.com> X-Sender: klam@awod.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 28 Aug 1996 20:28:01 -0400 To: Brian Tao , FREEBSD-HACKERS-L , FREEBSD-SCSI-L From: Ken Lam Subject: Re: Streamlogic RAIDION drive arrays Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 03:39 PM 8/28/96 -0400, you wrote: > Has anyone tried Streamlogic's RAIDION drive arrays? Apparently >they can do RAID 1 and 5 in hardware... all your host sees is one very >large, very fast disk. I'm thinking of tossing one of those with a >dozen 2GB drives or so in for a news server. I may not need special >drivers, but I can see some hurdles with disktab-related stuff. >Maybe I can get an eval unit from them to play with. :) Yes. I have installed one for a non-linear video editor. It was a 12GB array. Worked great. Of course it was used on a Macintosh. It wasn't streamlogic, but micropolis then. The only thing I didn't really like was that I couldn't purchase is with other brand drives (I prefer Seagate Hawks). I didn't get a chance to test it under FreeBSD. Fairly fast, but other than the RAID 5 aspect, why not use CCD? News spool is hardly a get killed by users application (unless you have lots of disgruntled postal workers online ;) ) --- Ken Lam lam@awod.com Integrated Technical Systems Systems, Networks, and Internet Solutions -- Defining Technology Today "'Plug and Play' was only applicable to the original ATARI(tm)" From owner-freebsd-scsi Thu Aug 29 07:22:09 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA10613 for freebsd-scsi-outgoing; Thu, 29 Aug 1996 07:22:09 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA10608; Thu, 29 Aug 1996 07:22:06 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id JAA06736; Thu, 29 Aug 1996 09:20:22 -0500 From: Joe Greco Message-Id: <199608291420.JAA06736@brasil.moneng.mei.com> Subject: Re: Streamlogic RAIDION drive arrays To: klam@awod.com (Ken Lam) Date: Thu, 29 Aug 1996 09:20:22 -0500 (CDT) Cc: taob@io.org, freebsd-hackers@FreeBSD.org, freebsd-scsi@FreeBSD.org In-Reply-To: <1.5.4.32.19960829002801.00913104@awod.com> from "Ken Lam" at Aug 28, 96 08:28:01 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > At 03:39 PM 8/28/96 -0400, you wrote: > > Has anyone tried Streamlogic's RAIDION drive arrays? Apparently > >they can do RAID 1 and 5 in hardware... all your host sees is one very > >large, very fast disk. I'm thinking of tossing one of those with a > >dozen 2GB drives or so in for a news server. I may not need special > >drivers, but I can see some hurdles with disktab-related stuff. > >Maybe I can get an eval unit from them to play with. :) > > Yes. I have installed one for a non-linear video editor. It was > a 12GB array. Worked great. Of course it was used on a Macintosh. > > It wasn't streamlogic, but micropolis then. The only thing I > didn't really like was that I couldn't purchase is with other > brand drives (I prefer Seagate Hawks). > > I didn't get a chance to test it under FreeBSD. Fairly fast, but > other than the RAID 5 aspect, why not use CCD? News spool is hardly > a get killed by users application (unless you have lots of > disgruntled postal workers online ;) ) If it has write back cache, you have a reason to look at it :-) If not, it's not worth much. I've been considering trying something like a Mylex DAC960SI (?), SCSI-to-SCSI RAID controller, simply for the cache you can stick on it. ... JG From owner-freebsd-scsi Thu Aug 29 09:53:23 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA18369 for freebsd-scsi-outgoing; Thu, 29 Aug 1996 09:53:23 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA18354 for ; Thu, 29 Aug 1996 09:53:17 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id SAA12989 for ; Thu, 29 Aug 1996 18:51:43 +0200 Message-Id: <199608291651.SAA12989@login.bigblue.no> From: "Frode Nordahl" To: "scsi@FreeBSD.org" Date: Thu, 29 Aug 96 18:53:35 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: DPT drivers for FreeBSD? Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I saw in the mailing list archive that a DPT driver was being worked on for FreeBSD. Does anyone know the status of this project? --------------------------------- Frode Nordahl From owner-freebsd-scsi Thu Aug 29 09:58:54 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA18662 for freebsd-scsi-outgoing; Thu, 29 Aug 1996 09:58:54 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA18654 for ; Thu, 29 Aug 1996 09:58:48 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id SAA13020 for ; Thu, 29 Aug 1996 18:57:14 +0200 Message-Id: <199608291657.SAA13020@login.bigblue.no> From: "Frode Nordahl" To: "scsi@FreeBSD.org" Date: Thu, 29 Aug 96 18:59:07 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Adaptec 2940 vs. Tandberg TDC 4220 Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I have a problem with FreeBSD 2.1.0-STABLE, Adaptec 2940 and a Tandberg TDC 4220. When trying to use the tape drive, the system kernel comes up with error messages (SCSI bus is reset, some queue errors etc), and the system hangs and automaticly reboots. I have noticed that the messages referrs to SCSI ID 2 and not the SCSI ID that the tape drive uses. When booting, the tape gets a density code of 0x0 wich normally not works for any tape drive. Anyone have a sollution to this problem? --------------------------------- Frode Nordahl From owner-freebsd-scsi Thu Aug 29 12:46:34 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA29882 for freebsd-scsi-outgoing; Thu, 29 Aug 1996 12:46:34 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA29872; Thu, 29 Aug 1996 12:46:32 -0700 (PDT) Message-Id: <199608291946.MAA29872@freefall.freebsd.org> To: "Frode Nordahl" cc: "scsi@FreeBSD.org" Subject: Re: Adaptec 2940 vs. Tandberg TDC 4220 In-reply-to: Your message of "Thu, 29 Aug 1996 18:59:07 BST." <199608291657.SAA13020@login.bigblue.no> Date: Thu, 29 Aug 1996 12:46:31 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I have a problem with FreeBSD 2.1.0-STABLE, Adaptec 2940 and a Tandberg TDC 42 >20. > >When trying to use the tape drive, the system kernel comes up with error messa >ges (SCSI bus is reset, some >queue errors etc), and the system hangs and automaticly reboots. > >I have noticed that the messages referrs to SCSI ID 2 and not the SCSI ID that > the tape drive uses. > >When booting, the tape gets a density code of 0x0 wich normally not works for >any tape drive. Anyone have a >sollution to this problem? >--------------------------------- >Frode Nordahl Does your tape drive allow disconnection? Do you have disconnection enabled in SCSI-Select? It sounds like the tape is attempting an operation that takes a long time to perform, but it is not releasing the bus. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Fri Aug 30 08:35:38 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA26816 for freebsd-scsi-outgoing; Fri, 30 Aug 1996 08:35:38 -0700 (PDT) Received: from mail.vividnet.com (mail.vividnet.com [206.149.144.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA26807 for ; Fri, 30 Aug 1996 08:35:30 -0700 (PDT) Received: from aquarius.vividnet.com (postmaster@mail.vividnet.com) by mail.vividnet.com (8.7.5/8.7.5) with SMTP id IAA06131 for ; Fri, 30 Aug 1996 08:03:32 -0700 (PDT) Date: Fri, 30 Aug 1996 08:35:11 -0700 (PDT) From: Brian Wang To: freebsd-scsi@freebsd.org Subject: NCR0+IBM DORS-32160 WA0A 2 gigs HD - assertion "cp" failed 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 have just put a new mail/dns server online, which has the following configuration: FreeBSD 2.1.5 Release P75 CPU + ASUSTPN4 MB (Triton I with 256k pipeline cache) 32 megs non-edo RAM 3COM 509 ethernet card Trident PCI video card ASUS SC200 SCSI card (ncr) IBM DORS-32160 2 gigs HD I am getting some messages via dmesg complainting about assertion "cp" failed. The server runs fine, and does seem to operate quiet normal except from these errors coming from "ncr.c" (error outputs included at the end of this email). Should I just start replacing the SCSI subsystem? Thanks Sincerely, Brian Wang --error logs-- sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65400. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65400. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65400. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65400. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65400. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65400. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65400. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65400. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65400. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65c00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65c00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65c00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65c00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65e00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65e00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65e00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. assertion "cp" failed: file "../../pci/ncr.c", line 5563 assertion "cp" failed: file "../../pci/ncr.c", line 5563 sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65c00. From owner-freebsd-scsi Fri Aug 30 08:55:31 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA28910 for freebsd-scsi-outgoing; Fri, 30 Aug 1996 08:55:31 -0700 (PDT) Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA28881 for ; Fri, 30 Aug 1996 08:55:24 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-17.slip.Uni-Koeln.DE) by FileServ1.MI.Uni-Koeln.DE with SMTP id AA20721 (5.67b/IDA-1.5 for ); Fri, 30 Aug 1996 17:55:20 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id RAA02753; Fri, 30 Aug 1996 17:44:27 +0200 (MET DST) Date: Fri, 30 Aug 1996 17:44:27 +0200 (MET DST) Message-Id: <199608301544.RAA02753@x14.mi.uni-koeln.de> From: Stefan Esser To: Brian Wang Cc: freebsd-scsi@FreeBSD.org Subject: Re: NCR0+IBM DORS-32160 WA0A 2 gigs HD - assertion "cp" failed In-Reply-To: References: Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Brian Wang writes: > Hi, > > I have just put a new mail/dns server online, which has the > following configuration: > > FreeBSD 2.1.5 Release > P75 CPU + ASUSTPN4 MB (Triton I with 256k pipeline cache) > 32 megs non-edo RAM > 3COM 509 ethernet card > Trident PCI video card > ASUS SC200 SCSI card (ncr) > IBM DORS-32160 2 gigs HD > > I am getting some messages via dmesg complainting about assertion > "cp" failed. The server runs fine, and does seem to operate quiet normal > except from these errors coming from "ncr.c" (error outputs included at > the end of this email). Should I just start replacing the SCSI subsystem? > sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. > assertion "cp" failed: file "../../pci/ncr.c", line 5563 Oh well, the DORS shows that kind of problem ? How often do these messages occur ? Please try with Tagged Command Queueing disabled: # ncrcontrol -s tags=0 and let me know, whether that fixes the problem. I'll have a 53c875 + DORS drive soon, since I want to use these devices as the base for the reworking of the NCR driver (addition of Ultra-SCSI support). Up to now, I always choose devices that did not fail, and it seems that the DORS is finally a drive that I can expect to show errors on my development system, giving me a chance to understand why a modern drive does not work correctly with tags ... Regards, STefan From owner-freebsd-scsi Fri Aug 30 09:36:49 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA03199 for freebsd-scsi-outgoing; Fri, 30 Aug 1996 09:36:49 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA03192; Fri, 30 Aug 1996 09:36:46 -0700 (PDT) Message-Id: <199608301636.JAA03192@freefall.freebsd.org> To: Stefan Esser cc: Brian Wang , freebsd-scsi@FreeBSD.ORG Subject: Re: NCR0+IBM DORS-32160 WA0A 2 gigs HD - assertion "cp" failed In-reply-to: Your message of "Fri, 30 Aug 1996 17:44:27 +0200." <199608301544.RAA02753@x14.mi.uni-koeln.de> Date: Fri, 30 Aug 1996 09:36:46 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Up to now, I always choose devices that did not >fail, and it seems that the DORS is finally a drive >that I can expect to show errors on my development >system, giving me a chance to understand why a modern >drive does not work correctly with tags ... > >Regards, STefan These errors are for the QUEUE FULL condition right? I think drives are allowed to return this even if the cause is temporary. We'll have to come up with a strategy for when to reduce maxtags on drives that doesn't penalize drives that do this kind of thing occasionally. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Fri Aug 30 09:41:01 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA03827 for freebsd-scsi-outgoing; Fri, 30 Aug 1996 09:41:01 -0700 (PDT) Received: from mail.vividnet.com (mail.vividnet.com [206.149.144.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA03813 for ; Fri, 30 Aug 1996 09:40:58 -0700 (PDT) Received: from aquarius.vividnet.com (postmaster@mail.vividnet.com) by mail.vividnet.com (8.7.5/8.7.5) with SMTP id JAA06881; Fri, 30 Aug 1996 09:08:56 -0700 (PDT) Date: Fri, 30 Aug 1996 09:40:35 -0700 (PDT) From: Brian Wang To: Stefan Esser cc: freebsd-scsi@FreeBSD.org Subject: Re: NCR0+IBM DORS-32160 WA0A 2 gigs HD - assertion "cp" failed In-Reply-To: <199608301544.RAA02753@x14.mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 30 Aug 1996, Stefan Esser wrote: > Brian Wang writes: > > I am getting some messages via dmesg complainting about assertion > > "cp" failed. The server runs fine, and does seem to operate quiet normal > > except from these errors coming from "ncr.c" (error outputs included at > > the end of this email). Should I just start replacing the SCSI subsystem? > > > sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. > > assertion "cp" failed: file "../../pci/ncr.c", line 5563 > > Oh well, the DORS shows that kind of problem ? > > How often do these messages occur ? > > Please try with Tagged Command Queueing disabled: > > # ncrcontrol -s tags=0 > > and let me know, whether that fixes the problem. > > > I'll have a 53c875 + DORS drive soon, since I want > to use these devices as the base for the reworking > of the NCR driver (addition of Ultra-SCSI support). > > Up to now, I always choose devices that did not > fail, and it seems that the DORS is finally a drive > that I can expect to show errors on my development > system, giving me a chance to understand why a modern > drive does not work correctly with tags ... > > Regards, STefan Yes, DORS it is, and my first IBM SCSI drive. These assertion "cp" failed messages happened twice. The first time occured during FreeBSD installation, and the second during its first day operation (2 out of 2, so it is quiet often... ). Tag command queuing is off now, and lets see if that fixes it. Thanks for the help! Sincerely, Brian Wang From owner-freebsd-scsi Fri Aug 30 09:55:42 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA05026 for freebsd-scsi-outgoing; Fri, 30 Aug 1996 09:55:42 -0700 (PDT) Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA05020 for ; Fri, 30 Aug 1996 09:55:36 -0700 (PDT) Received: (from craig@localhost) by seabass.progroup.com (8.7.5/8.6.12) id JAA03796; Fri, 30 Aug 1996 09:53:18 -0700 (PDT) Message-Id: <199608301653.JAA03796@seabass.progroup.com> Subject: Re: NCR0+IBM DORS-32160 WA0A 2 gigs HD - assertion "cp" failed To: se@zpr.uni-koeln.de (Stefan Esser) Date: Fri, 30 Aug 1996 09:53:18 -0700 (PDT) From: "Craig Shaver" Cc: scsi@FreeBSD.org In-Reply-To: <199608301544.RAA02753@x14.mi.uni-koeln.de> from "Stefan Esser" at Aug 30, 96 05:44:27 pm X-Mailer: ELM [version 2.4 PL25 ME8b] 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 > > > Brian Wang writes: > > Hi, > > > > I have just put a new mail/dns server online, which has the > > following configuration: > > > > FreeBSD 2.1.5 Release 2.1.0R > > P75 CPU + ASUSTPN4 MB (Triton I with 256k pipeline cache) p133 + 512K > > 32 megs non-edo RAM edo > > 3COM 509 ethernet card > > Trident PCI video card > > ASUS SC200 SCSI card (ncr) I use this board as the first controller and use a tyan 825 board as a second controller with a > > IBM DORS-32160 2 gigs HD single atlas xp34300wide drive on it. That is where I am getting this same error! I get the same problem with the tyan 825 and an atlas xp34300wide 4.3g drive. > > > > I am getting some messages via dmesg complainting about assertion > > "cp" failed. The server runs fine, and does seem to operate quiet normal > > except from these errors coming from "ncr.c" (error outputs included at > > the end of this email). Should I just start replacing the SCSI subsystem? > > > sd0(ncr0:6:0): COMMAND FAILED (4 28) @f0b65a00. > > assertion "cp" failed: file "../../pci/ncr.c", line 5563 exact same message, big chunks of them, and most of the time the filesystem on that disk gets io errors -- it is used for news mostly. And then I have to reboot to get the filesystem back. > > Oh well, the DORS shows that kind of problem ? and the atlas > > How often do these messages occur ? > > Please try with Tagged Command Queueing disabled: > > # ncrcontrol -s tags=0 did that and other things, not sure, but looks like tags=0 helped. > > and let me know, whether that fixes the problem. > > > I'll have a 53c875 + DORS drive soon, since I want > to use these devices as the base for the reworking > of the NCR driver (addition of Ultra-SCSI support). I'm getting a tekram 875 and a seagate uw drive and will be building up a new system. I will use 2.1.5R and the driver from the tekram site that supports the tekram 390F. They have patch kits there too. Are you going to use any of their stuff? Are you going for just generic support of the 875? Is there any differences with the various 875 implementations that might allow for optimizations? Just curious, I was hoping the problems I was having would be cured in 2.1.5R, but it looks like someone else is having the same problem there too. > > Up to now, I always choose devices that did not > fail, and it seems that the DORS is finally a drive > that I can expect to show errors on my development > system, giving me a chance to understand why a modern > drive does not work correctly with tags ... > > Regards, STefan > -- Craig Shaver (craig@progroup.com) (415)390-0654 Productivity Group POB 60458 Sunnyvale, CA 94088 From owner-freebsd-scsi Fri Aug 30 13:52:30 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21145 for freebsd-scsi-outgoing; Fri, 30 Aug 1996 13:52:30 -0700 (PDT) Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA21115 for ; Fri, 30 Aug 1996 13:52:16 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-15.slip.Uni-Koeln.DE) by FileServ1.MI.Uni-Koeln.DE with SMTP id AA23587 (5.67b/IDA-1.5 for ); Fri, 30 Aug 1996 22:52:05 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id WAA07150; Fri, 30 Aug 1996 22:23:15 +0200 (MET DST) Date: Fri, 30 Aug 1996 22:23:15 +0200 (MET DST) Message-Id: <199608302023.WAA07150@x14.mi.uni-koeln.de> From: Stefan Esser To: "Craig Shaver" Cc: se@zpr.uni-koeln.de (Stefan Esser), scsi@FreeBSD.org Subject: Re: NCR0+IBM DORS-32160 WA0A 2 gigs HD - assertion "cp" failed In-Reply-To: <199608301653.JAA03796@seabass.progroup.com> References: <199608301544.RAA02753@x14.mi.uni-koeln.de> <199608301653.JAA03796@seabass.progroup.com> Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Craig Shaver writes: > > > > > > Brian Wang writes: > > > Hi, > > > > > > I have just put a new mail/dns server online, which has the > > > following configuration: > > > > > > FreeBSD 2.1.5 Release > 2.1.0R > > > P75 CPU + ASUSTPN4 MB (Triton I with 256k pipeline cache) > p133 + 512K > > > 32 megs non-edo RAM > edo > > > 3COM 509 ethernet card > > > Trident PCI video card > > > ASUS SC200 SCSI card (ncr) > I use this board as the first controller and use a tyan 825 board as > a second controller with a > > > IBM DORS-32160 2 gigs HD > single atlas xp34300wide drive on it. That is where I am getting this same > error! > > I get the same problem with the tyan 825 and an atlas xp34300wide 4.3g drive. Hmmm, an Atlas ??? I've tried with any number of tags (upto 32) and heavy load from many processes accessing the disk at a time, and never had a single such error (using a 2GB Atlas). > exact same message, big chunks of them, and most of the time the filesystem > on that disk gets io errors -- it is used for news mostly. And then I have to > reboot to get the filesystem back. The error recovery code has improved a lot after 2.1R. Try to upgrade to 2.1.5R and see whether that makes a difference. > > Please try with Tagged Command Queueing disabled: > > > > # ncrcontrol -s tags=0 > > did that and other things, not sure, but looks like tags=0 helped. Well, the message says the drive can't handle as many tags as the driver tries to use. But the default is 4, and that is by no means a large number of tags. 32 should work with just about every current drive, though I did not actually test this with too many different brands ... > I'm getting a tekram 875 and a seagate uw drive and will be building > up a new system. I will use 2.1.5R and the driver from the tekram site > that supports the tekram 390F. They have patch kits there too. Are you > going to use any of their stuff? Are you going for just generic support > of the 875? Is there any differences with the various 875 implementations > that might allow for optimizations? The 875 allows for many optimizations, and I plan to have the driver take advantage of them. But it is a HUGE effort to do it right. (And since I don't get paid for it, it would be a total waste of time if I did NOT try to do it right ;-) I have received test results from somebody who did FreeBSD tests for Tekram, and who tested my new code which calculates the pre- scaler parameters for the Ultra-SCSI chips. I asked him to post the results, since I consider them very interesting, but he did not do so, and I won't unless I get his permission, since he sent them in private mail. The Tekram driver comes out significantly slower than either the FreeBSD NCR driver, or an AH2940UW, which give quite similar results. The NCR driver can easily be configured to use more or less tags at run-time, and the results with 4, 8 and 16 tags clearly show that 8 tags gives the optimum performance. (The default of 4 tags does make the driver consume less memory, since each tag (== outstanding command) needs some storage to keep the commands parameters. Anyway, if you got the Tekram driver, just do some Bonnie tests (or whatever your benchmark of choice is) and post the results. > Just curious, I was hoping the problems I was having would be cured in > 2.1.5R, but it looks like someone else is having the same problem there > too. Those problems are caused by the drive not supproting as many tags as the driver assumed. Their is code to reduce the number of tags whenever this situation occurs, but I never managed to trigger it (well, I might just try with 256 tags, my Atlas must have some limit :) Justin Gibbs is working on a major refurbishing of the generic SCSI layer, and he is moving most of the tag support code there. This will make it much easier to deal with the situation you are suffereing from. But under 2.1.5, there should be no disruption of service, as you suffer from under 2.1R, because of driver improvements. So just give it a try ... Regards, STefan PS: If you are going to use the 53c875 under 2.1.5R, you'll need the following patch to /sys/pci/ncr.c to correctly set the clock pre-scaler register: Index: ncr.c =================================================================== RCS file: /usr/cvs/src/sys/pci/ncr.c,v retrieving revision 1.37.4.8 diff -C2 -r1.37.4.8 ncr.c *** ncr.c 1996/04/01 00:25:28 1.37.4.8 --- ncr.c 1996/08/30 20:21:14 *************** *** 1195,1199 **** static void ncr_exception (ncb_p np); static void ncr_free_ccb (ncb_p np, ccb_p cp, int flags); ! static void ncr_getclock (ncb_p np); static ccb_p ncr_get_ccb (ncb_p np, u_long flags, u_long t,u_long l); static u_int32_t ncr_info (int unit); --- 1195,1199 ---- static void ncr_exception (ncb_p np); static void ncr_free_ccb (ncb_p np, ccb_p cp, int flags); ! static void ncr_getclock (ncb_p np, u_char scntl3); static ccb_p ncr_get_ccb (ncb_p np, u_long flags, u_long t,u_long l); static u_int32_t ncr_info (int unit); *************** *** 3350,3354 **** */ ! ncr_getclock (np); /* --- 3350,3354 ---- */ ! ncr_getclock (np, INB(nc_scntl3)); /* *************** *** 6779,6785 **** ! static void ncr_getclock (ncb_p np) { ! u_char tbl[5] = {6,2,3,4,6}; u_char f; u_char ns_clock = (1000/NCR_CLOCK); --- 6779,6785 ---- ! static void ncr_getclock (ncb_p np, u_char scntl3) { ! u_char tbl[6] = {6,2,3,4,6,8}; u_char f; u_char ns_clock = (1000/NCR_CLOCK); *************** *** 6788,6792 **** ** Compute the best value for scntl3. */ ! f = (2 * MIN_SYNC_PD - 1) / ns_clock; if (!f ) f=1; --- 6788,6792 ---- ** Compute the best value for scntl3. */ ! /* f = (2 * MIN_SYNC_PD - 1) / ns_clock; if (!f ) f=1; *************** *** 6803,6806 **** --- 6803,6824 ---- printf ("%s: sclk=%d async=%d sync=%d (ns) scntl3=0x%x\n", ncr_name (np), ns_clock, np->ns_async, np->ns_sync, np->rv_scntl3); + */ + + /* + * For now just preserve the BIOS setting ... + */ + + if ((scntl3 & 7) == 0) { + scntl3 = 3; /* assume 40MHz if no value supplied by BIOS */ + } + + np->ns_sync = 25; + np->ns_async = 50; + np->rv_scntl3 = ((scntl3 & 0x7) << 4) -0x20 + (scntl3 & 0x7); + + if (bootverbose) { + printf ("\tinitial value of SCNTL3 = %02x, final = %02x\n", + scntl3, np->rv_scntl3); + } } From owner-freebsd-scsi Fri Aug 30 14:02:22 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA22214 for freebsd-scsi-outgoing; Fri, 30 Aug 1996 14:02:22 -0700 (PDT) Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA22201 for ; Fri, 30 Aug 1996 14:02:18 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-15.slip.Uni-Koeln.DE) by FileServ1.MI.Uni-Koeln.DE with SMTP id AA23715 (5.67b/IDA-1.5 for ); Fri, 30 Aug 1996 23:01:57 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id WAA07233; Fri, 30 Aug 1996 22:48:02 +0200 (MET DST) Date: Fri, 30 Aug 1996 22:48:02 +0200 (MET DST) Message-Id: <199608302048.WAA07233@x14.mi.uni-koeln.de> From: Stefan Esser To: "Justin T. Gibbs" Cc: Stefan Esser , Brian Wang , freebsd-scsi@FreeBSD.ORG Subject: Re: NCR0+IBM DORS-32160 WA0A 2 gigs HD - assertion "cp" failed In-Reply-To: <199608301636.JAA03192@freefall.freebsd.org> References: <199608301544.RAA02753@x14.mi.uni-koeln.de> <199608301636.JAA03192@freefall.freebsd.org> Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs writes: > >Up to now, I always choose devices that did not > >fail, and it seems that the DORS is finally a drive > >that I can expect to show errors on my development > >system, giving me a chance to understand why a modern > >drive does not work correctly with tags ... > > > >Regards, STefan > > These errors are for the QUEUE FULL condition right? I think drives > are allowed to return this even if the cause is temporary. We'll have > to come up with a strategy for when to reduce maxtags on drives that > doesn't penalize drives that do this kind of thing occasionally. Well, the NCR driver tries to do the right thing (reduce the number of tags in case of a QUEUE FULL) but it would never use a higher number again, after it had to cut down on tags use. But as I said before, I'm not sure whether the code works as designed. If you manage to deal with this correctly in your new SCSI code, a better implementation might be possible ... We have the IBM 0662..0664 drives as prime example of a drive that might reject tagged commands in certain situations, but IIRC, they do not return a QUEUE FULL, but a "MIX of tagged and untagged commands" error status. I will be busy with non-BSD stuff again this weekend, so there will be no advances to the NCR driver integration. (Sorry ...) Did you consider putting your changes on a CVS branch in -current ? This would GREATLY reduce the amount of work it takes me to have a development source tree .. Regards, STefan From owner-freebsd-scsi Fri Aug 30 15:16:33 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA01268 for freebsd-scsi-outgoing; Fri, 30 Aug 1996 15:16:33 -0700 (PDT) Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA01192 for ; Fri, 30 Aug 1996 15:16:10 -0700 (PDT) Received: (from craig@localhost) by seabass.progroup.com (8.7.5/8.6.12) id PAA13655 for scsi@FreeBSD.org; Fri, 30 Aug 1996 15:13:40 -0700 (PDT) Message-Id: <199608302213.PAA13655@seabass.progroup.com> Subject: Re: NCR0+IBM DORS-32160 WA0A 2 gigs HD - assertion "cp" failed To: scsi@FreeBSD.org Date: Fri, 30 Aug 1996 15:13:39 -0700 (PDT) From: "Craig Shaver" Reply-To: scsi@FreeBSD.org In-Reply-To: <199608302023.WAA07150@x14.mi.uni-koeln.de> from "Stefan Esser" at Aug 30, 96 10:23:15 pm X-Mailer: ELM [version 2.4 PL25 ME8b] 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 > > > Craig Shaver writes: > > > > > > > > > Brian Wang writes: > > > > Hi, del ... > > I get the same problem with the tyan 825 and an atlas xp34300wide 4.3g drive. > > Hmmm, an Atlas ??? > > I've tried with any number of tags (upto 32) and heavy load > from many processes accessing the disk at a time, and never > had a single such error (using a 2GB Atlas). > I can try some experiments to load different numbers of tags and let you know what happens over time. I'll try 32 tags next. > > > I'm getting a tekram 875 and a seagate uw drive and will be building > > up a new system. I will use 2.1.5R and the driver from the tekram site > > that supports the tekram 390F. They have patch kits there too. Are you > > going to use any of their stuff? Are you going for just generic support > > of the 875? Is there any differences with the various 875 implementations > > that might allow for optimizations? > > The 875 allows for many optimizations, and I plan to have the > driver take advantage of them. But it is a HUGE effort to do > it right. (And since I don't get paid for it, it would be a > total waste of time if I did NOT try to do it right ;-) > Please do take your time, I would rather have a driver that worked well. > I have received test results from somebody who did FreeBSD tests > for Tekram, and who tested my new code which calculates the pre- > scaler parameters for the Ultra-SCSI chips. > > I asked him to post the results, since I consider them very > interesting, but he did not do so, and I won't unless I get his > permission, since he sent them in private mail. > > The Tekram driver comes out significantly slower than either > the FreeBSD NCR driver, or an AH2940UW, which give quite similar > results. The NCR driver can easily be configured to use more or > less tags at run-time, and the results with 4, 8 and 16 tags > clearly show that 8 tags gives the optimum performance. (The > default of 4 tags does make the driver consume less memory, > since each tag (== outstanding command) needs some storage to > keep the commands parameters. > > Anyway, if you got the Tekram driver, just do some Bonnie tests > (or whatever your benchmark of choice is) and post the results. > I have none and have not tried to do any. I will try to find "Bonnie" and run it when I have this setup. (a month or two) I also have available a LDP UW scsi pci board based on the 875. If you need some testing help let me know. So far I have the asus200 (810), tyan (825), ldp (875), and the tekram (875) is on the way. del .... > > But under 2.1.5, there should be no disruption of service, as you > suffer from under 2.1R, because of driver improvements. So just > give it a try ... hmmmm...., I looked through the ncr.c code when I had another problem with the wide drive target ids. I originally set the drive to a target over 7. The boot barfed on it and could not recognize the disk until I put it back down to a target under 8. In the code I noticed that a mask was used for the target that was 7 in some places and 15 in others. Have you tested for targets greater than 7 on any of the 825's or 875's that allow for a dual channel. Just curious. > > Regards, STefan > > PS: If you are going to use the 53c875 under 2.1.5R, you'll need the > following patch to /sys/pci/ncr.c to correctly set the clock > pre-scaler register: Mucho gracias amigo! Have a good vacation! I'll wait to here from you sometime next week I guess ... :) From owner-freebsd-scsi Fri Aug 30 16:54:45 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA08266 for freebsd-scsi-outgoing; Fri, 30 Aug 1996 16:54:45 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA08261; Fri, 30 Aug 1996 16:54:44 -0700 (PDT) Message-Id: <199608302354.QAA08261@freefall.freebsd.org> To: peter cc: freebsd-scsi@FreeBSD.ORG Subject: Putting the "experimental" SCSI system on a branch In-reply-to: Your message of "Fri, 30 Aug 1996 22:48:02 +0200." <199608302048.WAA07233@x14.mi.uni-koeln.de> Date: Fri, 30 Aug 1996 16:54:43 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Did you consider putting your changes on a CVS branch in >-current ? This would GREATLY reduce the amount of work >it takes me to have a development source tree .. > >Regards, STefan I hadn't thought much about this, but it would certainly allow others to contribute to this revamp. Peter, how hard would it be to set this up? -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Fri Aug 30 23:21:03 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA24324 for freebsd-scsi-outgoing; Fri, 30 Aug 1996 23:21:03 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA24316 for ; Fri, 30 Aug 1996 23:21:00 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA22154; Sat, 31 Aug 1996 08:20:58 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27653; Sat, 31 Aug 1996 08:20:57 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id HAA07179; Sat, 31 Aug 1996 07:56:42 +0200 (MET DST) From: J Wunsch Message-Id: <199608310556.HAA07179@uriah.heep.sax.de> Subject: Re: Putting the "experimental" SCSI system on a branch To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sat, 31 Aug 1996 07:56:41 +0200 (MET DST) Cc: peter@freefall.freebsd.org, freebsd-scsi@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199608302354.QAA08261@freefall.freebsd.org> from "Justin T. Gibbs" at "Aug 30, 96 04:54:43 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 As Justin T. Gibbs wrote: > >Did you consider putting your changes on a CVS branch in > >-current ? This would GREATLY reduce the amount of work > >it takes me to have a development source tree .. > I hadn't thought much about this, but it would certainly allow > others to contribute to this revamp. Peter, how hard would it > be to set this up? I think all you need to do is to run easy-import on them, specify an existing module name (sys_scsi), and perform a vendor-branch import. -- 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. ;-)