From owner-aic7xxx  Fri Aug 29 13:59:54 1997
Return-Path: <owner-aic7xxx>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id NAA27937
          for aic7xxx-outgoing; Fri, 29 Aug 1997 13:59:54 -0700 (PDT)
Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA27931
          for <aic7xxx@FreeBSD.ORG>; Fri, 29 Aug 1997 13:59:51 -0700 (PDT)
Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id PAA04735; Fri, 29 Aug 1997 15:24:14 -0500 (CDT)
Message-Id: <199708292024.PAA04735@iworks.InterWorks.org>
Date: Fri, 29 Aug 1997 15:24:14 -0500 (CDT)
From: "Daniel M. Eischen" <deischen@iworks.InterWorks.org>
To: dledford@dialnet.net
Subject: Re: AHA-2940, CHECK_CONDITION
Cc: aic7xxx@FreeBSD.ORG, slimmer@fnal.gov
Sender: owner-aic7xxx@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > The aic7xxx driver (and other drivers too) automatically request
> > the sense information upon a check condition.  Check the sense
> > buffer in the SCSI command for non-zero which is what I believe
> > the mid-level SCSI code does.  
> 
> Of course, we also set the aic7xxx_error(cmd) = DID_ERROR (mapped from 
> DID_RETRY_COMMAND).  This very well could be causing the mid level code to 
> retry the command instead of passing the sense up to the calling party.  It 
> may be more appropriate to do something like this:

We don't set any error on a CHECK_CONDITION.

Dan Eischen
deischen@iworks.InterWorks.org