From owner-freebsd-scsi Tue Nov 14 9:54:52 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 62CE237B4D7 for ; Tue, 14 Nov 2000 09:54:49 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eAEHsf461679; Tue, 14 Nov 2000 10:54:42 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200011141754.eAEHsf461679@aslan.scsiguy.com> To: Jeff Fellin Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI target driver help In-Reply-To: Your message of "Tue, 14 Nov 2000 10:39:43 EST." <200011141539.KAA08238@aura.research.bell-labs.com> Date: Tue, 14 Nov 2000 10:54:41 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >I am writing a SCSI target device driver to capture SCSI disk commands >from a SCSI bus, and forward them to a user-level process for execution >and tracing. I am using an Adaptec 2940 Ultra2 SCSI Adapter boards >with external SCSI cables connecting the systems. ... Your problem is in the initiator side. Quite recently I fixed a problem in FreeBSD that prevented async notifications from being delivered to entities registered to paths with wildcards in them. The aic7xxx driver captures the AC_LOST_DEVICE event for all devices on its bus(es). When a device is lost, the aic7xxx driver clears out any negotiated transfer features assuming that if the device returns, it will be async. Without the async event being delivered, the intiator will continue to use a rate that the target does not expect, causing the timeout. This fix has not been merged to -stable yet due to the code freeze. If you have access to the CVS tree, pull the last revision to sys/cam/cam_xpt.c and apply it to your tree. It should apply without any problems. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message