Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Jun 1998 18:12:34 -0400 
From:      tcobb <tcobb@staff.circle.net>
To:        "'shimon@simon-shapiro.org'" <shimon@simon-shapiro.org>, Mike Smith <mike@smith.net.au>
Cc:        "freebsd-scsi@freebsd.org" <freebsd-scsi@FreeBSD.ORG>, "freebsd-current@freebsd.org" <freebsd-current@FreeBSD.ORG>
Subject:   RE: DPT Redux
Message-ID:  <509A2986E5C5D111B7DD0060082F32A402FB1D@freya.circle.net>

next in thread | raw e-mail | index | archive | help
> -----Original Message-----
> From: Simon Shapiro [mailto:shimon@simon-shapiro.org]
> I am deleting the cross-post to current....
> 
> On 02-Jun-98 Mike Smith wrote:
>  ...
> 
> > Then could you characterise "returning a successful 
> completion code for 
> > an incomplete/failed transfer"?  The SCSI stack has to 
> assume at this 
> > point that the transaction is complete, even though you're 
> admitting 
> > that it's not.
> 
> There was one specific failure mode, yes.  To get there, 
> especially on a
> RAID array, you had to have so many ducks lined up:
> 
> *  DPT free enough to accept commands
> *  DPT so busy it will not reply to INQUIRY on a RAID array 
> (there is no
>    SCSI bus involved here)
> *  DPT not setting the hardware registers as busy, while oh, so busy.
> 
> This condition had to persist for several minutes.  The patch 
> checked in
> against current fixes that.  the same patch will/should be checked in
> against 2.2 any moment now.
> 
> BTW, for this to exist, the DPT firmware has to be rather sick.  I can
> rplicate this scsnario with some broken, unpublished versions of the
> firmware.

In your test case, please try to replicate this problem with the
firmware version available for download from DPT's site right now.  That
was the version I used on my card (or, at least, the one available mid
last week).


-Troy Cobb
 Circle Net, Inc.
 http://www.circle.net

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?509A2986E5C5D111B7DD0060082F32A402FB1D>