From owner-freebsd-current@FreeBSD.ORG Wed Nov 5 16:17:30 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33F531065673; Wed, 5 Nov 2008 16:17:30 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.freebsd.org (Postfix) with ESMTP id D6A538FC14; Wed, 5 Nov 2008 16:17:28 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=bdeZpJpNa0wA:10 a=SER6hIBTabIA:10 a=d6BVkb5LuPPVEe4iNQMLyA==:17 a=trMMR0braKzLU2WKjEgA:9 a=tDSluKevbQ2ZOlGICIyAjUXvPzwA:4 a=9aOQ2cSd83gA:10 a=LY0hPdMaydYA:10 Received: from [62.113.135.6] (account mc467741@c2i.net [62.113.135.6] verified) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1140792857; Wed, 05 Nov 2008 17:17:26 +0100 From: Hans Petter Selasky To: "M. Warner Losh" Date: Wed, 5 Nov 2008 17:19:29 +0100 User-Agent: KMail/1.9.7 References: <20081104220725.GC8256@e.0x20.net> <200811050914.44225.hselasky@c2i.net> <20081105.021817.-332174942.imp@bsdimp.com> In-Reply-To: <20081105.021817.-332174942.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811051719.30962.hselasky@c2i.net> Cc: current@freebsd.org, bright@mu.org, rbgarga@gmail.com, freebsd-current@freebsd.org, freebsd-usb@freebsd.org, lme@freebsd.org Subject: Re: USB4BSD release candidate number 3 - request for review X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2008 16:17:30 -0000 On Wednesday 05 November 2008, M. Warner Losh wrote: > In message: <200811050914.44225.hselasky@c2i.net> > > : It is not a USB problem. It is the CAM layer that is hanging on the disk. > > Sure it is CAM layer and not buffer cache or filesystem code? > No, I'm not sure, except it is not an USB problem. I currently keep the CAM instance around after that the device has been removed from USB, returning an error on all subsequent SCSI requests. --HPS