From owner-freebsd-scsi Mon Jan 5 02:35:06 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA21333 for freebsd-scsi-outgoing; Mon, 5 Jan 1998 02:35:06 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA21289 for ; Mon, 5 Jan 1998 02:34:59 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from aegir.ifi.uio.no (2602@aegir.ifi.uio.no [129.240.64.190]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id LAA27784 for ; Mon, 5 Jan 1998 11:34:56 +0100 (MET) Received: (from dag-erli@localhost) by aegir.ifi.uio.no ; Mon, 5 Jan 1998 11:34:54 +0100 (MET) To: scsi@freebsd.org Subject: Tecmar NS8 Organization: Gutteklubben Terrasse X-url: http://www.ifi.uio.no/~dag-erli/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit From: dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav) Date: 05 Jan 1998 11:34:52 +0100 Message-ID: Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone have any experience with the Tecmar NS8 Travan streamer (or other SCSI Travan streamers)? How reliable is it, and can it really sustain a transfer rate of 1.2 MBps? -- * Finrod (INTJ) * Unix weenie * dag-erli@ifi.uio.no * cellular +47-92835919 * RFC1123: "Be liberal in what you accept, and conservative in what you send" # unzip ; strip ; touch ; finger ; mount ; fsck ; more ; yes ; umount ; sleep From owner-freebsd-scsi Mon Jan 5 12:08:11 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA06682 for freebsd-scsi-outgoing; Mon, 5 Jan 1998 12:08:11 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from base486.home.org (imdave@imdave.pr.mcs.net [205.164.3.77]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA06672 for ; Mon, 5 Jan 1998 12:08:05 -0800 (PST) (envelope-from imdave@mcs.net) Received: (from imdave@localhost) by base486.home.org (8.8.8/8.8.8) id OAA28428 for freebsd-scsi@freebsd.org; Mon, 5 Jan 1998 14:08:00 -0600 (CST) Date: Mon, 5 Jan 1998 14:08:00 -0600 (CST) From: Dave Bodenstab Message-Id: <199801052008.OAA28428@base486.home.org> To: freebsd-scsi@freebsd.org Subject: Is /sys/i386/isa/ncr5380.c supported? Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone know if /sys/i386/isa/ncr5380.c is still supported for the Trantor HA? I cannot get the driver working with 2.2.5. Thanks. Dave Bodenstab imdave@mcs.net From owner-freebsd-scsi Mon Jan 5 17:13:14 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA06474 for freebsd-scsi-outgoing; Mon, 5 Jan 1998 17:13:14 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA06455 for ; Mon, 5 Jan 1998 17:12:49 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt2-101.HiWAAY.net [208.147.148.101]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id TAA22491 for ; Mon, 5 Jan 1998 19:12:03 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id TAA26390 for ; Mon, 5 Jan 1998 19:12:01 -0600 (CST) Message-Id: <199801060112.TAA26390@nospam.hiwaay.net> X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd-scsi@freebsd.org Subject: Backup Exec tape format? From: David Kelly Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Jan 1998 19:12:01 -0600 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A tape arrived at work with some important data on it that we were not able to read with the standard Unix methods. After digging around and reading the tape raw with dd it appears to have been written with Backup Exec for Windows NT. Would you believe a 512-byte block? We don't have any of those and were dumbfounded that somebody thought we could read it. Am looking for two things: 1a) the format of a Backup Exec tape so I could write: 1b) source code to a Backup Exec tape reader the real solution is: 2) a free tar or pax for NT and SCSI DAT/DSS tape drives -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-scsi Tue Jan 6 05:08:53 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA08741 for freebsd-scsi-outgoing; Tue, 6 Jan 1998 05:08:53 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA08733 for ; Tue, 6 Jan 1998 05:08:47 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 1467 invoked by uid 1001); 6 Jan 1998 13:08:39 +0000 (GMT) To: dag-erli@ifi.uio.no Cc: scsi@FreeBSD.ORG Subject: Re: Tecmar NS8 In-Reply-To: Your message of "05 Jan 1998 11:34:52 +0100" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 06 Jan 1998 14:08:39 +0100 Message-ID: <1465.884092119@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Does anyone have any experience with the Tecmar NS8 Travan streamer > (or other SCSI Travan streamers)? How reliable is it, and can it > really sustain a transfer rate of 1.2 MBps? Reliability seems okay so far, but it's a bit early to tell - I've only had mine for a couple of weeks, and only used it for one full backup. With firmware version 6.11 (available from the Tecmar Web site) you can even get it to do WRITE FILEMARKS. As for a sustained transfer rate of 1.2 Mbyte/s - forget it. The raw (uncompressed) max data rate of this drive is 600 kbyte/s. The 1.2 Mbyte/s figure assumes 2:1 compression, which is rather doubtful for real-life data on a sustained basis. I've had one filesystem reach 1 Mbyte/s though (as reported by dump). Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-scsi Tue Jan 6 11:42:11 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA14094 for freebsd-scsi-outgoing; Tue, 6 Jan 1998 11:42:11 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA14080 for ; Tue, 6 Jan 1998 11:42:00 -0800 (PST) (envelope-from gallatin@CS.Duke.EDU) Received: from hurricane.cs.duke.edu (hurricane.cs.duke.edu [152.3.145.1]) by duke.cs.duke.edu (8.8.5/8.8.5) with ESMTP id OAA12981 for ; Tue, 6 Jan 1998 14:41:57 -0500 (EST) Received: (from gallatin@localhost) by hurricane.cs.duke.edu (8.8.4/8.7.3) id OAA17352; Tue, 6 Jan 1998 14:41:57 -0500 (EST) Date: Tue, 6 Jan 1998 14:41:57 -0500 (EST) Message-Id: <199801061941.OAA17352@hurricane.cs.duke.edu> From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-scsi@freebsd.org Subject: painfully slow crashdumps X-Mailer: VM 6.34 under 20.3 XEmacs Lucid Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We've recently begun using FreeBSD (2.2-stable) for OS research. We started out on IDE boxes, but we've just acquired a number of PII's with Adaptec 2940UW SCSI adapters and WD 'Enterprise' 4360 disks. One of the primary drawbacks to using these machines as crash-boxes is that panic()'ing and doing a crashdump takes nearly 5 minutes to complete on a 128MB machine dumping to a scsi disk (yes, less than 500K/sec). Crashdumps take less than 1 minute to complete when dumping to an IDE disk using the on-board IDE controller on these boxes. Running Bonnie on the scsi disks shows a write speed in excess of 4MB/sec. It looks like the conservative approach of dumping 1 page at a time is to blame for these slow crashdumps. As a workaround, I've hacked sddump() to use a static buffer of size N pages, and to copy N pages into this buffer before passing the buffer to the lower levels of the scsi code for writing to the disk. However, I know next to nothing about the scsi programming interface. I randomly chose N=8 (which yields a crashdump in ~50 seconds, or about 2.5MB/sec), but I'm concerned I may run across a hardware combination that cannot handle a transaction this large. Is this a valid concern? How can I determine the maximum transaction a controller/disk can handle at runtime? Thanks in advance for your advice. Oh, if anybody would like a patch to sd.c (1.95.2.5) I'd be happy to provide it. It was a 1/2 hour hack & is probably the wrong thing to do, but it sure makes our panic/reboot cycle faster which was the goal. ;-) ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 From owner-freebsd-scsi Wed Jan 7 10:11:28 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA23324 for freebsd-scsi-outgoing; Wed, 7 Jan 1998 10:11:28 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA23304 for ; Wed, 7 Jan 1998 10:11:14 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id LAA09578; Wed, 7 Jan 1998 11:08:45 -0700 (MST) Date: Wed, 7 Jan 1998 11:08:45 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199801071808.LAA09578@narnia.plutotech.com> To: Andrew Gallatin Subject: Re: painfully slow crashdumps Newsgroups: pluto.freebsd.scsi In-Reply-To: <199801061941.OAA17352@hurricane.cs.duke.edu> cc: scsi@FreeBSD.org User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In article <199801061941.OAA17352@hurricane.cs.duke.edu> you wrote: > However, I know next to nothing about the scsi programming interface. > I randomly chose N=8 (which yields a crashdump in ~50 seconds, or > about 2.5MB/sec), but I'm concerned I may run across a hardware > combination that cannot handle a transaction this large. Is this a > valid concern? How can I determine the maximum transaction a > controller/disk can handle at runtime? This information will be available with the CAM SCSI code. The idea is to allow peripheral drivers (like the disk driver) to determine the most efficient I/O size for the device, a size that does not need to be coalessed before being sent to the device. In this way, the disk driver, which has more flexibility in how it writes things, can be smart about what it does, but for devices like tapes, where you have to write the whole block in one go, the bus_dma system will take care of coalessing the data. It would be nice to make dumps over 16MB work on ISA busmastering controllers too, so perhaps dump should attempt to "steal" a portion of the bounce buffer area. Since interrupts are disabled, held bounce buffer resources will not be freed, so you'd have to do something to ensure you get the resources you need. > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 -- Justin T. Gibbs =========================================== FreeBSD - Turning PCs into workstations =========================================== From owner-freebsd-scsi Wed Jan 7 19:28:43 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA18757 for freebsd-scsi-outgoing; Wed, 7 Jan 1998 19:28:43 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA18752 for ; Wed, 7 Jan 1998 19:28:40 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id UAA11199; Wed, 7 Jan 1998 20:26:21 -0700 (MST) Date: Wed, 7 Jan 1998 20:26:21 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199801080326.UAA11199@narnia.plutotech.com> To: Aaron Benner Subject: Re: AIC7880P Newsgroups: pluto.freebsd.stable In-Reply-To: cc: scsi@FreeBSD.org User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In article you wrote: > I've got a problem, and I need to know if I sliced hairs too thin. > We recently aquired a pair of seagate barracuda 9 gig Ultra Wide scsi > drives, and an adaptec 2940UW (AIC7880P controller chip). You should send these kinds of bug reports to the SCSI list. > I need to know if, as the evidence seems to support, there is enough > difference between the AIC7880 and the AIC7880P for the Ultra Wide > controller to be incompatible with FreeBSD. They both work just fine with FreeBSD. > The current symptom is a hang at the kernel probe, the kernel recognizes > the card as a 2940 with a wide channel, reports the right card status, and > then the "waiting for SCSI devices to settle" just sits there like a lump. Sounds like a termination or cabling problem. Boot with the -v flag and write down everything that gets spit out during the aic7xxx probe. -- Justin T. Gibbs =========================================== FreeBSD - Turning PCs into workstations =========================================== From owner-freebsd-scsi Thu Jan 8 10:05:51 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08680 for freebsd-scsi-outgoing; Thu, 8 Jan 1998 10:05:51 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from news.cioe.com (news.cioe.com [204.248.219.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08655; Thu, 8 Jan 1998 10:05:39 -0800 (PST) (envelope-from steve@news.cioe.com) Received: (from root@localhost) by news.cioe.com (8.8.8/8.8.5) id NAA11593; Thu, 8 Jan 1998 13:05:29 -0500 (EST) Date: Thu, 8 Jan 1998 13:05:29 -0500 (EST) From: Steven Ames Message-Id: <199801081805.NAA11593@news.cioe.com> To: freebsd-questions@freebsd.org Subject: SCSI/Tape problem? Cc: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm encountering a problem that I just can't seem to solve. I have a FreeBSD system that I've been using to backup my network for quite a while. It is using an Adaptec 2940 card and an Exabyte 8205 tape backup. I'm using 'amanda' to do the backups onto 160M tapes. Alrighty... A while back the system started to lock up during the backup process. Also the command 'mt erase' would never terminate. This was on a 2.2.5-STABLE machine. I tried a different controller (still an Adaptec 2940). Same results. Different cable, no change. Different tape drive (Exabyte 8700XL), same results. Today I built a 2.1.7-RELEASE machine and tried it there. Similar results. The 'mt erase' command generates a lot of errors and eventually causes a reboot. I need a solution ASAP as I'm not getting backups until things work. I've also tried this on a 3.0-CURRENT (1/7/98) machine... same results as the 2.2.5 platform. Need help badly! -Steve From owner-freebsd-scsi Thu Jan 8 14:44:47 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA11581 for freebsd-scsi-outgoing; Thu, 8 Jan 1998 14:44:47 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA11565; Thu, 8 Jan 1998 14:44:38 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by iafnl.es.iaf.nl with UUCP id AA20996 (5.67b/IDA-1.5); Thu, 8 Jan 1998 23:44:14 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id WAA03382; Thu, 8 Jan 1998 22:38:46 +0100 (MET) From: Wilko Bulte Message-Id: <199801082138.WAA03382@yedi.iaf.nl> Subject: Re: SCSI/Tape problem? To: steve@news.cioe.com (Steven Ames) Date: Thu, 8 Jan 1998 22:38:46 +0100 (MET) Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG In-Reply-To: <199801081805.NAA11593@news.cioe.com> from "Steven Ames" at Jan 8, 98 01:05:29 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Steven Ames wrote... > I'm encountering a problem that I just can't seem to solve. > I have a FreeBSD system that I've been using to backup my > network for quite a while. It is using an Adaptec 2940 card > and an Exabyte 8205 tape backup. I'm using 'amanda' to do > the backups onto 160M tapes. Alrighty... > > A while back the system started to lock up during the backup > process. Also the command 'mt erase' would never terminate. You might run into some timeout situation. I have an (admittedly somewhat older) 8200 drive and it takes ages to do an erase. > I tried a different controller (still an Adaptec 2940). Same > results. Different cable, no change. Different tape drive > (Exabyte 8700XL), same results. > > Today I built a 2.1.7-RELEASE machine and tried it there. > Similar results. The 'mt erase' command generates a lot of > errors and eventually causes a reboot. > > I need a solution ASAP as I'm not getting backups until > things work. I've also tried this on a 3.0-CURRENT (1/7/98) > machine... same results as the 2.2.5 platform. Why not omit the 'mt erase' altogether? The drive will erase your tape anyhow when you start writing to it from BOT. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' --------------- Support your local daemons: run [Free,Net,Open]BSD Unix -- From owner-freebsd-scsi Thu Jan 8 19:09:18 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA02151 for freebsd-scsi-outgoing; Thu, 8 Jan 1998 19:09:18 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from news.cioe.com (news.cioe.com [204.248.219.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA02128; Thu, 8 Jan 1998 19:09:00 -0800 (PST) (envelope-from steve@news.cioe.com) Received: (from steve@localhost) by news.cioe.com (8.8.8/8.8.5) id UAA00259; Thu, 8 Jan 1998 20:57:03 -0500 (EST) Date: Thu, 8 Jan 1998 20:57:03 -0500 (EST) From: Steven Ames Message-Id: <199801090157.UAA00259@news.cioe.com> To: steve@news.cioe.com, wilko@yedi.iaf.nl Subject: Re: SCSI/Tape problem? Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I'm encountering a problem that I just can't seem to solve. > > I have a FreeBSD system that I've been using to backup my > > network for quite a while. It is using an Adaptec 2940 card > > and an Exabyte 8205 tape backup. I'm using 'amanda' to do > > the backups onto 160M tapes. Alrighty... > > > > A while back the system started to lock up during the backup > > process. Also the command 'mt erase' would never terminate. > > You might run into some timeout situation. I have an (admittedly > somewhat older) 8200 drive and it takes ages to do an erase. > > Why not omit the 'mt erase' altogether? The drive will erase your > tape anyhow when you start writing to it from BOT. Hrm... I was unclear. The 'mt erase' is obviously only a symptom. The backup process still causes my machine to lockup... -Steve From owner-freebsd-scsi Thu Jan 8 23:28:43 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA24335 for freebsd-scsi-outgoing; Thu, 8 Jan 1998 23:28:43 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA24330; Thu, 8 Jan 1998 23:28:27 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id RAA28368; Fri, 9 Jan 1998 17:47:22 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id RAA06150; Fri, 9 Jan 1998 17:47:22 +1030 (CST) (envelope-from grog) Message-ID: <19980109174722.63760@lemis.com> Date: Fri, 9 Jan 1998 17:47:22 +1030 From: Greg Lehey To: Steven Ames Cc: wilko@yedi.iaf.nl, freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI/Tape problem? References: <199801090157.UAA00259@news.cioe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199801090157.UAA00259@news.cioe.com>; from Steven Ames on Thu, Jan 08, 1998 at 08:57:03PM -0500 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Jan 08, 1998 at 08:57:03PM -0500, Steven Ames wrote: >>> I'm encountering a problem that I just can't seem to solve. >>> I have a FreeBSD system that I've been using to backup my >>> network for quite a while. It is using an Adaptec 2940 card >>> and an Exabyte 8205 tape backup. I'm using 'amanda' to do >>> the backups onto 160M tapes. Alrighty... >>> >>> A while back the system started to lock up during the backup >>> process. Also the command 'mt erase' would never terminate. >> >> You might run into some timeout situation. I have an (admittedly >> somewhat older) 8200 drive and it takes ages to do an erase. >> >> Why not omit the 'mt erase' altogether? The drive will erase your >> tape anyhow when you start writing to it from BOT. > > Hrm... I was unclear. The 'mt erase' is obviously only a > symptom. The backup process still causes my machine to lockup... FWIW, I have an 8505XL on a 2940UW (also an Archive DDS changer). I don't have any trouble with them. Admittedly, I'm a diehard tar user, but I can't imagine that's the problem. Are you 100% sure your termination is OK? I've found the 2940 to be very particular. For example, I *could not* get it to work with specific combinations of disks, though I'm sure that there is nothing wrong with the disks. I now have two 2940s in my machine, with some disks on each, and it works fine like that. Greg From owner-freebsd-scsi Fri Jan 9 09:15:29 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA19044 for freebsd-scsi-outgoing; Fri, 9 Jan 1998 09:15:29 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA19019; Fri, 9 Jan 1998 09:15:21 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by iafnl.es.iaf.nl with UUCP id AA00445 (5.67b/IDA-1.5); Fri, 9 Jan 1998 18:15:15 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id IAA09248; Fri, 9 Jan 1998 08:16:59 +0100 (MET) From: Wilko Bulte Message-Id: <199801090716.IAA09248@yedi.iaf.nl> Subject: Re: SCSI/Tape problem? To: steve@news.cioe.com (Steven Ames) Date: Fri, 9 Jan 1998 08:16:59 +0100 (MET) Cc: steve@news.cioe.com, freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG In-Reply-To: <199801090157.UAA00259@news.cioe.com> from "Steven Ames" at Jan 8, 98 08:57:03 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Steven Ames wrote... > > > > I'm encountering a problem that I just can't seem to solve. > > > I have a FreeBSD system that I've been using to backup my > > > network for quite a while. It is using an Adaptec 2940 card > > > and an Exabyte 8205 tape backup. I'm using 'amanda' to do > > > the backups onto 160M tapes. Alrighty... > > > > > > A while back the system started to lock up during the backup > > > process. Also the command 'mt erase' would never terminate. > > > > You might run into some timeout situation. I have an (admittedly > > somewhat older) 8200 drive and it takes ages to do an erase. > > > > Why not omit the 'mt erase' altogether? The drive will erase your > > tape anyhow when you start writing to it from BOT. > > Hrm... I was unclear. The 'mt erase' is obviously only a > symptom. The backup process still causes my machine to lockup... OK, that is obviously wrong. My 2.2.5R box performs dumps just fine on the 8200, as said without doing an mt erase. I do not use Amanda though The drive is hooked up to a NCR810 in my case. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' --------------- Support your local daemons: run [Free,Net,Open]BSD Unix -- From owner-freebsd-scsi Fri Jan 9 10:56:01 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA28639 for freebsd-scsi-outgoing; Fri, 9 Jan 1998 10:56:01 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA28602; Fri, 9 Jan 1998 10:55:48 -0800 (PST) (envelope-from font@Jupiter.Mcs.Net) Received: from Jupiter.Mcs.Net (font@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id MAA00657; Fri, 9 Jan 1998 12:55:43 -0600 (CST) Received: from localhost (font@localhost) by Jupiter.Mcs.Net (8.8.7/8.8.2) with SMTP id MAA19516; Fri, 9 Jan 1998 12:55:43 -0600 (CST) Date: Fri, 9 Jan 1998 12:55:42 -0600 (CST) From: Font To: Greg Lehey cc: Steven Ames , wilko@yedi.iaf.nl, freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI/Tape problem? In-Reply-To: <19980109174722.63760@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I echo Greg Lehey's lack of problems with a 2940UW and an Exabyte 8505 (non-XL for me). Specifically relating to termination, though, I had to change the Exabyte from an external wide connection to an internal narrow connection, because I already had a CD-ROM drive on the internal narrow connector and two WD Enterprise drives on the internal wide connector, and the 2940UW does not support the use of all three connectors at once. Repeat: only two of the three connections can be used at once, and termination should be properly configured for the types of connections used. (Now if I only know what "Sending SDTR!!" meant on boot for the WD drives...) A bug in my MUA causes news.announce.newusers font to be sent to beneficiaries and senders of UCE/SPAM. @ mcs.net Wishes are like dishes. On Fri, 9 Jan 1998, Greg Lehey wrote: > Date: Fri, 9 Jan 1998 17:47:22 +1030 > From: Greg Lehey > To: Steven Ames > Cc: wilko@yedi.iaf.nl, freebsd-questions@FreeBSD.ORG, > freebsd-scsi@FreeBSD.ORG > Subject: Re: SCSI/Tape problem? > > On Thu, Jan 08, 1998 at 08:57:03PM -0500, Steven Ames wrote: > >>> I'm encountering a problem that I just can't seem to solve. > >>> I have a FreeBSD system that I've been using to backup my > >>> network for quite a while. It is using an Adaptec 2940 card > >>> and an Exabyte 8205 tape backup. I'm using 'amanda' to do > >>> the backups onto 160M tapes. Alrighty... > >>> > >>> A while back the system started to lock up during the backup > >>> process. Also the command 'mt erase' would never terminate. > >> > >> You might run into some timeout situation. I have an (admittedly > >> somewhat older) 8200 drive and it takes ages to do an erase. > >> > >> Why not omit the 'mt erase' altogether? The drive will erase your > >> tape anyhow when you start writing to it from BOT. > > > > Hrm... I was unclear.. The 'mt erase' is obviously only a > > symptom. The backup process still causes my machine to lockup... > > FWIW, I have an 8505XL on a 2940UW (also an Archive DDS changer). I > don't have any trouble with them. Admittedly, I'm a diehard tar user, > but I can't imagine that's the problem. > > Are you 100% sure your termination is OK? I've found the 2940 to be > very particular. For example, I *could not* get it to work with > specific combinations of disks, though I'm sure that there is nothing > wrong with the disks. I now have two 2940s in my machine, with some > disks on each, and it works fine like that. > > Greg > From owner-freebsd-scsi Fri Jan 9 14:43:10 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA20909 for freebsd-scsi-outgoing; Fri, 9 Jan 1998 14:43:10 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from hydrogen.nike.efn.org (d182-89.uoregon.edu [128.223.182.89]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20875; Fri, 9 Jan 1998 14:42:53 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id OAA19287; Fri, 9 Jan 1998 14:19:43 -0800 (PST) Message-ID: <19980109141943.49997@hydrogen.nike.efn.org> Date: Fri, 9 Jan 1998 14:19:43 -0800 From: John-Mark Gurney To: Font Cc: Greg Lehey , Steven Ames , wilko@yedi.iaf.nl, freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI/Tape problem? References: <19980109174722.63760@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Font on Fri, Jan 09, 1998 at 12:55:42PM -0600 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Font scribbled this message on Jan 9: > (Now if I only know what "Sending SDTR!!" meant on boot for the WD > drives...) well.. I got that message from the CAM scsi code and my ahc2842... it turns out that the external cable has a pin shoved in, so that it wasn't making contact... when I pulled the pin out, things when back to normal... so check your cabling... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking P.O. Box 5693, 97405 Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-scsi Fri Jan 9 14:44:45 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA21054 for freebsd-scsi-outgoing; Fri, 9 Jan 1998 14:44:45 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA21036; Fri, 9 Jan 1998 14:44:38 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by iafnl.es.iaf.nl with UUCP id AA14762 (5.67b/IDA-1.5); Fri, 9 Jan 1998 23:44:18 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id VAA03013; Fri, 9 Jan 1998 21:57:25 +0100 (MET) From: Wilko Bulte Message-Id: <199801092057.VAA03013@yedi.iaf.nl> Subject: Re: SCSI/Tape problem? To: font@Mcs.Net (Font) Date: Fri, 9 Jan 1998 21:57:24 +0100 (MET) Cc: grog@lemis.com, steve@news.cioe.com, freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG In-Reply-To: from "Font" at Jan 9, 98 12:55:42 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Font wrote... > I echo Greg Lehey's lack of problems with a 2940UW and an Exabyte 8505 > (non-XL for me). Specifically relating to termination, though, I had to > change the Exabyte from an external wide connection to an internal narrow > connection, because I already had a CD-ROM drive on the internal narrow > connector and two WD Enterprise drives on the internal wide connector, and > the 2940UW does not support the use of all three connectors at once. > Repeat: only two of the three connections can be used at once, and > termination should be properly configured for the types of connections > used. > > (Now if I only know what "Sending SDTR!!" meant on boot for the WD > drives...) Wild guess: Synchronous Data Transfer Request ? _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' --------------- Support your local daemons: run [Free,Net,Open]BSD Unix -- From owner-freebsd-scsi Fri Jan 9 16:15:42 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA00286 for freebsd-scsi-outgoing; Fri, 9 Jan 1998 16:15:42 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from smtp2.xs4all.nl (smtp2.xs4all.nl [194.109.6.52]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA00273; Fri, 9 Jan 1998 16:15:35 -0800 (PST) (envelope-from albast@xs4all.nl) Received: from xs2.xs4all.nl (albast@xs2.xs4all.nl [194.109.6.43]) by smtp2.xs4all.nl (8.8.6/XS4ALL) with ESMTP id BAA14748; Sat, 10 Jan 1998 01:15:30 +0100 (CET) Received: (from albast@localhost) by xs2.xs4all.nl (8.8.6/8.8.6) id BAA14850; Sat, 10 Jan 1998 01:15:30 +0100 (MET) From: albast Message-Id: <199801100015.BAA14850@xs2.xs4all.nl> Subject: Any help greatly appreciated To: scsi@FreeBSD.ORG Date: Sat, 10 Jan 1998 01:15:29 +0100 (MET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL25] 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, This week I've had some equipment sent to the US of A. (Every part was in working order) Now there is a problem concerning a quantum SCSI disk, namely a "QUANTUM FIREBALL_TM1080S" This is supposed to be a 2.1 gig drive which worries me because I thought it was supposed to show 2110 instead of 1080.. but I have to rely on what the remote company (I'm not a USA redident) says (searching the quantum site doesn't clearly give information regarding this) They've informed me the drive shows: "sd1(NCR0:1:0): NOT READY asc:4,d5 Vendor Specific ASCQ, FALIURE" and then later on: "sd1: could not get size" I have never encountered these kind of messages before.. There were no problems when I did the installation of FreeBSD, as a "dangerously dedicated" disk. The system was maintained for a week without any problems like these arising at all.. it worked ok before the shipment to the USA. Any help would be greatly appreciated, what's wrong and what can I do about it (if at all possible) ? Does anyone know this drive is really of 2 gig capacity or if there could have been a mixup (1080 sounds like a 1 gig drive to me) ? I know I should have written this stuff down before sending (stupid me!) :-( Thanks in advance, I hope there is someone who is able to help me, Sincerely, Jeroen From owner-freebsd-scsi Fri Jan 9 20:32:40 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA17728 for freebsd-scsi-outgoing; Fri, 9 Jan 1998 20:32:40 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from news.cioe.com (news.cioe.com [204.248.219.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA17717; Fri, 9 Jan 1998 20:32:37 -0800 (PST) (envelope-from steve@news.cioe.com) Received: (from steve@localhost) by news.cioe.com (8.8.8/8.8.5) id XAA23764; Fri, 9 Jan 1998 23:32:47 -0500 (EST) Date: Fri, 9 Jan 1998 23:32:47 -0500 (EST) From: Steven Ames Message-Id: <199801100432.XAA23764@news.cioe.com> To: steve@news.cioe.com, wilko@yedi.iaf.nl Subject: Re: SCSI/Tape problem? Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hrm... I was unclear. The 'mt erase' is obviously only a > > symptom. The backup process still causes my machine to lockup... > > OK, that is obviously wrong. My 2.2.5R box performs dumps just fine on the > 8200, as said without doing an mt erase. I do not use Amanda though Correct. I do not _have_ to do the 'mt erase'. In fact I never do. However... 'mt erase' does not work... and my backup locks up. These are seperate but related issues. Bottom line is _it don't work_. I have tried just about every termination I can think to try. Different cables, different controller (still a 2940) and a different tape drive. It still doesn't work. So something is wrong. Options anyone? -Steve From owner-freebsd-scsi Fri Jan 9 23:00:56 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA27116 for freebsd-scsi-outgoing; Fri, 9 Jan 1998 23:00:56 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from silvia.HIP.Berkeley.EDU (ala-ca34-45.ix.netcom.com [207.93.143.173]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA27106; Fri, 9 Jan 1998 23:00:49 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id XAA06618; Fri, 9 Jan 1998 23:00:36 -0800 (PST) Date: Fri, 9 Jan 1998 23:00:36 -0800 (PST) Message-Id: <199801100700.XAA06618@silvia.HIP.Berkeley.EDU> To: albast@xs4all.nl CC: scsi@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: <199801100015.BAA14850@xs2.xs4all.nl> (message from albast on Sat, 10 Jan 1998 01:15:29 +0100 (MET)) Subject: Re: Any help greatly appreciated From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Now there is a problem concerning a quantum SCSI disk, namely a * "QUANTUM FIREBALL_TM1080S" * * This is supposed to be a 2.1 gig drive which worries me because I thought * it was supposed to show 2110 instead of 1080.. but I have to rely on * what the remote company (I'm not a USA redident) says * (searching the quantum site doesn't clearly give information regarding this) You need to look in the "archive" section. http://www.quantum.com/products/archive/fireball540/ It says the TM1080S is a 1GB drive with SCSI interface. * They've informed me the drive shows: * "sd1(NCR0:1:0): NOT READY asc:4,d5 Vendor Specific ASCQ, FALIURE" * and then later on: * "sd1: could not get size" Sorry, can't help you on that one. Sounds very much like the drive died though. Satoshi From owner-freebsd-scsi Sat Jan 10 00:12:47 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA07594 for freebsd-scsi-outgoing; Sat, 10 Jan 1998 00:12:47 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA07580; Sat, 10 Jan 1998 00:12:42 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id SAA01761; Sat, 10 Jan 1998 18:42:22 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id SAA13613; Sat, 10 Jan 1998 18:42:22 +1030 (CST) (envelope-from grog) Message-ID: <19980110184222.53552@lemis.com> Date: Sat, 10 Jan 1998 18:42:22 +1030 From: Greg Lehey To: Steven Ames Cc: wilko@yedi.iaf.nl, freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI/Tape problem? References: <199801100432.XAA23764@news.cioe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199801100432.XAA23764@news.cioe.com>; from Steven Ames on Fri, Jan 09, 1998 at 11:32:47PM -0500 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Jan 09, 1998 at 11:32:47PM -0500, Steven Ames wrote: >>> Hrm... I was unclear. The 'mt erase' is obviously only a >>> symptom. The backup process still causes my machine to lockup... >> >> OK, that is obviously wrong. My 2.2.5R box performs dumps just fine on the >> 8200, as said without doing an mt erase. I do not use Amanda though > > Correct. I do not _have_ to do the 'mt erase'. In fact I never do. > However... 'mt erase' does not work... and my backup locks up. These > are seperate but related issues. Bottom line is _it don't work_. > > I have tried just about every termination I can think to try. Different > cables, different controller (still a 2940) and a different > tape drive. It still doesn't work. So something is wrong. Options > anyone? What else do you have connected to the string? If there's something else, and you obviously have access to a second controller, try using both controllers, with only the tape connected to the one controller. If that doesn't work, consider your drive options. This was an Exabyte 8505, wasn't it? Exabytes used to have millions of drive options, so much that hardly two drives were the same. Maybe the drive does something that the driver doesn't understand. Greg From owner-freebsd-scsi Sat Jan 10 04:56:54 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA28702 for freebsd-scsi-outgoing; Sat, 10 Jan 1998 04:56:54 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA28686 for ; Sat, 10 Jan 1998 04:56:41 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id NAA00904; Sat, 10 Jan 1998 13:57:26 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id NAA03974; Sat, 10 Jan 1998 13:08:26 +0100 (CET) (envelope-from roberto) Message-ID: <19980110130826.53639@keltia.freenix.fr> Date: Sat, 10 Jan 1998 13:08:26 +0100 From: Ollivier Robert To: scsi@FreeBSD.ORG, albast Subject: Re: Any help greatly appreciated References: <199801100015.BAA14850@xs2.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199801100015.BAA14850@xs2.xs4all.nl>; from albast on Sat, Jan 10, 1998 at 01:15:29AM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3963 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to albast: > Now there is a problem concerning a quantum SCSI disk, namely a > "QUANTUM FIREBALL_TM1080S" The Quantum fireball 1080S is a 1 Gig drive. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Thu Jan 8 00:49:00 CET 1998 From owner-freebsd-scsi Sat Jan 10 06:14:18 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA03592 for freebsd-scsi-outgoing; Sat, 10 Jan 1998 06:14:18 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA03584 for ; Sat, 10 Jan 1998 06:14:08 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id PAA06548 for freebsd-scsi@FreeBSD.ORG; Sat, 10 Jan 1998 15:15:01 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id PAA00296; Sat, 10 Jan 1998 15:07:28 +0100 (CET) (envelope-from roberto) Message-ID: <19980110150728.28270@keltia.freenix.fr> Date: Sat, 10 Jan 1998 15:07:28 +0100 From: Ollivier Robert To: "FreeBSD SCSI Users' list" Subject: ncr CAM code Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3963 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Justin and everyone, I just made a kernel with the new CAM code that includes ncr support and this is what I get with "boot -v". It works (this message is sent with a system running kernel.cam) but I don't understand the messages below... Why are the two 34330W IBM drives running with a speed of 6.6 MB/s while the 32160 is found as an ultra drive at 20 MB/s ? The conner is also found at 3.3 MB/s when it should probably be at 10 MB/s (or I have misunderstood what the numbers say). My current config found by the old code is appended below. New CAM code -=-=-=-=-=-=-=-=- ncr0: rev 0x03 int a irq 9 on pci0.11.0 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM ncr1: rev 0x12 int a irq 11 on pci0.12.0 ncr1: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo ncr1: single-ended, open drain IRQ driver ncr0: restart (scsi reset). ncr1: restart (scsi reset). ncr1: SCSI phase error fixup: CCB address mismatch (0xf07e1400 != 0x00000000) np->nccb = 0xf07e5400 (probe1:ncr1:0:2:0): phase change 6-7 5@004eb5d8 resid=1. (probe1:ncr1:0:2:0): MSG_MESSAGE_REJECT received (2:8). (probe1:ncr1:0:5:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe1:ncr1:0:5:0): ILLEGAL REQUEST asc:49,0 (probe1:ncr1:0:5:0): Invalid message error (probe1:ncr1:0:6:0): MSG_MESSAGE_REJECT received (6:8). sa0 at ncr0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 3.300MB/s transfers pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI2 device pass0: Serial Number B30V0730 pass0: 6.600MB/s transfers (16bit), Tagged Queueing Enabled pass1 at ncr0 bus 0 target 1 lun 0 pass1: Fixed Direct Access SCSI2 device pass1: Serial Number F35P3185 pass1: 6.600MB/s transfers (16bit), Tagged Queueing Enabled pass2 at ncr0 bus 0 target 2 lun 0 pass2: Fixed Direct Access SCSI2 device pass2: Serial Number 5U2Z5754 pass2: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled pass3 at ncr0 bus 0 target 4 lun 0 pass3: Removable Sequential Access SCSI2 device pass3: 3.300MB/s transfers pass4 at ncr1 bus 0 target 2 lun 0 pass4: Fixed Direct Access SCSI2 device pass4: Serial Number EX90VKV pass4: 3.300MB/s transfers pass5 at ncr1 bus 0 target 6 lun 0 pass5: Removable CD-ROM SCSI2 device pass5: 3.300MB/s transfers da12 at ncr1 bus 0 target 2 lun 0 da12: Fixed Direct Access SCSI2 device da12: Serial Number EX90VKV da12: 3.300MB/s transfers da12: 1030MB (2110812 512 byte sectors: 255H 63S/T 131C) Considering FFS root f/s. cd0 at ncr1 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: Serial Number F35P3185 da1: 6.600MB/s transfers (16bit), Tagged Queueing Enabled da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: Serial Number B30V0730 da0: 6.600MB/s transfers (16bit), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: Serial Number 5U2Z5754 da2: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) -=-=-=-=-=-=-=-=- old SCSI code -=-=-=-=-=-=-=-=- ncr0: rev 0x03 int a irq 9 on pci0.11.0 scbus0 at ncr0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: WIDE SCSI (16 bit) enabled sd0: 40.0 MB/s (50 ns, offset 15) 4134MB (8467200 512 byte sectors) sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access sd1: WIDE SCSI (16 bit) enabled sd1: 40.0 MB/s (50 ns, offset 15) 4134MB (8467200 512 byte sectors) sd2 at scbus0 target 2 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access sd2: 20.0 MB/s (50 ns, offset 15) 2063MB (4226725 512 byte sectors) st1 at scbus0 target 4 lun 0 st1: type 1 removable SCSI 2 st1: Sequential-Access density code 0x0, drive empty ncr1: rev 0x12 int a irq 11 on pci0.12.0 scbus1 at ncr1 bus 0 sd12 at scbus1 target 2 lun 0 sd12: type 0 fixed SCSI 2 sd12: Direct-Access sd12: 10.0 MB/s (100 ns, offset 8) 1030MB (2110812 512 byte sectors) st0 at scbus1 target 5 lun 0 st0: type 1 removable SCSI 2 st0: Sequential-Access st0: 5.0 MB/s (200 ns, offset 8) density code 0x13, drive empty -=-=-=-=-=-=-=-=- -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Thu Jan 8 00:49:00 CET 1998 From owner-freebsd-scsi Sat Jan 10 08:40:49 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA15587 for freebsd-scsi-outgoing; Sat, 10 Jan 1998 08:40:49 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA15568 for ; Sat, 10 Jan 1998 08:40:35 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from gjallarhorn.ifi.uio.no (2602@gjallarhorn.ifi.uio.no [129.240.65.40]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id RAA14035 for ; Sat, 10 Jan 1998 17:40:32 +0100 (MET) Received: (from dag-erli@localhost) by gjallarhorn.ifi.uio.no ; Sat, 10 Jan 1998 17:40:32 +0100 (MET) To: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI/Tape problem? References: Organization: Gutteklubben Terrasse X-url: http://www.ifi.uio.no/~dag-erli/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit From: dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav) Date: 10 Jan 1998 17:40:31 +0100 In-Reply-To: Font's message of "Fri, 9 Jan 1998 12:55:42 -0600 (CST)" Message-ID: Lines: 20 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Font writes: > connection, because I already had a CD-ROM drive on the internal narrow > connector and two WD Enterprise drives on the internal wide connector, and > the 2940UW does not support the use of all three connectors at once. > Repeat: only two of the three connections can be used at once, and > termination should be properly configured for the types of connections > used. Of course you can only use two out of three. No matter how you look at it you still have only one SCSI channel, and it can't have three extremities. There's nothing magical about termination though, just leave the adapter setting on "Automatic" and make sure each end of the bus is terminated. -- * Finrod (INTJ) * Unix weenie * dag-erli@ifi.uio.no * cellular +47-92835919 * RFC1123: "Be liberal in what you accept, and conservative in what you send" # unzip ; strip ; touch ; finger ; mount ; fsck ; more ; yes ; umount ; sleep From owner-freebsd-scsi Sat Jan 10 19:20:23 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA01196 for freebsd-scsi-outgoing; Sat, 10 Jan 1998 19:20:23 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA01164 for ; Sat, 10 Jan 1998 19:20:12 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt1-220.HiWAAY.net [208.147.147.220]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id TAA08480; Sat, 10 Jan 1998 19:40:33 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id SAA23436; Sat, 10 Jan 1998 18:34:51 -0600 (CST) Message-Id: <199801110034.SAA23436@nospam.hiwaay.net> X-Mailer: exmh version 2.0.1 12/23/97 To: Steven Ames Cc: freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: SCSI/Tape problem? In-reply-to: Message from Greg Lehey of "Sat, 10 Jan 1998 18:42:22 +1030." <19980110184222.53552@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Jan 1998 18:34:51 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I have tried just about every termination I can think to try. Different > > cables, different controller (still a 2940) and a different > > tape drive. It still doesn't work. So something is wrong. Options > > anyone? > > What else do you have connected to the string? If there's something > else, and you obviously have access to a second controller, try using > both controllers, with only the tape connected to the one controller. > > If that doesn't work, consider your drive options. This was an > Exabyte 8505, wasn't it? Exabytes used to have millions of drive > options, so much that hardly two drives were the same. Maybe the > drive does something that the driver doesn't understand. Ditto. There is an Exabyte firmware version for most every company that has ever purchased an Exabyte tape drive in modest volume. Think the drive in question was an 8205XL? It *might* have flash firmware. If so, the Exabyte home page has downloadable firmware. Problem is you have to upgrade your drive from DOS or Windows. Upgrading Exabyte firmware has solved several problems for me in the past with SGI workstations. Have had such a hassle last month with TTi packaged Exabytes that I dug up a P-90, an ISA ethernet card, 2940A, and put the tape drive on that. Combinded with NIS and NFS, those SGI users are quite happy with the solution. Meanwhile, am still working with TTi to get a solution which allows their Exabytes to connect directly to SGI's. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-scsi Sat Jan 10 19:27:06 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA02732 for freebsd-scsi-outgoing; Sat, 10 Jan 1998 19:27:06 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA02697 for ; Sat, 10 Jan 1998 19:26:50 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id OAA13426; Sat, 10 Jan 1998 14:21:14 -0700 (MST) Date: Sat, 10 Jan 1998 14:21:14 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199801102121.OAA13426@narnia.plutotech.com> To: Ollivier Robert cc: scsi@FreeBSD.org Subject: Re: ncr CAM code Newsgroups: pluto.freebsd.scsi In-Reply-To: <19980110150728.28270@keltia.freenix.fr> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In article <19980110150728.28270@keltia.freenix.fr> you wrote: > Hi Justin and everyone, > I just made a kernel with the new CAM code that includes ncr support and > this is what I get with "boot -v". It works (this message is sent with a > system running kernel.cam) but I don't understand the messages below... > Why are the two 34330W IBM drives running with a speed of 6.6 MB/s while > the 32160 is found as an ultra drive at 20 MB/s ? The conner is also found > at 3.3 MB/s when it should probably be at 10 MB/s (or I have misunderstood > what the numbers say). It looks like I broke wide followed by sync negotiation when I did the port. The 34330Ws are never asked to go sync, so you get the async speed exported by the NCR X 2 reported. I'll have to go scrounge up a wide device I can stick on the 875 I have here to fix it. BTW, the async reporting is done the way it is since some SCSI bus topologies (like fibre channel and SSA) don't have a notion of transfer negotiations. So, the CAM code has a concept of a base transport speed which it will report unless the controller updates the XPT's concept of what negotiated transfer parameters are in effect. As for the conner, I'm not really sure what I did to upset it, but maybe as I look into the first problem I'll understand how it could be left async. My guess is it has something to do with the message reject that is reported, but I don't know from the error message how to tell what message was rejected. It could also be that I screwed up the transfer negotiation events that are supposed to be sent to the XPT layer and that the transfer speeds are really correct. -- Justin T. Gibbs =========================================== FreeBSD - Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat Jan 10 20:03:16 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA07235 for freebsd-scsi-outgoing; Sat, 10 Jan 1998 20:03:16 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA07229 for ; Sat, 10 Jan 1998 20:03:06 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id DAA29811 for scsi@FreeBSD.org; Sun, 11 Jan 1998 03:20:39 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id BAA18818; Sun, 11 Jan 1998 01:35:07 +0100 (CET) (envelope-from roberto) Message-ID: <19980111013507.02400@keltia.freenix.fr> Date: Sun, 11 Jan 1998 01:35:07 +0100 From: Ollivier Robert To: scsi@FreeBSD.org Subject: Re: ncr CAM code References: <19980110150728.28270@keltia.freenix.fr> <199801102121.OAA13426@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199801102121.OAA13426@narnia.plutotech.com>; from Justin T. Gibbs on Sat, Jan 10, 1998 at 02:21:14PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3963 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to Justin T. Gibbs: > It could also be that I screwed up the transfer negotiation events that are > supposed to be sent to the XPT layer and that the transfer speeds are really > correct. Another point, my HP 35480A DAT is not recogized at boot time. It generates an error at the beginning and the driver doesn't initialize it. ncr0: restart (scsi reset). ncr1: restart (scsi reset). ncr1: SCSI phase error fixup: CCB address mismatch (0xf07e1400 != 0x00000000) np ->nccb = 0xf07e5400 (probe1:ncr1:0:2:0): phase change 6-7 5@004eb5d8 resid=1. \ Conner (probe1:ncr1:0:2:0): MSG_MESSAGE_REJECT received (2:8). / CFP-1080S (probe1:ncr1:0:5:0): INQUIRY. CDB: 12 0 0 0 24 0 \ (probe1:ncr1:0:5:0): ILLEGAL REQUEST asc:49,0 | HP 35480A DAT (probe1:ncr1:0:5:0): Invalid message error / (probe1:ncr1:0:6:0): MSG_MESSAGE_REJECT received (6:8). - Sony CDU-415 I rebooted and this time, the second ncr card (SC-200) wasn't recognized at all... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Thu Jan 8 00:49:00 CET 1998 From owner-freebsd-scsi Sat Jan 10 20:29:35 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA10463 for freebsd-scsi-outgoing; Sat, 10 Jan 1998 20:29:35 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from pericles.aipo.gov.au (pericles.aipo.gov.au [202.14.186.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA10441; Sat, 10 Jan 1998 20:29:26 -0800 (PST) (envelope-from Carl.Makin@aipo.gov.au) From: Carl.Makin@aipo.gov.au Received: (from smap@localhost) by pericles.aipo.gov.au (8.8.5/8.6.12) id PAA08707; Sun, 11 Jan 1998 15:28:52 +1100 (EST) X-Authentication-Warning: pericles.aipo.gov.au: smap set sender to using -f Received: from notes.aipo.gov.au(192.3.1.11) by pericles.aipo.gov.au via smap (V2.0) id xma008705; Sun, 11 Jan 98 15:28:43 +1100 Received: by notes.aipo.gov.au(Lotus SMTP MTA v1.05b4 (287.3 12-16-1996)) id 4A256589.001DDEB5 ; Sun, 11 Jan 1998 15:26:15 +1000 X-Lotus-FromDomain: INTERNET To: freebsd-stable@freebsd.org, freebsd-scsi@freebsd.org Message-ID: <4A256589.001DDBEF.00@notes.aipo.gov.au> Date: Sun, 11 Jan 1998 15:23:13 +1000 Subject: seagate.c kernel compile error and sea device problems. Mime-Version: 1.0 Content-type: text/plain; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Under FreeBSD 2.2.5-RELEASE, I get the following error from seagate.c when I compile a kernel. root@brain:/sys/compile/BRAIN$ make cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../.. -I/usr/include -DAPM_BROKEN_STATCLOCK -DIPDIVERT -DNETATALK -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../i386/isa/seagate.c ../../i386/isa/seagate.c:581: warning: no previous prototype for `seaintr' ../../i386/isa/seagate.c: In function `sea_data_output': ../../i386/isa/seagate.c:1111: warning: assignment discards `volatile' from pointer target type ../../i386/isa/seagate.c: In function `sea_data_input': ../../i386/isa/seagate.c:1181: warning: assignment discards `volatile' from pointer target type sh ../../conf/newvers.sh BRAIN -DAPM_BROKEN_STATCLOCK -DIPDIVERT -DNETATALK -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DNFS -DFFS -DINET cc -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../.. -I/usr/include -DAPM_BROKEN_STATCLOCK -DIPDIVERT -DNETATALK -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL -c vers.c loading kernel rearranging symbols text data bss dec hex 1011712 81920 89084 1182716 120bfc root@brain:/sys/compile/BRAIN$ I noticed this as I've been having a few problems with the sea driver driving a TMC-850MEX (Future Domain TMC-950 chip) scsi card and talking to a DEC TZK10 tape drive (QIC-525). I've been getting; Jan 10 21:20:33 brain /kernel: sea0/5/0 data length underflow and the write to tape continues however reading back from the tape often (ie not always but often) fails at the same point as the above error occured. I modified /sys/i386/isa/seagate.c and commented out "BLINDTRANSFERS". It had no noticible effect so then I changed the kernel config file to remove the IRQ and memory address information (it then autodetects memory and uses no IRQ). This seems to have stopped the "data length underflow" errors (limited testing so far). I uncommented the "BLINDTRANSFERS" option and tried again with the autodetect sea0 config line and the errors started again. I'm not overly worried as it seems to be working now and the only thing I have on the sea0 adaptor is the tape drive however I'm not a kernel hacking wizard and I'd like to bring this to the attention to someone who might be! ;) please cc me on any replies to this mail (I'm not on freebsd-scsi). Carl.