From owner-freebsd-bugs  Sun Sep  8 12:48:12 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA18704
          for bugs-outgoing; Sun, 8 Sep 1996 12:48:12 -0700 (PDT)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA18695
          for <freebsd-bugs@FreeBSD.org>; Sun, 8 Sep 1996 12:48:09 -0700 (PDT)
Received: from boris.clintondale.com (boris.clintondale.com [206.88.120.5])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id MAA02401
          for <freebsd-bugs@FreeBSD.org>; Sun, 8 Sep 1996 12:48:08 -0700 (PDT)
Received: from localhost (matt@localhost) by boris.clintondale.com (8.7.5/8.7.3) with SMTP id PAA05009; Sun, 8 Sep 1996 15:46:36 -0400 (EDT)
Date: Sun, 8 Sep 1996 15:46:36 -0400 (EDT)
From: Matt Hamilton <matt@boris.clintondale.com>
To: Darren Reed <avalon@coombs.anu.edu.au>
cc: freebsd-bugs@FreeBSD.org, Darren Reed <avalon@cheops.anu.edu.au>
Subject: Re: more on T130 card + 2.1.5
In-Reply-To: <199609081000.AA16234@mail.crl.com>
Message-ID: <Pine.BSF.3.95.960908154042.4993B-100000@boris.clintondale.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-bugs@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> But, the next command I did was an "mt offl" (tape still in the drive)
> and it panic'd straight away, in the same was as before.
> 
> nca0 at 0x358-0x35f irq 7 on isa
> nca0: type NCR-5380
> (nca0:4:0): "WANGTEK 6130-HS 4G16" type 1 removable SCSI 2
> st0(nca0:4:0): Sequential-Access density code 0x13,  drive empty

I had a HP C1534A SCSI DAT drive connected to an Adaptec 2940 running
FreeBSD-2.1.5 and had lots of trouble with the drive causing SCSI resets
whenever I tried to use the drive.  First it timed out during 'data-out
phase' then it reset the SCSI bus, sometimes even reseting my hard-drives
:(

I solved the problem by moving to 2.2-960801-SNAP.  It now works fine....
so there must be something in the SCSI code that's different.  I know the
the SCSI code has been pretty much re-written a couple of days ago in
CURRENT, but this is a production machine and SNAP is as daring as I want
to be :)

You may be able to just move the SCSI stuff from SNAP into 2.1.5, but I
don't know if it depends on anything in particular in 2.2 that 2.1.5
doesn't have.

-Matt