From owner-freebsd-scsi Sun Sep 3 6:32:51 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id A86B137B424 for ; Sun, 3 Sep 2000 06:32:47 -0700 (PDT) Received: from ganerc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13VZt4-00060T-02; Sun, 3 Sep 2000 15:32:42 +0200 Received: (from daemon@localhost) by ganerc.mips.inka.de (8.11.0/8.11.0) id e83Cgov30809 for freebsd-scsi@freebsd.org; Sun, 3 Sep 2000 14:42:50 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Keeping a DLT4000 streaming? Date: 3 Sep 2000 14:42:49 +0200 Message-ID: <8oth09$u2b$1@ganerc.mips.inka.de> To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If any of you guys have a DLT4000 (or faster) tape drive, and manage to keep it streaming properly _with compression enabled_, I'd like to know your setup. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 3 6:43:17 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 2BC5137B424 for ; Sun, 3 Sep 2000 06:43:10 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13Va3A-000BjS-00; Sun, 03 Sep 2000 13:43:08 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id PAA00698; Sun, 3 Sep 2000 15:43:43 +0200 (CEST) (envelope-from wkb) Date: Sun, 3 Sep 2000 15:43:43 +0200 From: Wilko Bulte To: Christian Weisgerber Cc: freebsd-scsi@freebsd.org Subject: Re: Keeping a DLT4000 streaming? Message-ID: <20000903154343.E564@freebie.demon.nl> References: <8oth09$u2b$1@ganerc.mips.inka.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <8oth09$u2b$1@ganerc.mips.inka.de>; from naddy@mips.inka.de on Sun, Sep 03, 2000 at 02:42:49PM +0200 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Sep 03, 2000 at 02:42:49PM +0200, Christian Weisgerber wrote: DLTs need data like hungry piranhas to keep streaming ;-) My DLT4000 generally does not stream. It is hooked up to a seperate AH2940UW (you generally don't want your disks on the same SCSI bus). Reportedly using tools like 'team' should help by buffering the data. I have not tried that yet. Obviously the compressibility of the data is a factor as well. See the attached script to get compression and error stats from the drive. In addition there is a mode page setting (at least on DLT7000, but I think 4000 has it too) that selects 'capacity' or 'speed' mode. The drive drops out of compression mode in favor of keeping tape motion streaming. It does so on the fly, based on whether the mode page enables it or not. Wilko > If any of you guys have a DLT4000 (or faster) tape drive, and manage > to keep it streaming properly _with compression enabled_, I'd like > to know your setup. -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dlt_errlog #!/bin/sh # dltinfo: get more information out of your DLT tape drive. # # (C) 1996, Wilko Bulte, wilko@freebsd.org # # Warning: This script has only been tested on a DEC TZ87 & TZ88 DLT # # You need the DLT drive's OEM manual (or similar) to make # sense out of some of the data reported. # Please send any constructive comments by email to wilko@freebsd.org Unit=2 ## camcontrol(8) setup Verbose="-v" TimeOut="-t 3" get_write_error_log() { RetVal=`camcontrol cmd -n sa -u $Unit \ $Verbose \ $Timeout \ -c "4d 0 42 0 0 0 0 0 3f 0" \ -i 63 \ "{skip} *i4 \ {skip} *i4 \ {Corrected errors without substantial delay} i4 \ {skip} *i4 \ {Corrected errors with possible delay } i4 \ {skip} *i4 \ {Total errors } i4 \ {skip} *i4 \ {Total errors corrected } i4 \ {skip} *i4 \ {Total times correction algorithm processed} i4 \ {skip} *i4 \ {Total bytes processed } i8 \ {skip} *i4 \ {Total uncorrected errors } i4" ` set $RetVal echo "--- write errors ---" printf "Corrected errors without substantial delay = %d\n" $1 printf "Corrected errors with possible delay = %d\n" $2 printf "Total errors = %d\n" $3 printf "Total errors corrected = %d\n" $4 printf "Total times correction algorithm processed = %d\n" $5 printf "Total bytes processed = %d\n" $6 printf "Total uncorrected errors = %d\n" $7 } get_read_error_log() { RetVal=`camcontrol cmd -n sa -u $Unit \ $Verbose \ $Timeout \ -c "4d 0 43 0 0 0 0 0 3f 0" \ -i 63 \ "{skip} *i4 \ {skip} *i4 \ {Corrected errors without substantial delay} i4 \ {skip} *i4 \ {Corrected errors with possible delay } i4 \ {skip} *i4 \ {Total errors } i4 \ {skip} *i4 \ {Total errors corrected } i4 \ {skip} *i4 \ {Total times correction algorithm processed} i4 \ {skip} *i4 \ {Total bytes processed } i8 \ {skip} *i4 \ {Total uncorrected errors } i4" ` set $RetVal echo "--- read errors ---" printf "Corrected errors without substantial delay = %d\n" $1 printf "Corrected errors with possible delay = %d\n" $2 printf "Total errors = %d\n" $3 printf "Total errors corrected = %d\n" $4 printf "Total times correction algorithm processed = %d\n" $5 printf "Total bytes processed = %d\n" $6 printf "Total uncorrected errors = %d\n" $7 } get_compression_log() { # Assumption: from the results observed in testing it lookse # like the residual counts are in kBytes (and not # in Mbytes as the TZ87 manual tells us). RetVal=`camcontrol cmd -n sa -u $Unit \ $Verbose \ $Timeout \ -c "4d 0 72 0 0 0 0 0 4c 0" \ -i 76 \ "{skip} *i4 \ {skip } *i4 \ {Read compression ratio (* 100 %) } i2 \ {skip } *i4 \ {Write compression ratio (* 100 %) } i2 \ {skip } *i4 \ {Total host Mbytes reads } i4 \ {skip } *i4 \ {Total host kbytes read residual } i4 \ {skip } *i4 \ {On tape Mbytes read } i4 \ {skip} *i4 \ {On tape kbytes read residual } i4 \ {skip} *i4 \ {Host requested Mbytes written } i4 \ {skip} *i4 \ {Host requested kbytes written residual } i4 \ {skip} *i4 \ {On tape Mbytes written } i4 \ {skip} *i4 \ {On tape kbytes written residual } i4 " ` set $RetVal echo "--- compression statistics ---" printf "Read compression ratio = %d %%\n" $1 printf "Write compression ratio = %d %%\n" $2 printf "Total host Mbytes read = %d\n" $3 printf "Total host kbytes read residual = %d\n" $4 printf "On tape Mbytes read = %d\n" $5 printf "On tape kbytes read residual = %d\n" $6 printf "Host requested Mbytes written = %d\n" $7 printf "Host requested kbytes written residual = %d\n" $8 printf "On tape Mbytes written = %d\n" $9 printf "On tape kbytes written residual = %d\n" $10 } get_read_error_log echo get_write_error_log echo get_compression_log echo --n8g4imXOkfNTN/H1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 3 12:19:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id A786B37B423 for ; Sun, 3 Sep 2000 12:19:33 -0700 (PDT) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id OAA90570; Sun, 3 Sep 2000 14:19:30 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Sun, 3 Sep 2000 14:19:30 -0500 (CDT) From: Chris Dillon To: Christian Weisgerber Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Keeping a DLT4000 streaming? In-Reply-To: <8oth09$u2b$1@ganerc.mips.inka.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 3 Sep 2000, Christian Weisgerber wrote: > If any of you guys have a DLT4000 (or faster) tape drive, and > manage to keep it streaming properly _with compression enabled_, > I'd like to know your setup. Keeping a DLT4000 streaming would be a lot harder than keeping a DDS2/3 drive streaming, but I keep my DDS drive streaming (with no H/W compression, I have to use gzip instead) by using several large 'team' (ports/misc/team) buffers. I currently use five 8MB buffers. A buffer only empties when it is full, so that way only 8MB streamable chunks make it to the drive, even if the disks can't keep all of the buffers full. You might want 32MB at a time or more for a DLT drive that is doing its own compression. I believe I had to modify the team code to get even an 8MB buffer. One disadvantage to using something like team is that the buffers exist entirely in system RAM, so you'll need plenty of free RAM if you want large buffers. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 3 15: 8:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 9409537B43C; Sun, 3 Sep 2000 15:08:47 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA18060; Sun, 3 Sep 2000 18:09:04 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Sun, 3 Sep 2000 18:09:04 -0400 (EDT) From: "Brandon D. Valentine" To: questions@freebsd.org, freebsd-scsi@freebsd.org Subject: AIC7892 / Adaptec 29160 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been having a devil of a time installing 4.1-RELEASE on a machine with a Supermicro 370DL3. The machine has a built in AIC7892 Ultra160 SCSI controller. I've tried LVD, UW, and narrow drives on all three connectors along with different cables and different drives. No combination will be successful. The install always picks a random point during the install of the bin dist to hang. Sometimes if I wait around long enough I will get a panic with SCB errors. To make sure the problem wasn't the SCSI controller I stuck an Adaptec 29160 in one of the 64-bit PCI slots and hooked the drive to that, turning the onboard SCSI controller off in the BIOS. I still receive the same behavior from sysinstall. This leads me to believe it is an issue related to 29160 support in 4.1-RELEASE. I don't have any Ultra160 capable drives but I've tried LVD 80, UW 40, and UN 20 drives on the appropriate connectors. Does anybody. anywhere have any advice on how to get FreeBSD installed on this machine and then how to make sure it's not going to crash in the future? My problem appears very similiar to this one found in the archives but not followed up on: http://www.freebsd.org/cgi/getmsg.cgi?fetch=1702308+1705755+/usr/local/www/db/text/2000/freebsd-questions/20000319.freebsd-questions Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 3 15:32:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from firebat.bushong.net (c128625-a.frmt1.sfba.home.com [24.176.225.90]) by hub.freebsd.org (Postfix) with ESMTP id 67E8E37B424; Sun, 3 Sep 2000 15:32:14 -0700 (PDT) Received: (from dbushong@localhost) by firebat.bushong.net (8.9.3/8.9.3) id PAA84206; Sun, 3 Sep 2000 15:32:08 -0700 (PDT) (envelope-from dbushong) Date: Sun, 3 Sep 2000 15:32:08 -0700 From: David Bushong To: "Brandon D. Valentine" Cc: questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: AIC7892 / Adaptec 29160 Message-ID: <20000903153208.V19901@bushong.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bandix@looksharp.net on Sun, Sep 03, 2000 at 06:09:04PM -0400 X-Floating-Sheep-Port: 0xbaa Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had the exact same problem with the exact same motherboard. I finally gave up at stuck a Tekram DC-390U3 in the box and it's worked like a charm. Obviously, this is not the answer you wanted (I was on a deadline). Also, sadly, I didn't realize that there are two different shapes of 64-bit PCI slots and the 370DL3 only has one shape and the Tekram is the other, so I had to use it as a 32-bit card.. You can find my posts and pondering about possible explanations with a search on either freebsd-scsi or freebsd-stable.. don't remember which. --David Bushong On Sun, Sep 03, 2000 at 06:09:04PM -0400, Brandon D. Valentine wrote: > I've been having a devil of a time installing 4.1-RELEASE on a machine > with a Supermicro 370DL3. The machine has a built in AIC7892 Ultra160 > SCSI controller. I've tried LVD, UW, and narrow drives on all three > connectors along with different cables and different drives. No > combination will be successful. The install always picks a random point > during the install of the bin dist to hang. Sometimes if I wait around > long enough I will get a panic with SCB errors. To make sure the > problem wasn't the SCSI controller I stuck an Adaptec 29160 in one of > the 64-bit PCI slots and hooked the drive to that, turning the onboard > SCSI controller off in the BIOS. I still receive the same behavior from > sysinstall. This leads me to believe it is an issue related to 29160 > support in 4.1-RELEASE. I don't have any Ultra160 capable drives but > I've tried LVD 80, UW 40, and UN 20 drives on the appropriate > connectors. Does anybody. anywhere have any advice on how to get > FreeBSD installed on this machine and then how to make sure it's not > going to crash in the future? My problem appears very similiar to this > one found in the archives but not followed up on: > http://www.freebsd.org/cgi/getmsg.cgi?fetch=1702308+1705755+/usr/local/www/db/text/2000/freebsd-questions/20000319.freebsd-questions > > Brandon D. Valentine > -- > bandix at looksharp.net | bandix at structbio.vanderbilt.edu > "Truth suffers from too much analysis." -- Ancient Fremen Saying > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 3 23:42:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id C526337B422; Sun, 3 Sep 2000 23:42:22 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id CAA21731; Mon, 4 Sep 2000 02:41:55 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Mon, 4 Sep 2000 02:41:55 -0400 (EDT) From: "Brandon D. Valentine" To: David Bushong Cc: questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: AIC7892 / Adaptec 29160 In-Reply-To: <20000903153208.V19901@bushong.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 3 Sep 2000, David Bushong wrote: >I had the exact same problem with the exact same motherboard. I finally >gave up at stuck a Tekram DC-390U3 in the box and it's worked like a charm. >Obviously, this is not the answer you wanted (I was on a deadline). Also, >sadly, I didn't realize that there are two different shapes of 64-bit PCI >slots and the 370DL3 only has one shape and the Tekram is the other, so I >had to use it as a 32-bit card.. You can find my posts and pondering about >possible explanations with a search on either freebsd-scsi or freebsd-stable.. >don't remember which. That's not good news at all for a $500 motherboard or $200 64-bit PCI SCSI controller. I've seen plenty of posts in the archives from people with working 29160s. There's has got to be a fix to my problem. Hopefully somebody out there has an idea. >On Sun, Sep 03, 2000 at 06:09:04PM -0400, Brandon D. Valentine wrote: >> I've been having a devil of a time installing 4.1-RELEASE on a machine >> with a Supermicro 370DL3. The machine has a built in AIC7892 Ultra160 >> SCSI controller. I've tried LVD, UW, and narrow drives on all three >> connectors along with different cables and different drives. No >> combination will be successful. The install always picks a random point >> during the install of the bin dist to hang. Sometimes if I wait around >> long enough I will get a panic with SCB errors. To make sure the >> problem wasn't the SCSI controller I stuck an Adaptec 29160 in one of >> the 64-bit PCI slots and hooked the drive to that, turning the onboard >> SCSI controller off in the BIOS. I still receive the same behavior from >> sysinstall. This leads me to believe it is an issue related to 29160 >> support in 4.1-RELEASE. I don't have any Ultra160 capable drives but >> I've tried LVD 80, UW 40, and UN 20 drives on the appropriate >> connectors. Does anybody. anywhere have any advice on how to get >> FreeBSD installed on this machine and then how to make sure it's not >> going to crash in the future? My problem appears very similiar to this >> one found in the archives but not followed up on: >> http://www.freebsd.org/cgi/getmsg.cgi?fetch=1702308+1705755+/usr/local/www/db/text/2000/freebsd-questions/20000319.freebsd-questions >> >> Brandon D. Valentine >> -- >> bandix at looksharp.net | bandix at structbio.vanderbilt.edu >> "Truth suffers from too much analysis." -- Ancient Fremen Saying >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-scsi" in the body of the message > Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 4 1: 5:19 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from theshell.com (arsenic.theshell.com [63.236.138.5]) by hub.freebsd.org (Postfix) with SMTP id 0A5A837B423 for ; Mon, 4 Sep 2000 01:05:17 -0700 (PDT) Received: (qmail 4662 invoked by uid 500); 4 Sep 2000 08:05:19 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 4 Sep 2000 08:05:19 -0000 Date: Mon, 4 Sep 2000 01:05:19 -0700 (PDT) From: "Barrett G. Lyon" To: "Brandon D. Valentine" Cc: David Bushong , freebsd-scsi@FreeBSD.ORG Subject: Re: AIC7892 / Adaptec 29160 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org | That's not good news at all for a $500 motherboard or $200 64-bit PCI | SCSI controller. I've seen plenty of posts in the archives from people | with working 29160s. There's has got to be a fix to my problem. | Hopefully somebody out there has an idea. I did get the 29160 working with our system but it would crash randomly. We had to remove the card from the system and move to a symbios U2W. I guess it's just a card, but I did get pissed with Adaptec. Maybe it's not their fault, but it is fun to point fingers. -Barrett Barrett G. Lyon http://www.theshell.com http://www.alphalinux.org A corporation is like a tree of monkeys, all the monkeys on top looking down see smiling faces, while all the monkeys looking up see assholes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 4 8:10:29 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from garbanzo.ssesco.com (garbanzo.ssesco.com [192.55.187.34]) by hub.freebsd.org (Postfix) with ESMTP id 3841937B423 for ; Mon, 4 Sep 2000 08:10:12 -0700 (PDT) Received: from ROBIN ([199.199.226.58]) by garbanzo.ssesco.com (8.8.4/8.8.5) with SMTP id KAA17638 for ; Mon, 4 Sep 2000 10:07:00 -0500 Received: by localhost with Microsoft MAPI; Mon, 4 Sep 2000 10:08:50 -0500 Message-ID: <01C01658.1F36EBC0.echriste@ssesco.com> From: Eric Christeson Reply-To: "echriste@ssesco.com" To: "'freebsd-scsi@freebsd.org'" Subject: Problems with tape drive Date: Mon, 4 Sep 2000 10:08:48 -0500 Organization: SSESCO X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been having a problem with my tape drive and I have a solution, I just don't know if it's the correct solution. I'm running 4.1 stable and have a drive that gets recognized as a Tandberg TDC 3800 (see dmesg output that follows) with DC6525 tapes. I have scsi and sa in the kernel and everything set up correctly, but whenever I try to do anything with the tape drive I get an error. $ sudo mt status mt: /dev/nsa0: Invalid argument (sa0:sym0:0:5:0): unable to set fixed blocksize to 1024 I set some debug flags and did some digging through cam/scsi/scsi_sa.c and found that the quirk entry for the Tandberg 3800 doesn't set SA_QUIRK_FIXED or SA_QUIRK_VARIABLE so on line 1978 last_media_blksize gets set to 1024 which in turn causes it to try to set the device blocksize to 1024 around line 2041. I don't know if my drive or media is funky or what, but it wants the blocksize to be 512 and only 512 (or variable). I've gotten around this by setting either SA_QUIRK_FIXED or SA_QUIRK_VARIABLE in the Tandberg 3800 quirk entry. dmesg output: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-STABLE #0: Thu Aug 31 15:06:00 CDT 2000 root@finch.koehntop.net:/usr/obj/usr/src/sys/FINCH Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (179.63-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 snip... sa0 at sym0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers thanks eric Eric J Christeson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 4 13: 4: 8 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.chuckr.org (picnic.chuckr.org [216.254.96.118]) by hub.freebsd.org (Postfix) with ESMTP id EE2DF37B422 for ; Mon, 4 Sep 2000 13:04:05 -0700 (PDT) Received: from localhost (chuckr@localhost) by picnic.chuckr.org (8.9.3/8.9.3) with ESMTP id QAA34254; Mon, 4 Sep 2000 16:03:54 -0400 (EDT) (envelope-from chuckr@picnic.chuckr.org) Date: Mon, 4 Sep 2000 16:03:53 -0400 (EDT) From: Chuck Robey To: "Barrett G. Lyon" Cc: "Brandon D. Valentine" , David Bushong , freebsd-scsi@FreeBSD.ORG Subject: Re: AIC7892 / Adaptec 29160 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 4 Sep 2000, Barrett G. Lyon wrote: > | That's not good news at all for a $500 motherboard or $200 64-bit PCI > | SCSI controller. I've seen plenty of posts in the archives from people > | with working 29160s. There's has got to be a fix to my problem. > | Hopefully somebody out there has an idea. > > I did get the 29160 working with our system but it would crash > randomly. We had to remove the card from the system and move to a symbios > U2W. I guess it's just a card, but I did get pissed with Adaptec. Maybe > it's not their fault, but it is fun to point fingers. I've been watching this thread *very* closely, because I've been unable to get my new IBM ultra160 drive to boot using the 29160. I'd thought that maybe it was a thing that would be fixed by using an IBM-supplied utility to zero the disk, but that's not been the case. I'm reluctantly ready to try another controller now. Does that sound like a reasonable thing to try? Could you give me a recommendation of another controller, and tell me where you bought it? Thanks. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.chuckr.org| electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 4 13:18:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 6A5ED37B422 for ; Mon, 4 Sep 2000 13:18:54 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id QAA26955; Mon, 4 Sep 2000 16:18:27 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Mon, 4 Sep 2000 16:18:26 -0400 (EDT) From: "Brandon D. Valentine" To: Chuck Robey Cc: "Barrett G. Lyon" , David Bushong , freebsd-scsi@FreeBSD.ORG Subject: Re: AIC7892 / Adaptec 29160 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 4 Sep 2000, Chuck Robey wrote: >I've been watching this thread *very* closely, because I've been unable to >get my new IBM ultra160 drive to boot using the 29160. I'd thought that >maybe it was a thing that would be fixed by using an IBM-supplied utility >to zero the disk, but that's not been the case. I'm reluctantly ready to >try another controller now. This is quite frustrating to me. I've never been very impressed with Tekram's offerings or Mylex's scsi-only(buslogic) range. I've always bought Adaptec because they always seem to just work. I can't fathom what could be so different about this card. It's still a 78xx series chip. The same revision of the ahc driver runs flawlessly on my onboard AIC7895s and my AHA2940U 32-bit PCI cards which are in most of my equipment. This motherboard and the 29160 I've got are the first two U160 products I've ever bought. I don't even have U160 drives hooked up to them. This is with standard LVD 80 equipment I'm seeing these problems. It can't be a problem with the recent addition of U160 speeds then. I'm gonna try some current snaps tomorrow and see if they help. If not, would the ahc hackers tell me what info they need from the machine to debug the problem? If this drags out too long I may have to just return the machine and look for something with a different 78xx revision but before I do I'd at least like to get the developers some good info. Let me know. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 4 13:23:44 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front2m.grolier.fr (front2m.grolier.fr [195.36.216.52]) by hub.freebsd.org (Postfix) with ESMTP id 104FF37B423; Mon, 4 Sep 2000 13:23:37 -0700 (PDT) Received: from nas1-120.vlt.club-internet.fr (nas1-120.vlt.club-internet.fr [194.158.100.120]) by front2m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA29080; Mon, 4 Sep 2000 22:23:04 +0200 (MET DST) Date: Mon, 4 Sep 2000 22:05:30 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: David Bushong Cc: "Brandon D. Valentine" , questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: AIC7892 / Adaptec 29160 In-Reply-To: <20000903153208.V19901@bushong.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 3 Sep 2000, David Bushong wrote: > I had the exact same problem with the exact same motherboard. I finally= =20 > gave up at stuck a Tekram DC-390U3 in the box and it's worked like a char= m. > Obviously, this is not the answer you wanted (I was on a deadline). Also= , > sadly, I didn't realize that there are two different shapes of 64-bit PCI > slots and the 370DL3 only has one shape and the Tekram is the other, so I > had to use it as a 32-bit card.. You can find my posts and pondering abo= ut > possible explanations with a search on either freebsd-scsi or freebsd-sta= ble.. > don't remember which. There are actually 3 different PCI card edge connectors types for each BUS width: 1) 5V (only) 2) 3.3V (only) 3) universal (supports either 5V or 3.3V depending on PCI connector type=20 on motherboard) The Supermicro 370DL3/DLE motherboards have two 3.3V 64 bit PCI connectors, but the Tekram DC-390/U3x controllers seem to use a 5V connector. This doesn't fit. This is not due to the SYM53C1010 chip that supports both 3.3V and 5V and thus allows all the 3 types of PCI card connectors (5V, 3.3V and universal). The SYM53C1010-based boards from Symbios/LSI use universal PCI connectors, but they are probably more expensive than Tekram ones. - SYM22915 -> 2 Ultra3 (LVD) SCSI buses - SYM21940 -> 1 Ultra3 (LVD) SCSI bus + 1 UltraWide SCSI bus Thanks to their universal PCI connectors these ones works with both 5V and 3.3V 64 bit PCI connectors on motherboard. =20 G=E9rard. PS1: In my opinion, Tekram choice for the DC-390 U3 PCI board connector couldn't be worse, based on technical considerations. > --David Bushong >=20 > On Sun, Sep 03, 2000 at 06:09:04PM -0400, Brandon D. Valentine wrote: > > I've been having a devil of a time installing 4.1-RELEASE on a machine > > with a Supermicro 370DL3. The machine has a built in AIC7892 Ultra160 > > SCSI controller. I've tried LVD, UW, and narrow drives on all three > > connectors along with different cables and different drives. No > > combination will be successful. The install always picks a random poin= t > > during the install of the bin dist to hang. Sometimes if I wait around > > long enough I will get a panic with SCB errors. To make sure the > > problem wasn't the SCSI controller I stuck an Adaptec 29160 in one of > > the 64-bit PCI slots and hooked the drive to that, turning the onboard > > SCSI controller off in the BIOS. I still receive the same behavior fro= m > > sysinstall. This leads me to believe it is an issue related to 29160 > > support in 4.1-RELEASE. I don't have any Ultra160 capable drives but > > I've tried LVD 80, UW 40, and UN 20 drives on the appropriate > > connectors. Does anybody. anywhere have any advice on how to get > > FreeBSD installed on this machine and then how to make sure it's not > > going to crash in the future? My problem appears very similiar to this > > one found in the archives but not followed up on: > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=3D1702308+1705755+/usr/loca= l/www/db/text/2000/freebsd-questions/20000319.freebsd-questions > >=20 > > Brandon D. Valentine > > --=20 > > bandix at looksharp.net | bandix at structbio.vanderbilt.edu > > "Truth suffers from too much analysis." -- Ancient Fremen Saying > >=20 > >=20 > >=20 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 4 14: 4:30 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front1m.grolier.fr (front1m.grolier.fr [195.36.216.51]) by hub.freebsd.org (Postfix) with ESMTP id 41EF937B42C for ; Mon, 4 Sep 2000 14:04:25 -0700 (PDT) Received: from nas5-244.vlt.club-internet.fr (nas5-244.vlt.club-internet.fr [194.158.107.244]) by front1m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA19729; Mon, 4 Sep 2000 23:03:40 +0200 (MET DST) Date: Mon, 4 Sep 2000 22:46:06 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: "Brandon D. Valentine" Cc: Chuck Robey , "Barrett G. Lyon" , David Bushong , freebsd-scsi@FreeBSD.ORG Subject: Re: AIC7892 / Adaptec 29160 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 4 Sep 2000, Brandon D. Valentine wrote: > On Mon, 4 Sep 2000, Chuck Robey wrote: >=20 > >I've been watching this thread *very* closely, because I've been unable = to > >get my new IBM ultra160 drive to boot using the 29160. I'd thought that > >maybe it was a thing that would be fixed by using an IBM-supplied utilit= y > >to zero the disk, but that's not been the case. I'm reluctantly ready t= o > >try another controller now. >=20 > This is quite frustrating to me. I've never been very impressed with > Tekram's offerings or Mylex's scsi-only(buslogic) range. I've always If by Tekram's offerings you mean SYM53C8XX PCI-SCSI I/O processors based controllers, then the comparison with what you call "Mylex scsi-only" could well be inappropriate. Both the SYM53C8XX and Adaptec aic7xxx have a phase engine. They are kind of half-clever PCI-SCSI I/O processors. They both allow very low-latency SCSI I/Os, but require to implement both the firmware and the software for a given O/S driver. You also must keep in mind that a PCI-SCSI host bus adapter is not only a PCI chip + a software driver. There are lots of other glues that can make difference in reliability and quality. It seems that many people want to buy expensive Adaptec based controllers but only may tolerate extra cheap Symbios based controllers. Btw, during the 5 years I hacked software for Symbios chips, I never discovered the actual reasons that made Symbios based controllers not deserve to be as expensive as Adaptec ones.;-) > bought Adaptec because they always seem to just work. I can't fathom > what could be so different about this card. It's still a 78xx series > chip. The same revision of the ahc driver runs flawlessly on my onboard > AIC7895s and my AHA2940U 32-bit PCI cards which are in most of my > equipment. This motherboard and the 29160 I've got are the first two > U160 products I've ever bought. I don't even have U160 drives hooked up > to them. This is with standard LVD 80 equipment I'm seeing these > problems. It can't be a problem with the recent addition of U160 speeds > then. I'm gonna try some current snaps tomorrow and see if they help. > If not, would the ahc hackers tell me what info they need from the > machine to debug the problem? If this drags out too long I may have to > just return the machine and look for something with a different 78xx > revision but before I do I'd at least like to get the developers some > good info. Let me know. The ahc driver has the best possible maintainer. IMO, you should relax and wait for his reply. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 4 14:39:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front2m.grolier.fr (front2m.grolier.fr [195.36.216.52]) by hub.freebsd.org (Postfix) with ESMTP id AAF9537B449 for ; Mon, 4 Sep 2000 14:39:11 -0700 (PDT) Received: from nas6-50.vlt.club-internet.fr (nas6-50.vlt.club-internet.fr [194.158.108.50]) by front2m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA08678 for ; Mon, 4 Sep 2000 23:39:07 +0200 (MET DST) Date: Mon, 4 Sep 2000 23:21:33 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: freebsd-scsi@FreeBSD.org Subject: New `sym' driver version for testing. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I just made avalaible a new version of the `sym' driver. You can download it from the following URL: http://people.freefall.org/~groudier/sym-1.7.0-20000904.tar.gz There are no new features in this driver version. I just flushed all the simplifications and optimizations I had in mind, prior to adding new functionnalities in the driver. You must be aware that this driver version is still experimental. I haven't yet written the change-log against driver version in -current, but I will do it in a couple of days. The only thing I can say at the moment is that, based on my calculations, the I/O latency should still have won a couple of micro-seconds. People that use stupid `one IO at a time' benchmarks to measure latency must know that a lower latency not always make results of these benchmarks better. If you experience such a weird result, you may, for example manually add some delay in the driver and I bet you will make your stupid benchmark happy. For example, you may hack the driver in that place: (Exemple for 50 micro-second latency) /* * SIM action entry point. */ static void sym_action(struct cam_sim *sim, union ccb *ccb) { -=09int s =3D splcam(); +=09int s; +=09UDELAY(50); +=09s =3D splcam(); =09sym_action1(sim, ccb); =09splx(s); } With some old hardisks, adding a > 100 micro-second latency, can also give best `stupid latency benchmark' results. Btw, donnot run your system with such an ugly hack for real work. ;-) If I ever receive a report that proves that adding latency can make stupid latency benchmarks give better results in some special situation, then I may well try to explain why. :-) G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 4 14:56:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B6F7737B422 for ; Mon, 4 Sep 2000 14:56:12 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA15854; Mon, 4 Sep 2000 14:55:59 -0700 Date: Mon, 4 Sep 2000 14:52:33 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Eric Christeson Cc: "'freebsd-scsi@freebsd.org'" Subject: Re: Problems with tape drive In-Reply-To: <01C01658.1F36EBC0.echriste@ssesco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've been having a problem with my tape drive and I have a solution, I just > don't know if it's the correct solution. I'm running 4.1 stable and have a > drive that gets recognized as a Tandberg TDC 3800 (see dmesg output that > follows) with DC6525 tapes. I have scsi and sa in the kernel and > everything set up correctly, but whenever I try to do anything with the > tape drive I get an error. > > $ sudo mt status > mt: /dev/nsa0: Invalid argument > (sa0:sym0:0:5:0): unable to set fixed blocksize to 1024 Hmm? > > I set some debug flags and did some digging through cam/scsi/scsi_sa.c and > found that the quirk entry for the Tandberg 3800 doesn't set SA_QUIRK_FIXED > or SA_QUIRK_VARIABLE so on line 1978 last_media_blksize gets set to 1024 > which in turn causes it to try to set the device blocksize to 1024 around > line 2041. I don't know if my drive or media is funky or what, but it > wants the blocksize to be 512 and only 512 (or variable). I've gotten > around this by setting either SA_QUIRK_FIXED or SA_QUIRK_VARIABLE in the > Tandberg 3800 quirk entry. Okay. Definite bug. Thanks. Good sleuthing. I believe that it should be SA_QUIRK_FIXED. I keep gettting beat up on whenever I try to make all QIC drives FIXED. DC6525 has to be 512 bytes. That's a fixed thing (cough). I'll clean it up and do the checkins. Thansk again. > > > dmesg output: > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.1-STABLE #0: Thu Aug 31 15:06:00 CDT 2000 > root@finch.koehntop.net:/usr/obj/usr/src/sys/FINCH > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium Pro (179.63-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x619 Stepping = 9 > > snip... > > sa0 at sym0 bus 0 target 5 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 3.300MB/s transfers > > thanks > eric > > Eric J Christeson > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 4 17:56:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 6731E37B423 for ; Mon, 4 Sep 2000 17:56:52 -0700 (PDT) Received: from ganerc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13W72g-0001nw-06; Tue, 5 Sep 2000 02:56:50 +0200 Received: (from daemon@localhost) by ganerc.mips.inka.de (8.11.0/8.11.0) id e850rX498800 for freebsd-scsi@freebsd.org; Tue, 5 Sep 2000 02:53:33 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Keeping a DLT4000 streaming? Date: 5 Sep 2000 02:53:33 +0200 Message-ID: <8p1g6d$30f2$1@ganerc.mips.inka.de> References: <8oth09$u2b$1@ganerc.mips.inka.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chris Dillon wrote: > I keep my DDS drive streaming [...] by using several large 'team' > (ports/misc/team) buffers. I currently use five 8MB buffers. A > buffer only empties when it is full, so that way only 8MB streamable > chunks make it to the drive, even if the disks can't keep all of the > buffers full. You might want 32MB at a time or more for a DLT drive I've played around with this, and it just doesn't work. The team processes fill up their buffers at 8.0+MB/s, then they feed the data slowly at ~2.8MB/s or so to the tape drive. "iostat -d 1" shows that there are periods with no disk I/O at all. Apparently the team processes have filled their buffers and are waiting (while one is slowly feeding). I'm increasingly getting the impression that the DLT is simply not capable of accepting the data sufficiently fast from the SCSI bus. If the disk couldn't keep up with the tape, I would expect to see short bursts of maximum I/O on the tape bus (approaching 10MB/s), when a team process emptied its buffer. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 4 17:57: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 5D82E37B422 for ; Mon, 4 Sep 2000 17:56:52 -0700 (PDT) Received: from ganerc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13W72g-0001nw-05; Tue, 5 Sep 2000 02:56:50 +0200 Received: (from daemon@localhost) by ganerc.mips.inka.de (8.11.0/8.11.0) id e850TVo98222 for freebsd-scsi@freebsd.org; Tue, 5 Sep 2000 02:29:31 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Keeping a DLT4000 streaming? Date: 5 Sep 2000 02:29:30 +0200 Message-ID: <8p1epa$2vt5$1@ganerc.mips.inka.de> References: <8oth09$u2b$1@ganerc.mips.inka.de> <20000903154343.E564@freebie.demon.nl> To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte wrote: > DLTs need data like hungry piranhas to keep streaming ;-) I know. I'm prepared to shove as much down its throat as it will take, but somehow this fish doesn't want to swallow. > My DLT4000 generally does not stream. It is hooked up to a seperate > AH2940UW (you generally don't want your disks on the same SCSI > bus). Reportedly using tools like 'team' should help by buffering > the data. I have not tried that yet. I transfer single large files (complete filesystem dumps) from a holding disk to tape. The DLT4000 is on its own narrow/fast-10 bus (Sym810A), the disk is on a different wide/fast-20 bus (Sym875). Reading from the disk to /dev/null gives me ~8MB/s. I have used buffer(1) from the beginning, then tried team(1) as well. Tried different blocksizes, up to 64kB and multiples thereof. With compression _disabled_ the DLT streams along happily at 1.4MB/s, as shown by iostat(8). With compression _enabled_, it keeps backhitching. Average transfer rate, and in fact also the transfer rate for the short periods between stops when it is streaming, is ~2.7MB/s (as per "iostat -d 1"), give or take some, but under 3.0MB/s. > See the attached script to get compression and error stats from > the drive. I'll try this. > In addition there is a mode page setting (at least on DLT7000, > but I think 4000 has it too) that selects 'capacity' or 'speed' > mode. Details? The manual extensively documents the available mode page settings, and there is no mention of such an option. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 4 21:31:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 17BB737B422 for ; Mon, 4 Sep 2000 21:31:23 -0700 (PDT) Received: from ganerc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13WAOI-0001p9-00; Tue, 5 Sep 2000 06:31:22 +0200 Received: (from daemon@localhost) by ganerc.mips.inka.de (8.11.0/8.11.0) id e851bX801687 for freebsd-scsi@freebsd.org; Tue, 5 Sep 2000 03:37:33 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Keeping a DLT4000 streaming? Date: 5 Sep 2000 03:37:32 +0200 Message-ID: <8p1ios$1kc$1@ganerc.mips.inka.de> References: <8oth09$u2b$1@ganerc.mips.inka.de> <20000903154343.E564@freebie.demon.nl> To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte wrote: > Obviously the compressibility of the data is a factor as well. > See the attached script to get compression and error stats from > the drive. I just tried this: 323% write compression ratio, ~96.4M from host, ~29.0M to tape. So why don't I see a steady throughput of ~5M/s? -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 4 23:57:41 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from gilgamesch.bik-gmbh.de (T1-Hansenet.BIK-GmbH.de [192.76.134.246]) by hub.freebsd.org (Postfix) with ESMTP id A6ED937B422 for ; Mon, 4 Sep 2000 23:57:36 -0700 (PDT) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id IAA38241; Tue, 5 Sep 2000 08:56:50 +0200 (MET DST) Date: Tue, 5 Sep 2000 08:56:50 +0200 From: Martin Cracauer To: Chris Dillon Cc: Christian Weisgerber , freebsd-scsi@FreeBSD.ORG Subject: Re: Keeping a DLT4000 streaming? Message-ID: <20000905085650.A37471@cons.org> References: <8oth09$u2b$1@ganerc.mips.inka.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from cdillon@wolves.k12.mo.us on Sun, Sep 03, 2000 at 02:19:30PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In , Chris Dillon wrote: > On 3 Sep 2000, Christian Weisgerber wrote: > > > If any of you guys have a DLT4000 (or faster) tape drive, and > > manage to keep it streaming properly _with compression enabled_, > > I'd like to know your setup. > > Keeping a DLT4000 streaming would be a lot harder than keeping a > DDS2/3 drive streaming, but I keep my DDS drive streaming (with no H/W > compression, I have to use gzip instead) by using several large 'team' > (ports/misc/team) buffers. I currently use five 8MB buffers. A > buffer only empties when it is full, so that way only 8MB streamable > chunks make it to the drive, even if the disks can't keep all of the > buffers full. You might want 32MB at a time or more for a DLT drive > that is doing its own compression. I believe I had to modify the team > code to get even an 8MB buffer. I wrote ports/misc/cstream partly for this purpose. Using -B and -c you get buffering without size restrictions. Some of the -c modes are - while being well-tested - experimental, so be sure to check results if you want to use it for backup purposes. cstream also has data sinks and generators for quasi-random ascii data which would be useful to isolate the problem. Feedback welcome, of course. While we are at it, I'm having a different problem with my DTL. It writes 2.4 -3.0 MB/sec at 32kb blocksize, but it reads only 1 MB/sec. At smaller blocksizes I get get both reading and writing at 1.5 MB/sec. These tests are done with without using the filesystem, just one userspace program. Any idea what could make reading slower than writing? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 5 1:25: 7 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from racine.cybercable.fr (racine.cybercable.fr [212.198.0.201]) by hub.freebsd.org (Postfix) with SMTP id A1BB037B42C for ; Tue, 5 Sep 2000 01:25:04 -0700 (PDT) Received: (qmail 11124635 invoked from network); 5 Sep 2000 08:25:02 -0000 Received: from r203m230.cybercable.tm.fr (HELO ?195.132.203.230?) ([195.132.203.230]) (envelope-sender ) by racine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 5 Sep 2000 08:25:02 -0000 X-Mailer: Microsoft Outlook Express Macintosh Edition - 4.5 (0410) Date: Tue, 05 Sep 2000 10:27:37 +0200 Subject: scsi controller mac From: "Serge Thierry-Mieg" To: controllercards@egroups.fr Mime-version: 1.0 X-Priority: 3 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Message-Id: <20000905082504.A1BB037B42C@hub.freebsd.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I need an U2W controller for Mac 80Mo/s je cherche une carte SCSI U2W pour Mac freeserge@cybercable.fr 33 (1) 42 71 48 44 06 86 43 06 95 (france) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 5 1:31:53 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 9083E37B423 for ; Tue, 5 Sep 2000 01:31:51 -0700 (PDT) Received: (qmail 10912457 invoked from network); 5 Sep 2000 08:31:49 -0000 Received: from r203m230.cybercable.tm.fr (HELO ?195.132.203.230?) ([195.132.203.230]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 5 Sep 2000 08:31:49 -0000 X-Mailer: Microsoft Outlook Express Macintosh Edition - 4.5 (0410) Date: Tue, 05 Sep 2000 10:34:24 +0200 Subject: scsi controller mac From: "Serge Thierry-Mieg" To: controllercards@egroups.fr Mime-version: 1.0 X-Priority: 3 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Message-Id: <20000905083151.9083E37B423@hub.freebsd.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I need an U2W controller for Mac 80Mo/s je cherche une carte SCSI U2W pour Mac freeserge@cybercable.fr 33 (1) 42 71 48 44 06 86 43 06 95 (france) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 5 2:56:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f241.pav1.hotmail.com [64.4.31.241]) by hub.freebsd.org (Postfix) with ESMTP id D3E8637B422 for ; Tue, 5 Sep 2000 02:56:28 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 5 Sep 2000 02:56:28 -0700 Received: from 61.151.185.78 by pv1fd.pav1.hotmail.msn.com with HTTP; Tue, 05 Sep 2000 09:56:28 GMT X-Originating-IP: [61.151.185.78] From: "bsdnewbie bsdnewbie" To: freebsd-scsi@FreeBSD.org Subject: _Problem of KLD Date: Tue, 05 Sep 2000 17:56:28 CST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 05 Sep 2000 09:56:28.0662 (UTC) FILETIME=[8F93B160:01C0171F] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I write a driver for a pci scsi card. In order to make my driver easy for debugging, I write it as a loadable module. But it can not work well, so I compile it into kernel and things get better. The problem is: why the loadable module can not work as it compiled in to the kernel. (described as follows:) I write my program by referring "aic7xxx.c" My program: /* * Attach all the sub-devices we can find */ int foo_attach(struct foo_softc *foo) { ... bus_setup_intr(...); devq = cam_simq_alloc(SCB_MAX); sim = cam_sim_alloc(foo_action, foo_poll, "foo", foo, foo->unit, 1, SCB_MAX, devq); xpt_bus_register(sim, bus_id); xpt_create_path(&path, /*periph*/NULL, cam_sim_path(sim), CAM_TARGET_WILDCARD, CAM_LUN_WILDCARD); ... } 1) When I use "kldload foo.ko", the function foo_action will be called with the "ccb->ccb_h.func_code == XPT_PATH_INQ" only one time. And no function will be called by system any more. 2) When I compile this module into kernel, the function foo_action will be called with the func_code in order: XPT_PATH_INQ XPT_PATH_INQ XPT_PATH_INQ XPT_RESET_BUS XPT_PATH_INQ XPT_PATH_INQ XPT_PATH_INQ XPT_SCSI_IO detail log of situation 1: /kernel: foo: -> foo_pci_attach /kernel: foo: <-> foo_setup /kernel: foo: <-> foo_alloc /kernel: foo: <-> foo_reset /kernel: foo: <-> foo_init /kernel: foo: -> foo_attach /kernel: (noperiph:foo0:0:-1:-1): xpt_compile_path /kernel: (noperiph:foo0:0:-1:-1): xpt_setup_ccb /kernel: (noperiph:foo0:0:-1:-1): xpt_action /kernel: foo: -> foo_action /kernel: (noperiph:foo0:0:-1:-1): foo_action /kernel: foo: XPT_PATH_INQ /kernel: (noperiph:foo0:0:-1:-1): xpt_done /kernel: foo: <- foo_action /kernel: (xpt0:xpt0:0:-1:-1): xpt_async /kernel: (noperiph:foo0:0:-1:-1): xpt_release_path /kernel: (noperiph:foo0:0:-1:-1): xpt_compile_path /kernel: (noperiph:foo0:0:-1:-1): xpt_setup_ccb /kernel: (noperiph:foo0:0:-1:-1): xpt_action /kernel: foo: <- foo_attach /kernel: foo: <- foo_pci_attach detail log of 2: (displayed by dmesg) Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-RELEASE #4: Tue Sep 5 15:27:11 CST 2000 bsdnewbie@TPA.MyHome.com:/usr/src/sys/compile/NEW2 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (666.45-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 134217728 (131072K bytes) config> di pcic0 config> di sn0 config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 126468096 (123504K bytes) Preloaded elf kernel "kernel" at 0xc03fd000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03fd09c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 10 at device 7.2 on pc i0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port 1 power on failed, IOERROR uhub0: port 2 power on failed, IOERROR xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd800-0xd87f mem 0xea020000-0xea02 007f irq 12 at device 10.0 on pci0 xl0: Ethernet address: 00:10:5a:75:79:6a miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto foo0: port 0xec00-0xec3f,0xe800-0xe803,0xe400-0xe407,0xe000-0xe003 ,0xdc00-0xdc07 mem 0xea000000-0xea01ffff irq 9 at device 11.0 on pci0 foo: -> foo_pci_attach foo: <-> foo_setup foo: <-> foo_alloc foo: <-> foo_reset foo: <-> foo_init foo: -> foo_attach foo: -> foo_action foo: XPT_PATH_INQ foo: <- foo_action foo: <- foo_attach foo: <- foo_pci_attach pcib1: on motherboard pci2: on pcib1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ad0: 14649MB [29765/16/63] at ata0-master using UDMA66 acd0: CDROM at ata1-master using PIO4 (noperiph:foo0:0:-1:-1): xpt_compile_path (noperiph:foo0:0:-1:-1): xpt_setup_ccb (noperiph:foo0:0:-1:-1): xpt_action foo: -> foo_action (noperiph:foo0:0:-1:-1): foo_action foo: XPT_PATH_INQ (noperiph:foo0:0:-1:-1): xpt_done foo: <- foo_action (noperiph:foo0:0:-1:-1): xpt_release_path Waiting 15 seconds for SCSI devices to settle (xpt0:foo0:0:-1:-1): xpt_compile_path (xpt0:foo0:0:-1:-1): xpt_setup_ccb (xpt0:foo0:0:-1:-1): xpt_action foo: -> foo_action (xpt0:foo0:0:-1:-1): foo_action foo: XPT_PATH_INQ (xpt0:foo0:0:-1:-1): xpt_done foo: <- foo_action (xpt0:foo0:0:-1:-1): xpt_setup_ccb (xpt0:foo0:0:-1:-1): xpt_action foo: -> foo_action (xpt0:foo0:0:-1:-1): foo_action foo: XPT_RESET_BUS foo: <-> foo_reset (xpt0:foo0:0:-1:-1): xpt_done foo: <- foo_action (xpt0:foo0:0:-1:-1): xpt_finishconfig (xpt0:foo0:0:-1:-1): xpt_action (xpt0:foo0:0:-1:-1): xpt_scan_bus (xpt0:foo0:0:-1:-1): xpt_setup_ccb (xpt0:foo0:0:-1:-1): xpt_action foo: -> foo_action (xpt0:foo0:0:-1:-1): foo_action foo: XPT_PATH_INQ (xpt0:foo0:0:-1:-1): xpt_done foo: <- foo_action (xpt0:foo0:0:1:0): xpt_compile_path (xpt0:foo0:0:1:0): xpt_setup_ccb (xpt0:foo0:0:1:0): xpt_action (xpt0:foo0:0:1:0): xpt_scan_lun (xpt0:foo0:0:1:0): xpt_setup_ccb (xpt0:foo0:0:1:0): xpt_action foo: -> foo_action (xpt0:foo0:0:1:0): foo_action foo: XPT_PATH_INQ (xpt0:foo0:0:1:0): xpt_done foo: <- foo_action (probe0:foo0:0:1:0): xpt_compile_path (probe0:foo0:0:1:0): xpt_setup_ccb (probe0:foo0:0:1:0): xpt_action (probe0:foo0:0:1:0): xpt_setup_ccb (probe0:foo0:0:1:0): xpt_action (probe0:foo0:0:1:0): xpt_setup_ccb (probe0:foo0:0:1:0): xpt_action foo: -> foo_action (probe0:foo0:0:1:0): foo_action foo: XPT_PATH_INQ (probe0:foo0:0:1:0): xpt_done foo: <- foo_action (probe0:foo0:0:1:0): xpt_schedule (probe0:foo0:0:1:0): xpt_setup_ccb (probe0:foo0:0:1:0): probestart (probe0:foo0:0:1:0): xpt_action (probe0:foo0:0:1:0): . CDB: 12 0 0 0 24 0 foo: -> foo_action (probe0:foo0:0:1:0): foo_action foo: XPT_SCSI_IO (probe0:foo0:0:1:0): xpt_done foo: <- foo_action (probe0:foo0:0:1:0): camisr(probe0:foo0:0:1:0): probedone (xpt0:foo0:0:1:0): xpt_done (probe0:foo0:0:1:0): xpt_free_path (probe0:foo0:0:1:0): xpt_release_path (xpt0:foo0:0:1:0): camisr(xpt0:foo0:0:1:0): xpt_scan_bus (xpt0:foo0:0:1:0): xpt_setup_ccb (xpt0:foo0:0:1:0): xpt_action (xpt0:foo0:0:1:0): xpt_free_path (xpt0:foo0:0:1:0): xpt_release_path (xpt0:foo0:0:-1:-1): xpt_done (xpt0:foo0:0:-1:-1): camisr(xpt0:foo0:0:-1:-1): xpt_finishconfig (xpt0:foo0:0:-1:-1): xpt_free_path (xpt0:foo0:0:-1:-1): xpt_release_path (noperiph:xpt0:0:-1:-1): xpt_compile_path (noperiph:xpt0:0:-1:-1): xpt_setup_ccb (noperiph:xpt0:0:-1:-1): xpt_action (noperiph:xpt0:0:-1:-1): xpt_free_path (noperiph:xpt0:0:-1:-1): xpt_release_path (noperiph:xpt0:0:-1:-1): xpt_compile_path (noperiph:xpt0:0:-1:-1): xpt_setup_ccb (noperiph:xpt0:0:-1:-1): xpt_action (noperiph:xpt0:0:-1:-1): xpt_free_path (noperiph:xpt0:0:-1:-1): xpt_release_path (noperiph:xpt0:0:-1:-1): xpt_compile_path (noperiph:xpt0:0:-1:-1): xpt_setup_ccb (noperiph:xpt0:0:-1:-1): xpt_action (noperiph:xpt0:0:-1:-1): xpt_free_path (noperiph:xpt0:0:-1:-1): xpt_release_path (noperiph:xpt0:0:-1:-1): xpt_compile_path (noperiph:xpt0:0:-1:-1): xpt_setup_ccb (noperiph:xpt0:0:-1:-1): xpt_action (noperiph:xpt0:0:-1:-1): xpt_free_path (noperiph:xpt0:0:-1:-1): xpt_release_path Mounting root from ufs:/dev/ad0s2a I wanna to know why 1) and 2) runs in different way? How can I made 1) run just as that of 2)? I notice that in the source code of FreeBSD 4.1, aha is writen as a loadable module while ahc is writen to compiled into the kernel, why? Thanks in Advance, Best Regards, bsdnewbie Sep 5, 2k _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 6 6:50:56 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 71C6937B423 for ; Wed, 6 Sep 2000 06:50:51 -0700 (PDT) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.10.1/8.10.1) with ESMTP id e86Dm9o18178; Wed, 6 Sep 2000 15:48:09 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail3.siemens.de (8.11.0/8.11.0) with ESMTP id e86Dm806908550; Wed, 6 Sep 2000 15:48:08 +0200 (MEST) Received: (from localhost) by curry.mchp.siemens.de (8.11.0/8.11.0) id e86Dm8o39921; Date: Wed, 6 Sep 2000 15:48:08 +0200 From: Andre Albsmeier To: Wilko Bulte Cc: Christian Weisgerber , freebsd-scsi@FreeBSD.ORG Subject: Re: Keeping a DLT4000 streaming? Message-ID: <20000906154808.A62407@curry.mchp.siemens.de> References: <8oth09$u2b$1@ganerc.mips.inka.de> <20000903154343.E564@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000903154343.E564@freebie.demon.nl>; from wkb@freebie.demon.nl on Sun, Sep 03, 2000 at 03:43:43PM +0200 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 03-Sep-2000 at 15:43:43 +0200, Wilko Bulte wrote: > DLTs need data like hungry piranhas to keep streaming ;-) My DLT4000 generally > does not stream. It is hooked up to a seperate AH2940UW (you generally don't > want your disks on the same SCSI bus). Reportedly using tools like 'team' > should help by buffering the data. I have not tried that yet. Obviously > the compressibility of the data is a factor as well. See the attached script > to get compression and error stats from the drive. In addition there is a > mode page setting (at least on DLT7000, but I think 4000 has it too) that > selects 'capacity' or 'speed' mode. The drive drops out of compression mode > in favor of keeping tape motion streaming. It does so on the fly, based > on whether the mode page enables it or not. > > Wilko Thanks for the great script! One thing: The line printf "On tape kbytes written residual = %d\n" $10 should probably be something like shift printf "On tape kbytes written residual = %d\n" $9 Otherwise, it works great. -Andre > > > If any of you guys have a DLT4000 (or faster) tape drive, and manage > > to keep it streaming properly _with compression enabled_, I'd like > > to know your setup. > > -- > Wilko Bulte wilko@freebsd.org > Arnhem, the Netherlands > #!/bin/sh > > # dltinfo: get more information out of your DLT tape drive. > # > # (C) 1996, Wilko Bulte, wilko@freebsd.org > # > # Warning: This script has only been tested on a DEC TZ87 & TZ88 DLT > # > # You need the DLT drive's OEM manual (or similar) to make > # sense out of some of the data reported. > > # Please send any constructive comments by email to wilko@freebsd.org > > Unit=2 > > ## camcontrol(8) setup > Verbose="-v" > TimeOut="-t 3" > > get_write_error_log() { > > RetVal=`camcontrol cmd -n sa -u $Unit \ > $Verbose \ > $Timeout \ > -c "4d 0 42 0 0 0 0 0 3f 0" \ > -i 63 \ > "{skip} *i4 \ > {skip} *i4 \ > {Corrected errors without substantial delay} i4 \ > {skip} *i4 \ > {Corrected errors with possible delay } i4 \ > {skip} *i4 \ > {Total errors } i4 \ > {skip} *i4 \ > {Total errors corrected } i4 \ > {skip} *i4 \ > {Total times correction algorithm processed} i4 \ > {skip} *i4 \ > {Total bytes processed } i8 \ > {skip} *i4 \ > {Total uncorrected errors } i4" > ` > set $RetVal > echo "--- write errors ---" > printf "Corrected errors without substantial delay = %d\n" $1 > printf "Corrected errors with possible delay = %d\n" $2 > printf "Total errors = %d\n" $3 > printf "Total errors corrected = %d\n" $4 > printf "Total times correction algorithm processed = %d\n" $5 > printf "Total bytes processed = %d\n" $6 > printf "Total uncorrected errors = %d\n" $7 > } > > get_read_error_log() { > > RetVal=`camcontrol cmd -n sa -u $Unit \ > $Verbose \ > $Timeout \ > -c "4d 0 43 0 0 0 0 0 3f 0" \ > -i 63 \ > "{skip} *i4 \ > {skip} *i4 \ > {Corrected errors without substantial delay} i4 \ > {skip} *i4 \ > {Corrected errors with possible delay } i4 \ > {skip} *i4 \ > {Total errors } i4 \ > {skip} *i4 \ > {Total errors corrected } i4 \ > {skip} *i4 \ > {Total times correction algorithm processed} i4 \ > {skip} *i4 \ > {Total bytes processed } i8 \ > {skip} *i4 \ > {Total uncorrected errors } i4" > ` > set $RetVal > echo "--- read errors ---" > printf "Corrected errors without substantial delay = %d\n" $1 > printf "Corrected errors with possible delay = %d\n" $2 > printf "Total errors = %d\n" $3 > printf "Total errors corrected = %d\n" $4 > printf "Total times correction algorithm processed = %d\n" $5 > printf "Total bytes processed = %d\n" $6 > printf "Total uncorrected errors = %d\n" $7 > > } > > get_compression_log() { > > # Assumption: from the results observed in testing it lookse > # like the residual counts are in kBytes (and not > # in Mbytes as the TZ87 manual tells us). > > RetVal=`camcontrol cmd -n sa -u $Unit \ > $Verbose \ > $Timeout \ > -c "4d 0 72 0 0 0 0 0 4c 0" \ > -i 76 \ > "{skip} *i4 \ > {skip } *i4 \ > {Read compression ratio (* 100 %) } i2 \ > {skip } *i4 \ > {Write compression ratio (* 100 %) } i2 \ > {skip } *i4 \ > {Total host Mbytes reads } i4 \ > {skip } *i4 \ > {Total host kbytes read residual } i4 \ > {skip } *i4 \ > {On tape Mbytes read } i4 \ > {skip} *i4 \ > {On tape kbytes read residual } i4 \ > {skip} *i4 \ > {Host requested Mbytes written } i4 \ > {skip} *i4 \ > {Host requested kbytes written residual } i4 \ > {skip} *i4 \ > {On tape Mbytes written } i4 \ > {skip} *i4 \ > {On tape kbytes written residual } i4 " > ` > set $RetVal > echo "--- compression statistics ---" > printf "Read compression ratio = %d %%\n" $1 > printf "Write compression ratio = %d %%\n" $2 > printf "Total host Mbytes read = %d\n" $3 > printf "Total host kbytes read residual = %d\n" $4 > printf "On tape Mbytes read = %d\n" $5 > printf "On tape kbytes read residual = %d\n" $6 > printf "Host requested Mbytes written = %d\n" $7 > printf "Host requested kbytes written residual = %d\n" $8 > printf "On tape Mbytes written = %d\n" $9 > printf "On tape kbytes written residual = %d\n" $10 > > } > > get_read_error_log > echo > get_write_error_log > echo > get_compression_log > echo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 6 10:25: 6 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp1.andrew.cmu.edu (SMTP1.ANDREW.CMU.EDU [128.2.10.81]) by hub.freebsd.org (Postfix) with ESMTP id AAF3337B423 for ; Wed, 6 Sep 2000 10:25:04 -0700 (PDT) Received: from unix11.andrew.cmu.edu (UNIX11.ANDREW.CMU.EDU [128.2.15.15]) by smtp1.andrew.cmu.edu (8.9.3/8.9.3) with SMTP id NAA11801 for ; Wed, 6 Sep 2000 13:25:02 -0400 (EDT) Date: Wed, 6 Sep 2000 13:25:03 -0400 (EDT) From: Gregory C Schohn To: freebsd-scsi@freebsd.org Subject: new - uncooperative seagate hard drives Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi - I just bought a pair of 18GB HDs (a cheetah 10KRPM & a barracuda). I've been able to lay partitions down in dos & solaris86 - but I've had no luck even correctly reading the partition table. Each time, I get try reading the parition, fdisk complains of an invalid partition table. I've gone through fdisk many times now to build some partitions & each time the disk light flickers, & there are no complaints, but when I go back - the table is untouched (& still has an invalid magic). so - I saw that some people where having problems w/ newer scsi drives & adaptec controllers (I have a 2940U2W). One workaround was to disable the write cache. I tried doing this w/ camcontrol modepage da2 -m 8 -e -P [1234] & WCE never showed up in the editor (though it did when I just listed contents). When I added it, camcontrol complained w/ camcontrol: modepage entry "WCE" is read-only; skipping. interestingly the WCE flag is set to 0 (though on my ibm hd it is set to 1, so I was presuming that the values were flipped). the drives are pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number LP7294430000114024TQ pass1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled & pass2: Fixed Direct Access SCSI-2 device pass2: Serial Number LCC47151000021400@Y1 pass2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled does anybody know if (a) these drives could be susceptible to the firmware bug that was discussed back in July or (b) if so, how can I edit the WCE flag? any help would be very much appreciated... thanks, Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 6 15:35: 6 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from zero.arkaine.com (zero.arkaine.com [206.217.210.40]) by hub.freebsd.org (Postfix) with ESMTP id 2F65637B423; Wed, 6 Sep 2000 15:35:01 -0700 (PDT) Received: from exsrv.arkaine.com (exsrv.arkaine.com [192.168.10.10]) by zero.arkaine.com (8.9.3/8.9.3) with ESMTP id SAA40321; Wed, 6 Sep 2000 18:22:10 -0500 (EST) (envelope-from andre@arkaine.com) Received: by exsrv.arkaine.com with Internet Mail Service (5.5.2650.21) id ; Wed, 6 Sep 2000 18:46:12 -0400 Message-ID: From: Andre Chang To: "'freebsd-smp@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: SMP and AMI RAID controller Date: Wed, 6 Sep 2000 18:46:11 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I'm having a problem installing a SMP kernel with a certain RAID controller. The controller drivers are fairly new and I'm hoping that people from SMP or SCSI lists may shed s ome light :) First I'll list the system configuration and info: hardware: Intel PR440FX MB (onboard SCSI, LAN) 2 Intel PPro 200 CPU's (same _ numbers) 1 128MB EDO DIMM 1 Intel Pro 10/100 NIC 1 matrox SVGA card 1 AMI MEGARAID 466 RAID w 16MB EDO chip 2 2GB HDD (RAID 1 -mirroring- config) 1 floppy 1 2GB HDD for testing with onboard controller (not in final system) software: FreeBSD ZERO.akwc.net 4.1-RELEASE FreeBSD 4.1-RELEASE #0: Thu Jul 27 04:44:16 GMT 2000 root@usw4.freebsd.org:/usr/src/sys/compile/GENERIC i386 I reverted to testing the release where the fixed amr drivers were available. TESTING A: I've tested doing a FTP install onto the mirrored HDD's of the AMI controller, 4.1-RELEASE and booting the machine. This works fine. When I build a kernel that is the same as GENERIC except for commenting out the following two lines: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O the machine gets to this point and hangs forever, sometimes locking the machine: Waiting 15 seconds for SCSI devices to settle no devsw (majdev=0 bootdev=0xa0200000) Mounting root from ufs:/dev/amrd0s1a TESTING B: I've done the exact same as "TESTING A:" but used the spare 2GB HDD on the onboard controller as the install and boot drive (while leaving the AMI controller in the system) and the system boots. Thoughts: I cant figure out if its the kernel or the drivers for the AMI RAID controller. I'm leaning towards the amr driver but how does SMP affect that? Any help would be greatly appreciated. Thanks :) -- Andre. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 7 7:58:24 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp3.andrew.cmu.edu (SMTP3.ANDREW.CMU.EDU [128.2.10.83]) by hub.freebsd.org (Postfix) with ESMTP id D69B737B423 for ; Thu, 7 Sep 2000 07:58:22 -0700 (PDT) Received: from unix11.andrew.cmu.edu (UNIX11.ANDREW.CMU.EDU [128.2.15.15]) by smtp3.andrew.cmu.edu (8.9.3/8.9.3) with SMTP id KAA16068 for ; Thu, 7 Sep 2000 10:58:20 -0400 (EDT) Date: Thu, 7 Sep 2000 10:58:21 -0400 (EDT) From: Gregory C Schohn To: freebsd-scsi@freebsd.org Subject: RE: new - uncooperative seagate hard drives Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi - everybody can ignore the email that I sent yesterday. A long time ago parity checking was turned off in the scsi controller. When I turned it back on, I had errors galore. After removing the drives from there external case & trying again - the drives now work fine :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 7 21:29:45 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 3A7EE37B423; Thu, 7 Sep 2000 21:29:39 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id AAA65604; Fri, 8 Sep 2000 00:29:38 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Fri, 8 Sep 2000 00:29:38 -0400 (EDT) From: "Brandon D. Valentine" To: scsi@freebsd.org Cc: gibbs@freebsd.org Subject: Supermicro 370DL3 owners, good news! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, most of you followed my thread[0] several days ago concerning problems installing 4.1-RELEASE on a Supermicro 370DL3 w/ AIC7892. Quite a few of you wrote back speaking of your own woes with the same board or other 7892 based U160 controllers, particularly 29160s. After much playing today I found a driver revision which worked and allowed me to do a full install of FreeBSD. It took making quite a few current snapshot install floppy sets before I found a working revision. I just kept looking through commit logs for src/sys/dev/aic7xxx/* until I found a good date to get the snapshot on. Here's my uname: moby# uname -a FreeBSD moby.structbio.vanderbilt.edu 5.0-20000827-CURRENT FreeBSD 5.0-20000827-CURRENT #0: Sun Aug 27 12:36:38 GMT 2000 root@usw2.freebsd.org:/usr/src/sys/compile/GENERIC i386 If those of you having trouble with this hardware would try running this current snap or backporting the 1.47 revision of aic7xxx.c and the other aic7xxx files involved in that commit it would help constitute a good review for MFC. I'd like to get Justin to MFC his latest version of the driver ASAP, hint hint. I'm going to try running bonnie and/or rawio overnight and make sure I've got proof that the driver is good and stable on my hardware. [0] http://docs.freebsd.org/cgi/getmsg.cgi?fetch=10386+0+current/freebsd-scsi Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 8 5:40:14 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id 3729837B423 for ; Fri, 8 Sep 2000 05:40:12 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e88Cdik14137 for ; Fri, 8 Sep 2000 09:39:45 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Sep 2000 09:39:44 -0300 (ADT) From: The Hermit Hacker To: freebsd-scsi@freebsd.org Subject: bad drive or bad termination? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just looking for an opinion on this error message: Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): WRITE(06). CDB: a 14 89 0 80 0 Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): WRITE(06). CDB: a 14 89 0 80 0 Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): ABORTED COMMAND info:148900 asc:47,0 Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): ABORTED COMMAND info:148900 asc:47,0 Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): SCSI parity error field replaceable unit: 3 Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): SCSI parity error field replaceable unit: 3 bad drive sort of error messsage, or bad scsi termination? or really not able to determine from the error? :( thanks ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 8 10: 6:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3F4BB37B43E for ; Fri, 8 Sep 2000 10:06:08 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA01057; Fri, 8 Sep 2000 10:06:02 -0700 Date: Fri, 8 Sep 2000 10:02:22 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: The Hermit Hacker Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: bad drive or bad termination? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bad cable maybe? > > Just looking for an opinion on this error message: > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): WRITE(06). CDB: a 14 89 0 80 0 > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): WRITE(06). CDB: a 14 89 0 80 0 > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): ABORTED COMMAND info:148900 asc:47,0 > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): ABORTED COMMAND info:148900 asc:47,0 > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): SCSI parity error field replaceable unit: 3 > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): SCSI parity error field replaceable unit: 3 > > bad drive sort of error messsage, or bad scsi termination? or really not able > to determine from the error? :( > > thanks ... > > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 8 12:18:42 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 6FEAB37B422 for ; Fri, 8 Sep 2000 12:18:39 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13XTfW-0006yc-00 for freebsd-scsi@freebsd.org; Fri, 08 Sep 2000 19:18:34 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e88JJMu61015 for freebsd-scsi@freebsd.org; Fri, 8 Sep 2000 21:19:22 +0200 (CEST) (envelope-from wkb) Date: Fri, 8 Sep 2000 21:19:21 +0200 From: Wilko Bulte To: freebsd-scsi@freebsd.org Subject: suggestion for camcontrol Message-ID: <20000908211921.A49085@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Would it be difficult for camcontrol to display the initiator ID of the hostadapter in addition to the devices in the output of devlist? Today: miata#camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 2 lun 0 (pass2,da2) Suggested example: miata#camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 2 lun 0 (pass2,da2) at scbus0 target 7 I'm currently playing with shared SCSI buses and in situations like that it is really practical if you can get a display of the complete SCSI bus. Wilko -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 8 12:19:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B2E9237B422 for ; Fri, 8 Sep 2000 12:19:29 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA01472; Fri, 8 Sep 2000 12:19:22 -0700 Date: Fri, 8 Sep 2000 12:15:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: suggestion for camcontrol In-Reply-To: <20000908211921.A49085@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've thought this would be a very desirable feature myself. > Would it be difficult for camcontrol to display the initiator ID of the > hostadapter in addition to the devices in the output of devlist? > > Today: > > miata#camcontrol devlist > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > at scbus0 target 2 lun 0 (pass2,da2) > > Suggested example: > > miata#camcontrol devlist > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > at scbus0 target 2 lun 0 (pass2,da2) > at scbus0 target 7 > > I'm currently playing with shared SCSI buses and in situations like that it > is really practical if you can get a display of the complete SCSI bus. > > Wilko > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 8 12:45:29 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id EB76037B443 for ; Fri, 8 Sep 2000 12:45:25 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA20930; Fri, 8 Sep 2000 13:45:20 -0600 (MDT) (envelope-from ken) Date: Fri, 8 Sep 2000 13:45:20 -0600 From: "Kenneth D. Merry" To: Wilko Bulte Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: suggestion for camcontrol Message-ID: <20000908134520.A20744@panzer.kdm.org> References: <20000908211921.A49085@freebie.demon.nl> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000908211921.A49085@freebie.demon.nl>; from wkb@freebie.demon.nl on Fri, Sep 08, 2000 at 09:19:21PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Sep 08, 2000 at 21:19:21 +0200, Wilko Bulte wrote: > Would it be difficult for camcontrol to display the initiator ID of the > hostadapter in addition to the devices in the output of devlist? > > Today: > > miata#camcontrol devlist > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > at scbus0 target 2 lun 0 (pass2,da2) > > Suggested example: > > miata#camcontrol devlist > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > at scbus0 target 2 lun 0 (pass2,da2) > at scbus0 target 7 > > I'm currently playing with shared SCSI buses and in situations like that it > is really practical if you can get a display of the complete SCSI bus. Well, the initiator isn't currently included in the CAM EDT, and I'm not sure that it would be the right thing to do that. You'd need the initiator to be in the EDT in order for printing it with 'camcontrol devlist' to just work. (Well, it wouldn't quite "just work", you might need some additional printing logic.) The most likely place for that information to go would be the Path Inquiry CCB. In fact, the initiator ID is already in that CCB, it just isn't displayed by 'camcontrol negotiate da0 -v'. I've attached a patch to do that, here's what you get: # ./camcontrol negotiate da0 -v Current Parameters: (pass0:ahc0:0:0:0): sync parameter: 12 (pass0:ahc0:0:0:0): frequency: 20.000MHz (pass0:ahc0:0:0:0): offset: 8 (pass0:ahc0:0:0:0): bus width: 16 bits (pass0:ahc0:0:0:0): disconnection is enabled (pass0:ahc0:0:0:0): tagged queueing is enabled ahc0: SIM/HBA version: 1 ahc0: supports tag queue messages ahc0: supports SDTR message ahc0: supports 16 bit wide SCSI ahc0: HBA engine count: 0 ahc0: maximum target: 15 ahc0: maximum LUN: 64 ahc0: highest path ID in subsystem: 0 ahc0: initiator ID: 7 ahc0: SIM vendor: FreeBSD ahc0: HBA vendor: Adaptec ahc0: bus ID: 0 ahc0: base transfer speed: 3.300MB/sec As far as putting it in the devlist output, we could kludge some of the information in there, but the adapter model number isn't currently included in the path inquiry. It might be possible to add a new node type into the EDT, or perhaps to represent the initiator as a target device, but that would require adding target matching capability. We could add the initiator as a regular device (lun), but it wouldn't have many of the things associated with a lun/device node, like inquiry data. Anyway, the bottom line is that it can be done, but doing it in a clean manner isn't trivial. I think it would need some discussion to figure out whether there should be a node for the initiator in the EDT, and if so, what sort of node it should be. Ken -- Kenneth Merry ken@kdm.org --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="camcontrol.c.initiator_id.20000908" ==== //depot/FreeBSD-ken/src/sbin/camcontrol/camcontrol.c#14 - /a/ken/perforce/FreeBSD-ken/src/sbin/camcontrol/camcontrol.c ==== *** /tmp/tmp.20855.0 Fri Sep 8 13:29:32 2000 --- /a/ken/perforce/FreeBSD-ken/src/sbin/camcontrol/camcontrol.c Fri Sep 8 13:26:28 2000 *************** *** 2307,2312 **** --- 2307,2314 ---- cpi->max_lun); fprintf(stdout, "%s highest path ID in subsystem: %d\n", adapter_str, cpi->hpath_id); + fprintf(stdout, "%s initiator ID: %d\n", adapter_str, + cpi->initiator_id); fprintf(stdout, "%s SIM vendor: %s\n", adapter_str, cpi->sim_vid); fprintf(stdout, "%s HBA vendor: %s\n", adapter_str, cpi->hba_vid); fprintf(stdout, "%s bus ID: %d\n", adapter_str, cpi->bus_id); --k+w/mQv8wyuph6w0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 8 13: 4:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id 8E61D37B43F for ; Fri, 8 Sep 2000 13:04:36 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e88K3tY21343; Fri, 8 Sep 2000 17:03:55 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Sep 2000 17:03:54 -0300 (ADT) From: The Hermit Hacker To: Matthew Jacob Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: bad drive or bad termination? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Okay, more on this (hadn't thought about cabling, thanks, will look at that on Monday) ... First off, this drive used to be the root drive of the system for the past year or so, running Solaris7/x86, with no problems. We recently removed a drive out off that bus, moved the root drive to da2 and installed a new 9gig as root drive, with FreeBSD ... I seem to be able to very easily recreate the bug ... the machine is used as a news server, using INN and its cyclic buffers ... on da3, if I use dd to create a new buffer, after a period of time (2+gig into creating ~3.9gig buffer, those 6 lines will pop onto the screen. The build will eventually finish, with no more errors being produced ... during "normal operation", I don't see those errors popping up ... on Monday, I'll try to build on da4 and see if I can force the errors to happen again, but am wondering if maybe that makes a difference? Still sound like cabling, or maybe something else? On Fri, 8 Sep 2000, Matthew Jacob wrote: > > Bad cable maybe? > > > > > > Just looking for an opinion on this error message: > > > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): WRITE(06). CDB: a 14 89 0 80 0 > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): WRITE(06). CDB: a 14 89 0 80 0 > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): ABORTED COMMAND info:148900 asc:47,0 > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): ABORTED COMMAND info:148900 asc:47,0 > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): SCSI parity error field replaceable unit: 3 > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): SCSI parity error field replaceable unit: 3 > > > > bad drive sort of error messsage, or bad scsi termination? or really not able > > to determine from the error? :( > > > > thanks ... > > > > > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy > > Systems Administrator @ hub.org > > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 8 14:54: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 87BA837B424 for ; Fri, 8 Sep 2000 14:53:57 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA02077; Fri, 8 Sep 2000 14:53:55 -0700 Date: Fri, 8 Sep 2000 14:50:15 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: The Hermit Hacker Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: bad drive or bad termination? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Check for onboard termination, etc., being set? Double termination can also do this to you. Hmm. It's the dpt, eh? I would hope it's generating parity correctly. Can't vouch... > > Okay, more on this (hadn't thought about cabling, thanks, will look at > that on Monday) ... > > First off, this drive used to be the root drive of the system for the past > year or so, running Solaris7/x86, with no problems. We recently removed a > drive out off that bus, moved the root drive to da2 and installed a new > 9gig as root drive, with FreeBSD ... > > I seem to be able to very easily recreate the bug ... the machine is used > as a news server, using INN and its cyclic buffers ... on da3, if I use dd > to create a new buffer, after a period of time (2+gig into creating > ~3.9gig buffer, those 6 lines will pop onto the screen. The build will > eventually finish, with no more errors being produced ... during "normal > operation", I don't see those errors popping up ... on Monday, I'll try to > build on da4 and see if I can force the errors to happen again, but am > wondering if maybe that makes a difference? Still sound like cabling, or > maybe something else? > > > On Fri, 8 Sep 2000, Matthew Jacob wrote: > > > > > Bad cable maybe? > > > > > > > > > > Just looking for an opinion on this error message: > > > > > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): WRITE(06). CDB: a 14 89 0 80 0 > > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): WRITE(06). CDB: a 14 89 0 80 0 > > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): ABORTED COMMAND info:148900 asc:47,0 > > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): ABORTED COMMAND info:148900 asc:47,0 > > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): SCSI parity error field replaceable unit: 3 > > > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): SCSI parity error field replaceable unit: 3 > > > > > > bad drive sort of error messsage, or bad scsi termination? or really not able > > > to determine from the error? :( > > > > > > thanks ... > > > > > > > > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy > > > Systems Administrator @ hub.org > > > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 8 14:58:19 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7EECE37B423 for ; Fri, 8 Sep 2000 14:58:16 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA02094; Fri, 8 Sep 2000 14:57:50 -0700 Date: Fri, 8 Sep 2000 14:54:09 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Wilko Bulte , freebsd-scsi@FreeBSD.ORG Subject: Re: suggestion for camcontrol In-Reply-To: <20000908134520.A20744@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The points about cleanliness are worthy- except the deal here is that the interfaces have to be clean. The program 'camcontrol devlist' does not. You should be able to do XPT_PATH_INQ for paths 0 through 0xff to get at the list of SIMs. > On Fri, Sep 08, 2000 at 21:19:21 +0200, Wilko Bulte wrote: > > Would it be difficult for camcontrol to display the initiator ID of the > > hostadapter in addition to the devices in the output of devlist? > > > > Today: > > > > miata#camcontrol devlist > > at scbus0 target 0 lun 0 (pass0,da0) > > at scbus0 target 1 lun 0 (pass1,da1) > > at scbus0 target 2 lun 0 (pass2,da2) > > > > Suggested example: > > > > miata#camcontrol devlist > > at scbus0 target 0 lun 0 (pass0,da0) > > at scbus0 target 1 lun 0 (pass1,da1) > > at scbus0 target 2 lun 0 (pass2,da2) > > at scbus0 target 7 > > > > I'm currently playing with shared SCSI buses and in situations like that it > > is really practical if you can get a display of the complete SCSI bus. > > Well, the initiator isn't currently included in the CAM EDT, and I'm not > sure that it would be the right thing to do that. You'd need the initiator > to be in the EDT in order for printing it with 'camcontrol devlist' to just > work. (Well, it wouldn't quite "just work", you might need some additional > printing logic.) > > The most likely place for that information to go would be the Path Inquiry > CCB. In fact, the initiator ID is already in that CCB, it just isn't > displayed by 'camcontrol negotiate da0 -v'. I've attached a patch to do > that, here's what you get: > > # ./camcontrol negotiate da0 -v > Current Parameters: > (pass0:ahc0:0:0:0): sync parameter: 12 > (pass0:ahc0:0:0:0): frequency: 20.000MHz > (pass0:ahc0:0:0:0): offset: 8 > (pass0:ahc0:0:0:0): bus width: 16 bits > (pass0:ahc0:0:0:0): disconnection is enabled > (pass0:ahc0:0:0:0): tagged queueing is enabled > ahc0: SIM/HBA version: 1 > ahc0: supports tag queue messages > ahc0: supports SDTR message > ahc0: supports 16 bit wide SCSI > ahc0: HBA engine count: 0 > ahc0: maximum target: 15 > ahc0: maximum LUN: 64 > ahc0: highest path ID in subsystem: 0 > ahc0: initiator ID: 7 > ahc0: SIM vendor: FreeBSD > ahc0: HBA vendor: Adaptec > ahc0: bus ID: 0 > ahc0: base transfer speed: 3.300MB/sec > > As far as putting it in the devlist output, we could kludge some of the > information in there, but the adapter model number isn't currently included > in the path inquiry. > > It might be possible to add a new node type into the EDT, or perhaps to > represent the initiator as a target device, but that would require adding > target matching capability. We could add the initiator as a regular > device (lun), but it wouldn't have many of the things associated with a > lun/device node, like inquiry data. > > Anyway, the bottom line is that it can be done, but doing it in a clean > manner isn't trivial. I think it would need some discussion to figure out > whether there should be a node for the initiator in the EDT, and if so, > what sort of node it should be. > > Ken > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 8 15:16: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 63A4937B423 for ; Fri, 8 Sep 2000 15:16:03 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA22082; Fri, 8 Sep 2000 16:15:50 -0600 (MDT) (envelope-from ken) Date: Fri, 8 Sep 2000 16:15:50 -0600 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Wilko Bulte , freebsd-scsi@FreeBSD.ORG Subject: Re: suggestion for camcontrol Message-ID: <20000908161550.A21933@panzer.kdm.org> References: <20000908134520.A20744@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Fri, Sep 08, 2000 at 02:54:09PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Sep 08, 2000 at 14:54:09 -0700, Matthew Jacob wrote: > > The points about cleanliness are worthy- except the deal here is that the > interfaces have to be clean. The program 'camcontrol devlist' does not. Interfaces don't "have" to be clean, and neither does code that accesses those interfaces. Cleanliness is a choice made by the developer, and in this case I'm chosing the clean path rather than the quick-n-dirty path. The information in question is available through 'camcontrol negotiate -v', (once I commit the patch) so I don't think there's an urgent need for this, anyway. We've got time to do this the right way instead of throwing something in there that will likely stay there a long time. > You should be able to do XPT_PATH_INQ for paths 0 through 0xff to get at the > list of SIMs. Actually, you can't do that at the moment. To do a path inquiry, you need a device to do a path inquiry on. (i.e. path inquiries can only be done via the pass driver at the moment, they aren't supported through the xpt driver.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 8 22:50:29 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hawk.prod.itd.earthlink.net (hawk.prod.itd.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id 1CB3137B424; Fri, 8 Sep 2000 22:50:26 -0700 (PDT) Received: from earthlink.net (dialup-63.209.93.125.LosAngeles1.Level3.net [63.209.93.125]) by hawk.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id WAA09839; Fri, 8 Sep 2000 22:46:16 -0700 (PDT) Message-ID: <39B9CEAC.E2F5AF0A@earthlink.net> Date: Fri, 08 Sep 2000 22:46:20 -0700 From: Wes Warner X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.4.0-test8 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: adaptec 2940uw with smp kernel on a bp6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a abit bp6 and an adaptec 2940 uw scsi card. If I compile a SMP kernel with cupport for my scsi card I get this error... Waiting 15 seconds for SCSI devices to settle Timeout SCB handled by another timeout (probe1:ahc0:0:1:0)SCB 0xd timedout ahc0 Issued channel A bus reset 14 SCBs Aborted I can run SMP fine without the card or run with the card and no SMP, but I can't do them both together. Is there a fix for this? Thanks, Wes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 9 0:10:42 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24C1D37B617 for ; Sat, 9 Sep 2000 00:10:40 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 074B46E3362 for ; Sat, 9 Sep 2000 00:06:35 -0700 (PDT) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 13XeLc-0002hP-00; Fri, 8 Sep 2000 23:42:44 -0700 Date: Fri, 8 Sep 2000 23:42:40 -0700 (PDT) From: Tom Samplonius To: Wes Warner Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: adaptec 2940uw with smp kernel on a bp6 In-Reply-To: <39B9CEAC.E2F5AF0A@earthlink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 8 Sep 2000, Wes Warner wrote: > Hi, I have a abit bp6 and an adaptec 2940 uw scsi card. If I compile a > SMP > kernel with cupport for my scsi card I get this error... > > Waiting 15 seconds for SCSI devices to settle > Timeout SCB handled by another timeout > (probe1:ahc0:0:1:0)SCB 0xd timedout > ahc0 Issued channel A bus reset 14 SCBs Aborted > > I can run SMP fine without the card or run with the card and no SMP, but > I can't do them both together. Is there a fix for this? Perhaps. What version of FreeBSD are you using? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 9 7:27:24 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from fire.starkreality.com (fire.starkreality.com [198.78.158.210]) by hub.freebsd.org (Postfix) with ESMTP id F357437B422; Sat, 9 Sep 2000 07:27:16 -0700 (PDT) Received: from palehorse.starkreality.com (palehorse.starkreality.com [198.78.158.217]) by fire.starkreality.com (8.9.3/8.9.2) with ESMTP id JAA13254; Sat, 9 Sep 2000 09:27:06 -0500 (CDT) Message-Id: <4.3.2.7.2.20000909091918.039a0f70@mail.starkreality.com> X-Sender: caesar@mail.starkreality.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 09 Sep 2000 09:27:05 -0500 To: Wes Warner , freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG From: "William S. Duncanson" Subject: Re: adaptec 2940uw with smp kernel on a bp6 In-Reply-To: <39B9CEAC.E2F5AF0A@earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hm, I have a Tyan Tiger 100 with dual processors running in SMP mode with a 2940UW. I would suggest making sure that the BIOS for the motherboard and the card are up to date. Does any other MP capable OS work? What are the outputs of dmesg and mptable? At 00:46 9/9/2000, Wes Warner wrote: >Hi, I have a abit bp6 and an adaptec 2940 uw scsi card. If I compile a >SMP >kernel with cupport for my scsi card I get this error... > >Waiting 15 seconds for SCSI devices to settle >Timeout SCB handled by another timeout >(probe1:ahc0:0:1:0)SCB 0xd timedout >ahc0 Issued channel A bus reset 14 SCBs Aborted > >I can run SMP fine without the card or run with the card and no SMP, but >I can't do them both together. Is there a fix for this? > > Thanks, > Wes > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-smp" in the body of the message -- William S. Duncanson caesar@starkreality.com Smash forehead on keyboard to continue... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 9 9:51:21 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.prod.itd.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 62BDF37B422; Sat, 9 Sep 2000 09:51:18 -0700 (PDT) Received: from earthlink.net (dialup-209.245.67.138.LosAngeles1.Level3.net [209.245.67.138]) by gull.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id JAA24551; Sat, 9 Sep 2000 09:51:16 -0700 (PDT) Message-ID: <39BA6A83.8B800FD9@earthlink.net> Date: Sat, 09 Sep 2000 09:51:15 -0700 From: Wes Warner X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.4.0-test8 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: adaptec 2940uw with smp kernel on a bp6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I"m running 4.1. Wes Tom Samplonius wrote: > > On Fri, 8 Sep 2000, Wes Warner wrote: > > > Hi, I have a abit bp6 and an adaptec 2940 uw scsi card. If I compile a > > SMP > > kernel with cupport for my scsi card I get this error... > > > > Waiting 15 seconds for SCSI devices to settle > > Timeout SCB handled by another timeout > > (probe1:ahc0:0:1:0)SCB 0xd timedout > > ahc0 Issued channel A bus reset 14 SCBs Aborted > > > > I can run SMP fine without the card or run with the card and no SMP, but > > I can't do them both together. Is there a fix for this? > > Perhaps. What version of FreeBSD are you using? > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 9 9:55:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.prod.itd.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 3AFAE37B42C; Sat, 9 Sep 2000 09:55:22 -0700 (PDT) Received: from earthlink.net (dialup-209.245.67.138.LosAngeles1.Level3.net [209.245.67.138]) by gull.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id JAA03817; Sat, 9 Sep 2000 09:55:20 -0700 (PDT) Message-ID: <39BA6B77.CA1D2C5F@earthlink.net> Date: Sat, 09 Sep 2000 09:55:19 -0700 From: Wes Warner X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.4.0-test8 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: adaptec 2940uw with smp kernel on a bp6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I updated both the scsi card bios and my mobo bios to see if that helped already. I didn't get any improvement. I currently am running slackware and it runs fine both smp and the scsi card. It works with either 2.2.x or 2.4.test.x. When I have scsi support enabled in the kernel the machine only gives me the error message, it will not totally boot. I don't ever get a terminal, it just hangs. Thanks, Wes "William S. Duncanson" wrote: > > Hm, I have a Tyan Tiger 100 with dual processors running in SMP mode with a > 2940UW. I would suggest making sure that the BIOS for the motherboard and > the card are up to date. Does any other MP capable OS work? What are the > outputs of dmesg and mptable? > > At 00:46 9/9/2000, Wes Warner wrote: > > >Hi, I have a abit bp6 and an adaptec 2940 uw scsi card. If I compile a > >SMP > >kernel with cupport for my scsi card I get this error... > > > >Waiting 15 seconds for SCSI devices to settle > >Timeout SCB handled by another timeout > >(probe1:ahc0:0:1:0)SCB 0xd timedout > >ahc0 Issued channel A bus reset 14 SCBs Aborted > > > >I can run SMP fine without the card or run with the card and no SMP, but > >I can't do them both together. Is there a fix for this? > > > > Thanks, > > Wes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 9 11:50:37 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 103D837B424; Sat, 9 Sep 2000 11:50:33 -0700 (PDT) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 13XpM3-0003gy-00; Sat, 9 Sep 2000 11:27:55 -0700 Date: Sat, 9 Sep 2000 11:27:48 -0700 (PDT) From: Tom Samplonius To: Wes Warner Cc: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: adaptec 2940uw with smp kernel on a bp6 In-Reply-To: <39BA6A83.8B800FD9@earthlink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 9 Sep 2000, Wes Warner wrote: > I"m running 4.1. > > Wes 4.1-RELEASE or 4.1-STABLE? I believe an up-to-date -STABLE has some ahc fixes. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 9 11:55:36 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from lithium.nac.net (lithium.nac.net [64.21.52.68]) by hub.freebsd.org (Postfix) with SMTP id A300137B423 for ; Sat, 9 Sep 2000 11:55:31 -0700 (PDT) Received: (qmail 66728 invoked from network); 9 Sep 2000 18:55:27 -0000 Received: from vpn-144.oct.nac.net (HELO shakalaka) (207.99.116.144) by mail.nac.net with SMTP; 9 Sep 2000 18:55:27 -0000 Date: Sat, 9 Sep 2000 14:57:33 -0400 (Eastern Daylight Time) From: Alex To: freebsd-scsi@FreeBSD.ORG Subject: DPT tools? In-Reply-To: Message-ID: X-X-Sender: alex@mail.nac.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Anyone know what version of Free you need to run to get the /usr/local/bin/dpt* tools? I've seen it mentioned, but I've never seen the actually binaries. As an aside, when using the mlxd device, has anyone seen this: helium:~$ mlxcontrol status mlxd0 mlxcontrol: couldn't get controller/drive for /dev/mlxd0 mlxd0: online To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 9 13:18:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 6715C37B42C for ; Sat, 9 Sep 2000 13:18:08 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA05519; Sat, 9 Sep 2000 13:17:24 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009092017.NAA05519@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alex Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: DPT tools? In-reply-to: Your message of "Sat, 09 Sep 2000 14:57:33 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Sep 2000 13:17:24 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > As an aside, when using the mlxd device, has anyone seen this: > > helium:~$ mlxcontrol status mlxd0 > mlxcontrol: couldn't get controller/drive for /dev/mlxd0 > mlxd0: online Try creating /dev/mlx0 -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 9 17:33:56 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id C66FB37B422; Sat, 9 Sep 2000 17:33:49 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8A0XYG15727; Sun, 10 Sep 2000 10:03:34 +0930 (CST) (envelope-from grog) Date: Sun, 10 Sep 2000 10:03:34 +0930 From: Greg Lehey To: Wes Warner Cc: FreeBSD Questions Subject: Re: adaptec 2940uw with smp kernel on a bp6 Message-ID: <20000910100334.A15703@wantadilla.lemis.com> References: <39B9CEAC.E2F5AF0A@earthlink.net> <39BA6B77.CA1D2C5F@earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39BA6B77.CA1D2C5F@earthlink.net>; from ufodziner@earthlink.net on Sat, Sep 09, 2000 at 09:55:19AM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Format recovered--see http://www.lemis.com/email/email-format.html] [Following up to -questions] On Saturday, 9 September 2000 at 9:55:19 -0700, Wes Warner wrote: > "William S. Duncanson" wrote: >> At 00:46 9/9/2000, Wes Warner wrote: >> >>> Hi, I have a abit bp6 and an adaptec 2940 uw scsi card. If I >>> compile a SMP kernel with cupport for my scsi card I get this >>> error... >>> >>> Waiting 15 seconds for SCSI devices to settle >>> Timeout SCB handled by another timeout >>> (probe1:ahc0:0:1:0)SCB 0xd timedout >>> ahc0 Issued channel A bus reset 14 SCBs Aborted >>> >>> I can run SMP fine without the card or run with the card and no >>> SMP, but I can't do them both together. Is there a fix for this? >> >> Hm, I have a Tyan Tiger 100 with dual processors running in SMP >> mode with a 2940UW. I would suggest making sure that the BIOS for >> the motherboard and the card are up to date. Does any other MP >> capable OS work? What are the outputs of dmesg and mptable? > > I updated both the scsi card bios and my mobo bios to see if that > helped already. I didn't get any improvement. I currently am > running slackware and it runs fine both smp and the scsi card. It > works with either 2.2.x or 2.4.test.x. When I have scsi support > enabled in the kernel the machine only gives me the error message, > it will not totally boot. I don't ever get a terminal, it just > hangs. Well, the simple answer is that this is not a general bug. Plenty of people, myself included, are running this combination of motherboard and host adapter. What is the rest of your hardware? dmesg output would be a good idea. It's also a good idea to try a GENERIC kernel modified for SMP, rather than a kernel with other modifications, just in case that's the problem. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 9 17:49: 6 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hawk.prod.itd.earthlink.net (hawk.prod.itd.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id ADABA37B422; Sat, 9 Sep 2000 17:49:03 -0700 (PDT) Received: from earthlink.net (dialup-63.212.128.135.LosAngeles1.Level3.net [63.212.128.135]) by hawk.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id RAA08596; Sat, 9 Sep 2000 17:49:01 -0700 (PDT) Message-ID: <39BADA7D.F68366E8@earthlink.net> Date: Sat, 09 Sep 2000 17:49:01 -0700 From: Wes Warner X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.4.0-test8 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: adaptec 2940uw with smp kernel on a bp6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm not sure to be honest. I downloaded it when it wasn't an rc anymore. I can tr to re-download it and see if htat works. Thanks, Wes Tom Samplonius wrote: > > On Sat, 9 Sep 2000, Wes Warner wrote: > > > I"m running 4.1. > > > > Wes > > 4.1-RELEASE or 4.1-STABLE? I believe an up-to-date -STABLE has some ahc > fixes. > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 9 21: 1:42 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.prod.itd.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 1795737B424; Sat, 9 Sep 2000 21:01:39 -0700 (PDT) Received: from earthlink.net (dialup-63.212.142.182.LosAngeles1.Level3.net [63.212.142.182]) by swan.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id VAA09925; Sat, 9 Sep 2000 21:01:37 -0700 (PDT) Message-ID: <39BB07A2.D04EF9E7@earthlink.net> Date: Sat, 09 Sep 2000 21:01:39 -0700 From: Wes Warner X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.4.0-test8 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: adaptec 2940uw with smp kernel on a bp6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What I am using is a generic kernel with SMP enabled. The kernel I use with the scsi working is just the regular generic. I'm trying to do this as tactful as possible. The rest of my hardware is... SBLive, Linksys 10/100 nic, ATI All-in-wonder 32meg, Colorado Floppy tape (with card), 3com 56k external modem, 3ea. WD 50 pin SCSI drives, Maxtor 20 gig ata66 drive (OS is on this drive), Quantum 5 gig, creative 52x cdrom, Philips 2x2x6 burner, ls-120. I think that is about it. If it matters, my processors are 433's and I have 256megs of RAM. I have tried it both overclocked and not with no luck either way. I can't get a dmesg output with both smp and scsi because it doesn't boot. Thanks, Wes > Well, the simple answer is that this is not a general bug. Plenty of > people, myself included, are running this combination of motherboard > and host adapter. What is the rest of your hardware? dmesg output > would be a good idea. It's also a good idea to try a GENERIC kernel > modified for SMP, rather than a kernel with other modifications, just > in case that's the problem. > > Greg > -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 9 22:48:52 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from lithium.nac.net (lithium.nac.net [64.21.52.68]) by hub.freebsd.org (Postfix) with SMTP id B458837B423 for ; Sat, 9 Sep 2000 22:48:46 -0700 (PDT) Received: (qmail 27095 invoked from network); 10 Sep 2000 05:48:46 -0000 Received: from vpn-144.oct.nac.net (HELO shakalaka) (207.99.116.144) by mail.nac.net with SMTP; 10 Sep 2000 05:48:46 -0000 Date: Sun, 10 Sep 2000 01:50:52 -0400 (Eastern Daylight Time) From: Alex To: Mike Smith Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: DPT tools? In-Reply-To: <200009092017.NAA05519@mass.osd.bsdi.com> Message-ID: X-X-Sender: alex@mail.nac.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, thats better. However: helium:/dev$ mlxcontrol status mlx0: DAC960PRL, 1 channel, firmware 4.07--48, 4MB RAM disk0000 (online) disk0001 (online) disk0002 (online) disk0003 (online) (then it just hangs there until I hit control-c). I let it sit for about 3 minutes, and it didn't return. any ideas on this one? On Sat, 9 Sep 2000, Mike Smith wrote: > > > > As an aside, when using the mlxd device, has anyone seen this: > > > > helium:~$ mlxcontrol status mlxd0 > > mlxcontrol: couldn't get controller/drive for /dev/mlxd0 > > mlxd0: online > > Try creating /dev/mlx0 > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 9 23:28:19 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from femail2.sdc1.sfba.home.com (femail2.sdc1.sfba.home.com [24.0.95.82]) by hub.freebsd.org (Postfix) with ESMTP id 93D2237B422; Sat, 9 Sep 2000 23:28:16 -0700 (PDT) Received: from cx443070b ([24.0.36.170]) by femail2.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20000910062809.OYIP27630.femail2.sdc1.sfba.home.com@cx443070b>; Sat, 9 Sep 2000 23:28:09 -0700 Message-ID: <000701c01af0$72e24ac0$aa240018@cx443070b> From: "Jeremiah Gowdy" To: "Wes Warner" , , References: <39BB07A2.D04EF9E7@earthlink.net> Subject: Re: adaptec 2940uw with smp kernel on a bp6 Date: Sat, 9 Sep 2000 23:29:15 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > What I am using is a generic kernel with SMP enabled. The kernel I use > with the scsi working is just the regular generic. I'm trying to do > this as tactful as possible. The rest of my hardware is... > > SBLive, Linksys 10/100 nic, ATI All-in-wonder 32meg, Colorado Floppy > tape (with card), 3com 56k external modem, 3ea. WD 50 pin SCSI drives, > Maxtor 20 gig ata66 drive (OS is on this drive), Quantum 5 gig, creative > 52x cdrom, Philips 2x2x6 burner, ls-120. > > I think that is about it. If it matters, my processors are 433's and I > have 256megs of RAM. I have tried it both overclocked and not with no > luck either way. I can't get a dmesg output with both smp and scsi > because it doesn't boot. > > Thanks, > Wes I wouldn't think a GENERIC kernel with SMP enabled would be better/cleaner/safer/less likely to crash than a cleaned kernel containing only the drivers you need. Seems like less likely of a chance of a conflict. I suggest, clean a GENERIC, enable SMP and go with that To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message