From owner-freebsd-scsi@FreeBSD.ORG Mon Aug 11 10:49:50 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 A603B37B401; Mon, 11 Aug 2003 10:49:50 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8CFD43FAF; Mon, 11 Aug 2003 10:49:49 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id <305LHV30>; Mon, 11 Aug 2003 13:49:48 -0400 Message-ID: From: Don Bowman To: "'Kenneth D. Merry'" , Don Bowman Date: Mon, 11 Aug 2003 13:49:46 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" cc: "'freebsd-scsi@freebsd.org'" cc: "'aic7xxx@freebsd.org'" Subject: RE: Ongoing U320 AIC7902 Seagate ST318453LW issues, SCB timed out 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: Mon, 11 Aug 2003 17:49:51 -0000 > From: Kenneth D. Merry [mailto:ken@kdm.org] > > On Fri, Aug 08, 2003 at 13:43:55 -0400, Don Bowman wrote: > > Just to confirm i'm talking about the same thing... > > my seagate device reports 255 tagged openings: > > > > # camcontrol tags 0:0:0 > > (pass0:ahd0:0:0:0): device openings: 255 > > > > but seagate indicates the device has only support for > > 64. Am i reading something different here? > > You'll see 255 openings until we get a queue full response > from the drive. > Then it'll go down to however many transactions we had > outstanding when the > queue full happened. > > If you want a little more information (e.g. how many transactions are > outstanding at a given moment), try: > > camcontrol tags da0 -v > > Ken So i've reconfirmed, the drive supports a max of 64 tags. under load I see the max go down to 252, how can that make sense? under severe load it may go lower, to e.g. 33. ??? From owner-freebsd-scsi@FreeBSD.ORG Mon Aug 11 10:59:49 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 17EC837B401; Mon, 11 Aug 2003 10:59:49 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C27943F75; Mon, 11 Aug 2003 10:59:48 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h7BHxjo06653; Mon, 11 Aug 2003 10:59:45 -0700 Received: from [10.100.253.70] (aslan.btc.adaptec.com [10.100.253.70]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id KAA24845; Mon, 11 Aug 2003 10:59:41 -0700 (PDT) Date: Mon, 11 Aug 2003 12:01:22 -0600 From: "Justin T. Gibbs" To: Don Bowman , "'Kenneth D. Merry'" Message-ID: <2442282704.1060624882@aslan.btc.adaptec.com> In-Reply-To: References: X-Mailer: Mulberry/3.1.0b5 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: "'freebsd-scsi@freebsd.org'" cc: "'aic7xxx@freebsd.org'" Subject: RE: Ongoing U320 AIC7902 Seagate ST318453LW issues, SCB timed out X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Justin T. Gibbs" List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2003 17:59:49 -0000 > So i've reconfirmed, the drive supports a max of 64 tags. > under load I see the max go down to 252, how can that make > sense? under severe load it may go lower, to e.g. 33. The actual number of transactions these drives support depends heavily on load. For reads, I believe that you can have much more than 64 commands outstanding to this drive. Once you start to fill the write buffer, the number of commands the drive can hold drops to 32 or 33 depending on the firmware rev. It seems that command resources are managed dynamically and that deferrred writes hold on to those resources while they are draining to the media. -- Justin From owner-freebsd-scsi@FreeBSD.ORG Mon Aug 11 11:02:48 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 105A437B40B for ; Mon, 11 Aug 2003 11:02:48 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 141C643F85 for ; Mon, 11 Aug 2003 11:02:45 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h7BI2iUp082662 for ; Mon, 11 Aug 2003 11:02:44 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h7BI2i3p082656 for scsi@freebsd.org; Mon, 11 Aug 2003 11:02:44 -0700 (PDT) Date: Mon, 11 Aug 2003 11:02:44 -0700 (PDT) Message-Id: <200308111802.h7BI2i3p082656@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: scsi@FreeBSD.org Subject: Current problem reports assigned to you 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: Mon, 11 Aug 2003 18:02:48 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [1999/12/21] kern/15608 scsi acd0 / cd0 give inconsistent errors on em 1 problem total. From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 12 17:07:33 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 AD8DE37B401 for ; Tue, 12 Aug 2003 17:07:33 -0700 (PDT) Received: from msgbas2x.cos.agilent.com (msgbas1tx.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAC8D43F75 for ; Tue, 12 Aug 2003 17:07:32 -0700 (PDT) (envelope-from ctuffli@cre85086tuf.rose.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id 7BE681082 for ; Tue, 12 Aug 2003 18:07:32 -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 21A6F18 for ; Tue, 12 Aug 2003 18:07:32 -0600 (MDT) Received: from cre85086tuf.rose.agilent.com (cre85086tuf.rose.agilent.com [130.30.174.150])ESMTP id RAA02721 for ; Tue, 12 Aug 2003 17:07:31 -0700 (PDT) Received: by cre85086tuf.rose.agilent.com (Postfix, from userid 1001) id 4179E19DF95; Tue, 12 Aug 2003 17:06:21 -0700 (PDT) Date: Tue, 12 Aug 2003 17:06:21 -0700 From: Chuck Tuffli To: freebsd-scsi@freebsd.org Message-ID: <20030813000620.GA2564@cre85086tuf.rose.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: 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: Wed, 13 Aug 2003 00:07:34 -0000 Hi - I started playing with scsi_target and have run into a problem getting it up and running. When I run fluffy# scsi_target -d 0:1:0 ./test_file scsi_target: aio support tested ok scsi_target: TARGIOCENABLE: Device not configured scsi_target: cleanup called fluffy# dmesg |grep -i isp isp0: port 0x3000-0x30ff mem 0xfc204000-0xfc204fff irq 11 at device 1.0 on pci3 isp0: port logout of iid 0 (noperiph:isp0:0:1:0): enable lun CCB rejected, status 0x39 It seems like there is some machine configuration step I missed, but I'm not sure what it was. Any ideas? The OS is 4.8 release with the following config # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # SCSI target emulator device targ # Blackhole driver device targbh options CAMDEBUG options VFS_AIO # QLogic support device isp device ispfw options ISP_TARGET_MODE=1 -- Chuck Tuffli Agilent Technologies, Storage and Networking From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 12 17:34:04 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 DA94537B401 for ; Tue, 12 Aug 2003 17:34:04 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08AF343FBD for ; Tue, 12 Aug 2003 17:34:04 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id h7D0XvYU090828; Tue, 12 Aug 2003 18:33:57 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id h7D0Xv02090827; Tue, 12 Aug 2003 18:33:57 -0600 (MDT) (envelope-from ken) Date: Tue, 12 Aug 2003 18:33:57 -0600 From: "Kenneth D. Merry" To: Chuck Tuffli Message-ID: <20030813003357.GA90771@panzer.kdm.org> References: <20030813000620.GA2564@cre85086tuf.rose.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030813000620.GA2564@cre85086tuf.rose.agilent.com> User-Agent: Mutt/1.4.1i 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: Wed, 13 Aug 2003 00:34:05 -0000 On Tue, Aug 12, 2003 at 17:06:21 -0700, Chuck Tuffli wrote: > Hi - > > I started playing with scsi_target and have run into a problem getting > it up and running. When I run > > fluffy# scsi_target -d 0:1:0 ./test_file > scsi_target: aio support tested ok > scsi_target: TARGIOCENABLE: Device not configured > scsi_target: cleanup called > > fluffy# dmesg |grep -i isp > isp0: port 0x3000-0x30ff mem 0xfc204000-0xfc204fff irq 11 at device 1.0 on pci3 > isp0: port logout of iid 0 > (noperiph:isp0:0:1:0): enable lun CCB rejected, status 0x39 > > It seems like there is some machine configuration step I missed, but > I'm not sure what it was. Any ideas? > > The OS is 4.8 release with the following config One thing I found, at least when connecting two Qlogic boards point to point, is that they'll typically negotiate which target ID they're using. In short, if target 1 isn't working for you, try target 0 instead. (If you've got the board hooked up to a switch, I'm not sure what will happen as far as IDs go.) Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 12 18:13:19 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 D674637B401 for ; Tue, 12 Aug 2003 18:13:19 -0700 (PDT) Received: from msgbas2x.cos.agilent.com (msgbas2x.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06C7443F75 for ; Tue, 12 Aug 2003 18:13:19 -0700 (PDT) (envelope-from ctuffli@cre85086tuf.rose.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id 8F610B0D; Tue, 12 Aug 2003 19:13:18 -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 2E90917; Tue, 12 Aug 2003 19:13:18 -0600 (MDT) Received: from cre85086tuf.rose.agilent.com (cre85086tuf.rose.agilent.com [130.30.174.150])ESMTP id SAA04505; Tue, 12 Aug 2003 18:13:16 -0700 (PDT) Received: by cre85086tuf.rose.agilent.com (Postfix, from userid 1001) id 3F06619DF95; Tue, 12 Aug 2003 18:12:07 -0700 (PDT) Date: Tue, 12 Aug 2003 18:12:07 -0700 From: Chuck Tuffli To: "Kenneth D. Merry" Message-ID: <20030813011206.GC2564@cre85086tuf.rose.agilent.com> References: <20030813000620.GA2564@cre85086tuf.rose.agilent.com> <20030813003357.GA90771@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030813003357.GA90771@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: Wed, 13 Aug 2003 01:13:20 -0000 On Tue, Aug 12, 2003 at 06:33:57PM -0600, Kenneth D. Merry wrote: [snip] > One thing I found, at least when connecting two Qlogic boards point to > point, is that they'll typically negotiate which target ID they're using. > > In short, if target 1 isn't working for you, try target 0 instead. (If > you've got the board hooked up to a switch, I'm not sure what will happen > as far as IDs go.) I do have this hooked up to a switch and 0:0:0 doesn't seem to work either. I just tried hooking this up to a private loop and get a different result fluffy# scsi_target -d 0:0:0 ./test_file scsi_target: aio support tested ok scsi_target: sending ccb (0x4) scsi_target: sending ccb (0x332) ... scsi_target: sending ccb (0x334) scsi_target: main loop beginning and there it hangs. camcontrol makes it look like the right thing is trying to happen fluffy# camcontrol devlist -v scbus0 on isp0 bus 0: < > at scbus0 target 0 lun 0 (targ0) < > at scbus0 target -1 lun -1 (targbh0) scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) The isp relavant portion of dmsg isp0: port 0x3000-0x30ff mem 0xfc204000-0xfc204fff irq 11 at device 1.0 on pci3 isp0: Mbox Command Async (0x4000) with no waiters (noperiph:isp0:0:0:0): (xpt0:isp0:0:0:0): debugging flags now 20 (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): Sending inline ccb 0x4 (0xbfbff99c) (targ0:isp0:0:0:0): getccb 0xc24ec900 (targ0:isp0:0:0:0): sendccb 0xc24ec900 (targ0:isp0:0:0:0): targreturnccb 0xc24ec900 (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ec900 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804f000) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ec800 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804f100) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ec700 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804f200) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ec600 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804f300) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ec500 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804f400) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ec400 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804f500) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ec300 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804f600) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ec200 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804f700) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ec100 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804f800) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ec000 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804f900) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24eef00 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804fa00) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24eee00 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804fb00) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24eed00 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804fc00) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24eec00 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804fd00) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24eeb00 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804fe00) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24eea00 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x804ff00) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ee900 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051000) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ee800 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051100) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ee700 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051200) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ee600 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051300) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ee500 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051400) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ee400 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051500) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ee300 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051600) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ee200 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051700) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ee100 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051800) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24ee000 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051900) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24eff00 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051a00) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24efe00 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051b00) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24efd00 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051c00) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24efc00 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051d00) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24efb00 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051e00) (targ0:isp0:0:0:0): write - uio_resid 4 (targ0:isp0:0:0:0): getccb 0xc24efa00 (targ0:isp0:0:0:0): Sent ATIO/INOT (0x8051f00) -- Chuck Tuffli Agilent Technologies, Storage and Networking From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 12 20:49:55 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 F0B8E37B401 for ; Tue, 12 Aug 2003 20:49:54 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0E8943F75 for ; Tue, 12 Aug 2003 20:49:53 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id h7D3nqYU091726; Tue, 12 Aug 2003 21:49:52 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id h7D3npJC091725; Tue, 12 Aug 2003 21:49:52 -0600 (MDT) (envelope-from ken) Date: Tue, 12 Aug 2003 21:49:51 -0600 From: "Kenneth D. Merry" To: Chuck Tuffli Message-ID: <20030813034951.GA91644@panzer.kdm.org> References: <20030813000620.GA2564@cre85086tuf.rose.agilent.com> <20030813003357.GA90771@panzer.kdm.org> <20030813011206.GC2564@cre85086tuf.rose.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030813011206.GC2564@cre85086tuf.rose.agilent.com> User-Agent: Mutt/1.4.1i 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: Wed, 13 Aug 2003 03:49:55 -0000 On Tue, Aug 12, 2003 at 18:12:07 -0700, Chuck Tuffli wrote: > On Tue, Aug 12, 2003 at 06:33:57PM -0600, Kenneth D. Merry wrote: > [snip] > > One thing I found, at least when connecting two Qlogic boards point to > > point, is that they'll typically negotiate which target ID they're using. > > > > In short, if target 1 isn't working for you, try target 0 instead. (If > > you've got the board hooked up to a switch, I'm not sure what will happen > > as far as IDs go.) > > I do have this hooked up to a switch and 0:0:0 doesn't seem to work > either. I just tried hooking this up to a private loop and get a > different result > > fluffy# scsi_target -d 0:0:0 ./test_file > scsi_target: aio support tested ok > scsi_target: sending ccb (0x4) > scsi_target: sending ccb (0x332) > ... > scsi_target: sending ccb (0x334) > scsi_target: main loop beginning > > and there it hangs. camcontrol makes it look like the right thing is > trying to happen > > fluffy# camcontrol devlist -v > scbus0 on isp0 bus 0: > < > at scbus0 target 0 lun 0 (targ0) > < > at scbus0 target -1 lun -1 (targbh0) > scbus-1 on xpt0 bus 0: > < > at scbus-1 target -1 lun -1 (xpt0) > > The isp relavant portion of dmsg > > isp0: port 0x3000-0x30ff mem 0xfc204000-0xfc204fff irq 11 at device 1.0 on pci3 > isp0: Mbox Command Async (0x4000) with no waiters > (noperiph:isp0:0:0:0): (xpt0:isp0:0:0:0): debugging flags now 20 > (targ0:isp0:0:0:0): write - uio_resid 4 > (targ0:isp0:0:0:0): Sending inline ccb 0x4 (0xbfbff99c) > (targ0:isp0:0:0:0): getccb 0xc24ec900 > (targ0:isp0:0:0:0): sendccb 0xc24ec900 > (targ0:isp0:0:0:0): targreturnccb 0xc24ec900 > (targ0:isp0:0:0:0): write - uio_resid 4 > (targ0:isp0:0:0:0): getccb 0xc24ec900 Well, what initiator are you using? 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.) Anyway, the autosense thing is definitely one thing that you'll need to tweak in order for it to work right with Fibre channel. You can try increasing the number of initiators if it looks like you're running out of CCBs. Also, I found that if you use Linux as the initiator, with Qlogic's driver, scsi_target(8) has problems when it gets the report luns command. I didn't have enough time when I was messing with it to figure out why. It should have just rejected the command, but that didn't seem to be happening. (It could also have had something to do with my hacks to take out the aio backend and do a fake ramdisk.) FreeBSD works fine as an initiator, and as a bonus, rescanning works a lot better. :) Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 12 20:56:27 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 367E037B401; Tue, 12 Aug 2003 20:56:27 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7098343F93; Tue, 12 Aug 2003 20:56:26 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Tue, 12 Aug 2003 23:56:24 -0400 Message-ID: From: Don Bowman To: Don Bowman , "'freebsd-scsi@freebsd.org'" , "'aic7xxx@freebsd.org'" Date: Tue, 12 Aug 2003 23:56:22 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Ongoing U320 AIC7902 Seagate ST318453LW issues, SCB timed out 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: Wed, 13 Aug 2003 03:56:27 -0000 What causes a "No or incomplete CDB sent to device." ? <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> (da0:ahd0:0:0:0): No or incomplete CDB sent to device. ahd0: Issued Channel A Bus Reset. 36 SCBs aborted (da0:ahd0:0:0:0): SCB 0x18 - timed out From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 12 20:58:18 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 940E237B401; Tue, 12 Aug 2003 20:58:18 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82AF943FBD; Tue, 12 Aug 2003 20:58:17 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Tue, 12 Aug 2003 23:58:17 -0400 Message-ID: From: Don Bowman To: Don Bowman , "'freebsd-scsi@freebsd.org'" , "'aic7xxx@freebsd.org'" Date: Tue, 12 Aug 2003 23:58:16 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Ongoing U320 AIC7902 Seagate ST318453LW issues, SCB timed out 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: Wed, 13 Aug 2003 03:58:19 -0000 > What causes a "No or incomplete CDB sent to device." ? > > <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> > (da0:ahd0:0:0:0): No or incomplete CDB sent to device. > ahd0: Issued Channel A Bus Reset. 36 SCBs aborted > (da0:ahd0:0:0:0): SCB 0x18 - timed out > or: <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> (da0:ahd0:0:0:0): No or incomplete CDB sent to device. ahd0: Issued Channel A Bus Reset. 35 SCBs aborted (da0:ahd0:0:0:0): Unexpected busfree in Data-in phase, 1 SCBs aborted, PRGMCNT = = 0x96 From owner-freebsd-scsi@FreeBSD.ORG Wed Aug 13 07:24:49 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 CD21E37B405 for ; Wed, 13 Aug 2003 07:24:49 -0700 (PDT) Received: from postfix.arnes.si (kanin.arnes.si [193.2.1.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A22843FD7 for ; Wed, 13 Aug 2003 07:24:47 -0700 (PDT) (envelope-from david.vrtin@arnes.si) Received: from rzenik.arnes.si (rzenik.arnes.si [193.2.1.232]) by postfix.arnes.si (Postfix) with ESMTP id 69B06A9CED for ; Wed, 13 Aug 2003 16:24:46 +0200 (MET DST) Received: from rzenik (localhost [127.0.0.1]) by rzenik.arnes.si (Postfix) with ESMTP id 22A5F42B43 for ; Wed, 13 Aug 2003 16:24:46 +0200 (MET DST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Aug 2003 16:24:46 +0200 From: David Vrtin Message-Id: <20030813142446.22A5F42B43@rzenik.arnes.si> Subject: LTO2 tape drives and FreeBSD 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: Wed, 13 Aug 2003 14:24:50 -0000 Hi Which LTO2 tape drives are supported in FreeBSD? DELL PowerVault 132T with 2 LTO2 drives is supported? Any experience with LTO2 tapes on FreeBSD? Thanks for any help! Best regards, David From owner-freebsd-scsi@FreeBSD.ORG Wed Aug 13 07:52:41 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 884D937B401; Wed, 13 Aug 2003 07:52:41 -0700 (PDT) Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com [194.25.134.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16C4643FAF; Wed, 13 Aug 2003 07:52:40 -0700 (PDT) (envelope-from Jan.Stocker@t-online.de) Received: from fwd05.aul.t-online.de by mailout03.sul.t-online.com with smtp id 19mwzI-000302-09; Wed, 13 Aug 2003 16:52:32 +0200 Received: from [10.1.2.252] (VgHuK-Zege560HnaCcYMBQbDOIF1kcy6apX+njhvu-ppjhNnpgpC0t@[217.82.129.17]) by fwd05.sul.t-online.com with esmtp id 19mwzB-23jUX20; Wed, 13 Aug 2003 16:52:25 +0200 From: Jan.Stocker@t-online.de (Jan Stocker) To: Nate Lawson In-Reply-To: <20030728212246.Q53955@root.org> References: <20030728212246.Q53955@root.org> Content-Type: text/plain Message-Id: <1060786289.671.9.camel@Twoflower.liebende.de> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Wed, 13 Aug 2003 14:51:30 +0000 Content-Transfer-Encoding: 7bit X-Seen: false X-ID: VgHuK-Zege560HnaCcYMBQbDOIF1kcy6apX+njhvu-ppjhNnpgpC0t cc: current@freebsd.org cc: scsi@freebsd.org Subject: USB connects my DigiCam to 8 devices the same time..... 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: Wed, 13 Aug 2003 14:52:42 -0000 After attaching my digicam (new kernel without quirks): Aug 13 16:39:50 Twoflower kernel: umass0: MINOLTA DIMAGE 2330 ZOOM DIMAGE2330ZOOM, rev 1.00/1.00, addr 2 Aug 13 16:39:50 Twoflower kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Aug 13 16:39:50 Twoflower kernel: da0: Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da0: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da0: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da1 at umass-sim0 bus 0 target 0 lun 1 Aug 13 16:39:50 Twoflower kernel: da1: Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da1: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da1: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da2 at umass-sim0 bus 0 target 0 lun 2 Aug 13 16:39:50 Twoflower kernel: da2: Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da2: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da2: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da3 at umass-sim0 bus 0 target 0 lun 3 Aug 13 16:39:50 Twoflower kernel: da3: Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da3: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da3: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da4 at umass-sim0 bus 0 target 0 lun 4 Aug 13 16:39:50 Twoflower kernel: da4: Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da4: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da4: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da5 at umass-sim0 bus 0 target 0 lun 5 Aug 13 16:39:50 Twoflower kernel: da5: Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da5: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da5: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da6 at umass-sim0 bus 0 target 0 lun 6 Aug 13 16:39:50 Twoflower kernel: da6: Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da6: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da6: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da7 at umass-sim0 bus 0 target 0 lun 7 Aug 13 16:39:50 Twoflower kernel: da7: Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da7: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da7: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:40:16 Twoflower kernel: umass0: at uhub0 port 1 (addr 2) disconnected Aug 13 16:40:16 Twoflower kernel: (da0:umass-sim0:0:0:0): lost device Aug 13 16:40:16 Twoflower kernel: (da0:umass-sim0:0:0:0): removing device entry Aug 13 16:40:16 Twoflower kernel: (da1:umass-sim0:0:0:1): lost device Aug 13 16:40:16 Twoflower kernel: (da1:umass-sim0:0:0:1): removing device entry Aug 13 16:40:16 Twoflower kernel: (da2:umass-sim0:0:0:2): lost device Aug 13 16:40:16 Twoflower kernel: (da2:umass-sim0:0:0:2): removing device entry Aug 13 16:40:16 Twoflower kernel: (da3:umass-sim0:0:0:3): lost device Aug 13 16:40:16 Twoflower kernel: (da3:umass-sim0:0:0:3): removing device entry Aug 13 16:40:16 Twoflower kernel: (da4:umass-sim0:0:0:4): lost device Aug 13 16:40:16 Twoflower kernel: (da4:umass-sim0:0:0:4): removing device entry Aug 13 16:40:16 Twoflower kernel: (da5:umass-sim0:0:0:5): lost device Aug 13 16:40:16 Twoflower kernel: (da5:umass-sim0:0:0:5): removing device entry Aug 13 16:40:16 Twoflower kernel: (da6:umass-sim0:0:0:6): lost device Aug 13 16:40:16 Twoflower kernel: (da6:umass-sim0:0:0:6): removing device entry Aug 13 16:40:16 Twoflower kernel: (da7:umass-sim0:0:0:7): lost device Aug 13 16:40:16 Twoflower kernel: (da7:umass-sim0:0:0:7): removing device entry Aug 13 16:40:16 Twoflower kernel: umass0: detached -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d-(+) s-:- a- C+++>++ UB++++ P+++ L- E--- W N+ o-- K? w++++$ O- M- V- PS PE? Y+ PGP+ t+() 5- X+ R+ tv- b++(+++) DI D--- G- e+++ h-- r++ z+ ------END GEEK CODE BLOCK------ From owner-freebsd-scsi@FreeBSD.ORG Wed Aug 13 08:26:56 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 3410A37B401; Wed, 13 Aug 2003 08:26:56 -0700 (PDT) Received: from gpu.utcc.utoronto.ca (gpu.utcc.utoronto.ca [128.100.100.1]) by mx1.FreeBSD.org (Postfix) with SMTP id 413C143F93; Wed, 13 Aug 2003 08:26:55 -0700 (PDT) (envelope-from dky@utcc.utoronto.ca) Received: from localhost by gpu.utcc.utoronto.ca with SMTP id <41639>; Wed, 13 Aug 2003 11:26:53 -0400 Date: Wed, 13 Aug 2003 11:26:50 -0400 From: Derek Yeung To: Don Bowman In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "'freebsd-scsi@freebsd.org'" cc: "'aic7xxx@freebsd.org'" Subject: RE: Ongoing U320 AIC7902 Seagate ST318453LW issues, SCB timed out 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: Wed, 13 Aug 2003 15:26:56 -0000 Hello, I'm running RedHat 9 Stock Kernel, Adaptec 39320D-R / AIC7902 with Seagate 36GB U320 disks I was wondering if someone can help me identify what dev 08:61 is and perhaps what these errors mean? Aug 13 00:07:38 bureau17 kernel: scsi1: ERROR on channel 0, id 2, lun 0, CDB: Read (10) 00 00 06 3f d7 00 01 00 00 Aug 13 00:07:38 bureau17 kernel: Info fld=0x640c3, Current sd08:61: sense key Medium Error Aug 13 00:07:38 bureau17 kernel: Additional sense indicates Unrecovered read error Aug 13 00:07:38 bureau17 kernel: I/O error: dev 08:61, sector 409728 Aug 13 00:07:47 bureau17 kernel: scsi1: ERROR on channel 0, id 2, lun 0, CDB: Read (10) 00 00 06 40 bf 00 00 08 00 Aug 13 00:07:47 bureau17 kernel: Info fld=0x640c3, Current sd08:61: sense key Medium Error Aug 13 00:07:47 bureau17 kernel: Additional sense indicates Unrecovered read error Aug 13 00:07:47 bureau17 kernel: I/O error: dev 08:61, sector 409728 Thanks very very much, /dky From owner-freebsd-scsi@FreeBSD.ORG Wed Aug 13 09:52:54 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 8DD5637B401; Wed, 13 Aug 2003 09:52:54 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3B5143FAF; Wed, 13 Aug 2003 09:52:53 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h7DGqro06129; Wed, 13 Aug 2003 09:52:53 -0700 Received: from [10.100.253.70] (aslan.btc.adaptec.com [10.100.253.70]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id JAA11104; Wed, 13 Aug 2003 09:52:52 -0700 (PDT) Date: Wed, 13 Aug 2003 10:54:34 -0600 From: "Justin T. Gibbs" To: Derek Yeung , Don Bowman Message-ID: <3190142704.1060793674@aslan.btc.adaptec.com> In-Reply-To: References: X-Mailer: Mulberry/3.1.0b5 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: "'freebsd-scsi@freebsd.org'" cc: "'aic7xxx@freebsd.org'" Subject: RE: Ongoing U320 AIC7902 Seagate ST318453LW issues, SCB timed out X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Justin T. Gibbs" List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2003 16:52:54 -0000 > > Hello, > > I'm running RedHat 9 Stock Kernel, Adaptec 39320D-R / AIC7902 with Seagate > 36GB U320 disks Please do not post a Linux question to the FreeBSD-SCSI list. Linux has its own lists. > I was wondering if someone can help me identify what dev 08:61 is and > perhaps what these errors mean? The errors mean that your disk drive is having media failures and cannot read certain sectors. The disk is at id2 on channel 0 of your 39320. You should probably replace the drive. -- Justin 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 From owner-freebsd-scsi@FreeBSD.ORG Thu Aug 14 09:22:57 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 0949E37B401 for ; Thu, 14 Aug 2003 09:22:57 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 82A7E43FDD for ; Thu, 14 Aug 2003 09:22:56 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 93608 invoked by uid 1000); 14 Aug 2003 16:22:57 -0000 Date: Thu, 14 Aug 2003 09:22:57 -0700 (PDT) From: Nate Lawson To: Chuck Tuffli In-Reply-To: <20030814011111.GB3594@cre85086tuf.rose.agilent.com> Message-ID: <20030814092214.C93571@root.org> References: <20030813034951.GA91644@panzer.kdm.org> <20030814011111.GB3594@cre85086tuf.rose.agilent.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org cc: "Kenneth D. Merry" 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 16:22:57 -0000 On Wed, 13 Aug 2003, Chuck Tuffli wrote: > 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! Glad to hear you got it working. I am planning to do some testing and finish the userland emulator at some point in the near future (next few months). -Nate From owner-freebsd-scsi@FreeBSD.ORG Thu Aug 14 12:44:23 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 143FE37B401 for ; Thu, 14 Aug 2003 12:44:23 -0700 (PDT) Received: from dsihi.com (cust13098.lava.net [64.65.83.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3B9243F85 for ; Thu, 14 Aug 2003 12:44:21 -0700 (PDT) (envelope-from john@dsihi.com) Received: from dsijk ([190.0.0.149]) by dsihi.com (8.10.1/8.10.1) with SMTP id h7EJk1H29330 for ; Thu, 14 Aug 2003 09:46:01 -1000 (HST) Message-ID: <003601c3629b$4912fd20$950000be@dsijk> From: "John Kamei" To: Date: Thu, 14 Aug 2003 09:35:58 -1000 Organization: DSI of Hawaii MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: AIC-7902 problems X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John Kamei List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Aug 2003 19:44:23 -0000 > FWIW, we have just run into the same issue with new supermicro > X5 motherboards as well. Downgrading the system bios to c182 from > 1.3c (no idea what these mean:) made the problem go away. > We are working with supermicro support on it right now. As I mentioned to Don in private email, I believe that this problem is caused by an errata in the P64H2 PCI-X hub. Information about this errata can be found here: http://developer.intel.com/design/chipsets/e7500/specupdt/290735.htm My suspicion is that the SCBs for some transactions are getting partially corrupted so the command that we think we are sending to the drive is not really getting sent. A good way to verify this is to force the PCI-X bus into PCI mode. The problem is supposed to only occur if there is another device on the PCI-X bus sharing the 7902, but it would not surprise me if the 7902 could also be hit with an unexpected GNT. I will be working with Supermicro to see if I can get both a PCI-X and SCSI bus trace to help isolate the problem. -- Justin Have these problems been resolved? Is the only way to get around this is to turn off packetization on the BIOS? Thanks From owner-freebsd-scsi@FreeBSD.ORG Thu Aug 14 13:03:08 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 A634237B401 for ; Thu, 14 Aug 2003 13:03:08 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A00443FA3 for ; Thu, 14 Aug 2003 13:03:08 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h7EK37o02548; Thu, 14 Aug 2003 13:03:07 -0700 Received: from [10.100.253.70] (aslan.btc.adaptec.com [10.100.253.70]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id NAA09776; Thu, 14 Aug 2003 13:03:06 -0700 (PDT) Date: Thu, 14 Aug 2003 14:04:52 -0600 From: "Justin T. Gibbs" To: John Kamei , freebsd-scsi@freebsd.org Message-ID: <3766522704.1060891492@aslan.btc.adaptec.com> In-Reply-To: <003601c3629b$4912fd20$950000be@dsijk> References: <003601c3629b$4912fd20$950000be@dsijk> X-Mailer: Mulberry/3.1.0b5 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: AIC-7902 problems X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Justin T. Gibbs" List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Aug 2003 20:03:08 -0000 If you are going to quote me, please do so properly so that it is obvious that you are quoting someone else. ... > Have these problems been resolved? Is the only way to get around this is to > turn off packetization on the BIOS? As far as I know, you should have no problems if you are running with the latest Supermicro BIOS for these motherboards. -- Justin