From owner-freebsd-current  Tue Mar 19 12:44:40 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA29636
          for current-outgoing; Tue, 19 Mar 1996 12:44:40 -0800 (PST)
Received: from desiree.teleport.com (desiree.teleport.com [192.108.254.21])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA29625
          Tue, 19 Mar 1996 12:44:30 -0800 (PST)
Received: from linda.teleport.com (mrl@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.12/8.6.9) with ESMTP id LAA16052; Tue, 19 Mar 1996 11:34:07 -0800
From: Mostyn/Annabella <mrl@teleport.com>
Received: (mrl@localhost) by linda.teleport.com (8.6.12/8.6.12) id LAA25294; Tue, 19 Mar 1996 11:34:07 -0800
Message-Id: <199603191934.LAA25294@linda.teleport.com>
Subject: Re: SCSI death in -current with DAT
To: gibbs@freefall.freebsd.org (Justin T. Gibbs)
Date: Tue, 19 Mar 1996 11:34:07 -0800 (PST)
Cc: current@freebsd.org, mrl@teleport.com, joerg_wunsch@uriah.heep.sax.de
In-Reply-To: <199603191708.JAA15782@freefall.freebsd.org> from "Justin T. Gibbs" at Mar 19, 96 09:08:20 am
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Its an aic7xxx driver problem related to parity checking which I
> recently enabled.  It seems that you get harmless parity errors
> when you have both a wide and narrow bus attached to the controller
> at one time.  I'm still investigating, but people seeing this problem
> should just disable parity checking in SCSI-Select.
              ^^^^^^^^^^^^^^^^^^^^^^^

Thank you very much. With parity switched off by the controller,
the DAT worked fine backing up a wide drive using a March 17th
-current system.

J"org, thank you for the fixed-block setup for the DAT - I didn't
use it but I'll keep it just in case.

Regards,
Mostyn Lewis