From owner-freebsd-scsi@FreeBSD.ORG Wed Aug 13 18:12:26 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9C8437B401 for ; Wed, 13 Aug 2003 18:12:26 -0700 (PDT) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 260DB43FA3 for ; Wed, 13 Aug 2003 18:12:26 -0700 (PDT) (envelope-from ctuffli@cre85086tuf.rose.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 93364180E1; Wed, 13 Aug 2003 19:12:25 -0600 (MDT) Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos2.cos.agilent.com (Postfix) with ESMTP id E58F44F; Wed, 13 Aug 2003 19:12:24 -0600 (MDT) Received: from cre85086tuf.rose.agilent.com (cre85086tuf.rose.agilent.com [130.30.174.150])ESMTP id SAA19577; Wed, 13 Aug 2003 18:12:23 -0700 (PDT) Received: by cre85086tuf.rose.agilent.com (Postfix, from userid 1001) id 1B33A19DF99; Wed, 13 Aug 2003 18:11:12 -0700 (PDT) Date: Wed, 13 Aug 2003 18:11:11 -0700 From: Chuck Tuffli To: "Kenneth D. Merry" Message-ID: <20030814011111.GB3594@cre85086tuf.rose.agilent.com> References: <20030813034951.GA91644@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030813034951.GA91644@panzer.kdm.org> User-Agent: Mutt/1.4i cc: freebsd-scsi@freebsd.org Subject: Re: problem running scsi_target X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Aug 2003 01:12:27 -0000 Aside from the 2 fixes you mention below (without which bad things happen), most of this was confusion on my part. I expected that isp(4) would act as both target and initiator on a loop such that camcontrol rescan all on the machine running the target would have turned up the FreeBSD Disk. Once I attached an initiator on a different box, I got the expected # camcontrol devlist ... at scbus2 target 0 lun 0 (da1,pass1) I also didn't understand that "main loop beginning" meant that the target was waiting for something. As soon as I did a rescan with the other initiator, it was obvious scsi_target wasn't dead. Thanks for the help Ken! On Tue, Aug 12, 2003 at 11:49:51PM -0400, Kenneth D. Merry wrote: [snip] > One thing I found is that the scsi_target(8) code doesn't entirely play > well with the isp(4) driver. > > I had to make some tweaks to get things working more or less okay, at > least > with tagged queueing turned on: > > - enable autosense. Fibre channel, and packetized parallel SCSI, do > autosense, but it is disabled by default. Go into scsi_cmds.c, and > in > tcmd_sense(), uncomment the code after if (ctio != NULL) { ... that > fills in the sense buffer and sets the CAM_SEND_SENSE command. > > - go into scsi_target.h and increase the value of MAX_INITIATORS to 256 > instead of 16. I ended up running out of CCBs otherwise, at least > with > tagged queueing turned on. (I made some other tweaks to it -- fake > ramdisk support -- that may have caused that problem, though.) -- Chuck Tuffli Agilent Technologies, Storage and Networking