From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 12 20:54:38 2007 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1E9E16A420 for ; Wed, 12 Dec 2007 20:54:38 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 802D913C45B for ; Wed, 12 Dec 2007 20:54:37 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 38716 invoked from network); 12 Dec 2007 20:27:54 -0000 Received: from 209-128-117-003.bayarea.net (HELO ?10.0.8.5?) (nate-mail@209.128.117.3) by root.org with ESMTPA; 12 Dec 2007 20:27:54 -0000 Message-ID: <4760446D.2060102@root.org> Date: Wed, 12 Dec 2007 12:28:29 -0800 From: Nate Lawson User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Sean Bruno References: <1197420795.2738.6.camel@iago.office.miralink.com> <86sl28snpe.wl%simokawa@FreeBSD.ORG> <1197425759.14437.0.camel@home-desk> <626eb4530712111837y4608e919w845461d36a18118f@mail.gmail.com> <475F5669.1010800@miralink.com> <476034FE.7080003@miralink.com> In-Reply-To: <476034FE.7080003@miralink.com> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Hidetoshi Shimokawa , freebsd-firewire@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: scsi_target witness lock error X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Dec 2007 20:54:38 -0000 Sean Bruno wrote: > Alrighty, a little cleaner patch to allow sbp_targ.c to acutally work > under RELENG_6. http://www.consultcsg.com/RELENG_6.diff > > Also and update with the witness error. And the kernel config I am using: > http://www.consultcsg.com/scsitarget_witness.txt > http://www.consultcsg.com/FIREWIRE_TGT > > Is scsi_target the only application that is making this kern env witness > error appear? I find it hard to believe that nothing else in the code > base hits this type of problem? Apparently scsi_target wasn't fully tested when the CAM locking went in. It was written before there was a design for CAM locking so it may need some reworking. For example, it assumes that it should acquire/drop locks multiple times in its start method if there are multiple CCBs queued. That may not be the fastest way, depending on contention for the SIM lock. -- Nate