From owner-aic7xxx  Fri Aug 29 17:55:22 1997
Return-Path: <owner-aic7xxx>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA09608
          for aic7xxx-outgoing; Fri, 29 Aug 1997 17:55:22 -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 RAA09599
          for <aic7xxx@FreeBSD.ORG>; Fri, 29 Aug 1997 17:55:16 -0700 (PDT)
Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id TAA05040; Fri, 29 Aug 1997 19:19:46 -0500 (CDT)
Message-Id: <199708300019.TAA05040@iworks.InterWorks.org>
Date: Fri, 29 Aug 1997 19:19:46 -0500 (CDT)
From: "Daniel M. Eischen" <deischen@iworks.InterWorks.org>
To: dledford@dialnet.net, mjacob@ns.feral.com
Subject: Re: AHA-2940, CHECK_CONDITION
Cc: aic7xxx@FreeBSD.ORG, slimmer@fnal.gov
Sender: owner-aic7xxx@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I noticed that today in a quick look at the Jun1 release. Isn't that
> a bug- you aren't even setting a value that target drivers can then
> see that "Oh, there's sense data"...? Or did I not read deeply enough...

The mid-level SCSI code checks the sense buffer after commands
are completed (at least that's the way it used to be).  We
could additionally set the WAS_SENSE flag in the scsi_cmnd,
but I think we'd be misusing it as it seems to be there
solely for the mid-level SCSI code to play with.

Dan Eischen
deischen@iworks.InterWorks.org