From owner-freebsd-scsi  Sun Oct  8 13:54:30 1995
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA11331
          for freebsd-scsi-outgoing; Sun, 8 Oct 1995 13:54:30 -0700
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA11325
          for <freebsd-scsi@freebsd.org>; Sun, 8 Oct 1995 13:54:27 -0700
Received: (from julian@localhost) by ref.tfs.com (8.6.11/8.6.9) id NAA13862; Sun, 8 Oct 1995 13:53:52 -0700
From: Julian Elischer <julian@ref.tfs.com>
Message-Id: <199510082053.NAA13862@ref.tfs.com>
Subject: Re: aha0: Bus dropped at unexpected time
To: jmr@computing.com (Jim Rowan)
Date: Sun, 8 Oct 1995 13:53:51 -0700 (PDT)
Cc: freebsd-scsi@freebsd.org
In-Reply-To: <199510080123.UAA00562@zee.computing.com> from "Jim Rowan" at Oct 7, 95 08:22:59 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 416       
Sender: owner-freebsd-scsi@freebsd.org
Precedence: bulk

that message is just relayed from the firmware..
the firmware doesn't like something going on on the SCSI bus.
possibly you might be able to get your drive to run in SCSI-1 mode
(often there's a jumper)

also there is a call in scsiconf.c somewhere to make a drive run in SCSI-2
mode, but it's commented out. you might change it to order SCSI-1 mode
for all devices and uncomment it, and see if that helps.

julian