From owner-freebsd-questions  Fri Jun 21 06:43:17 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA15977
          for questions-outgoing; Fri, 21 Jun 1996 06:43:17 -0700 (PDT)
Received: from starfire.mn.org (root@starfire.skypoint.net [199.86.32.187])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA15968
          for <questions@FreeBSD.org>; Fri, 21 Jun 1996 06:43:13 -0700 (PDT)
From: john@starfire.mn.org
Received: (from john@localhost)
	by starfire.mn.org (8.6.12/1.1)  id IAA00626
	for questions@FreeBSD.org; Fri, 21 Jun 1996 08:43:10 -0500
Message-Id: <199606211343.IAA00626@starfire.mn.org>
Subject: SCSI weirdness
To: questions@FreeBSD.org (FreeBSD questions)
Date: Fri, 21 Jun 1996 08:43:09 -0500 (CDT)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Having extended and maintained SCSI adapter firmware, and having used
logic probes on SCSI adapters and buses, and having run SCSI bus analysers,
(none of that sophisticated hardware is available to me right now,
unfortunately), I once used to pretend to myself that I knew something
about SCSI devices and operation.  My current situation seems to be
proving that a sham.

Trying to describe the symptoms and behaviors and the complicated history
is not appropriate in this forum, nor an effective use of bandwidth, but
if there's anyone out there who wants to try to dig into this one with
me, or who can suggest a more appropriate forum, I'd be very pleased.
There may turn out to be some interactions with the FreeBSD SCSI
implementation, which is one reason why I started here.

		   John Lind, Starfire Consulting Services
E-mail: john@starfire.MN.ORG		USnail: PO Box 17247, Mpls MN  55417