From owner-freebsd-current@FreeBSD.ORG Wed Nov 5 16:03:02 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 4A4FF1065695; Wed, 5 Nov 2008 16:03:02 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 07B808FC08; Wed, 5 Nov 2008 16:03:01 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id mA5Fxwsl030798; Wed, 5 Nov 2008 08:59:58 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 05 Nov 2008 09:01:11 -0700 (MST) Message-Id: <20081105.090111.-861032299.imp@bsdimp.com> To: rink@freebsd.org From: "M. Warner Losh" In-Reply-To: <20081105100433.GA43232@rink.nu> References: <200811050914.44225.hselasky@c2i.net> <20081105.021817.-332174942.imp@bsdimp.com> <20081105100433.GA43232@rink.nu> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: current@freebsd.org, bright@mu.org, hselasky@c2i.net, lme@freebsd.org, freebsd-current@freebsd.org, freebsd-usb@freebsd.org, rbgarga@gmail.com 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:03:02 -0000 In message: <20081105100433.GA43232@rink.nu> Rink Springer writes: : On Wed, Nov 05, 2008 at 02:18:17AM -0700, M. Warner Losh wrote: : > In message: <200811050914.44225.hselasky@c2i.net> : > Hans Petter Selasky writes: : > : On Wednesday 05 November 2008, Lars Engels wrote: : > : > Mounting a umass device, removing it and doing an 'ls' on the mountpoint : > : > freezes the system, I thought this should not happen with the new stack? : > : : > : 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? : : Well, the CAM layer problem will immediately first - it does not like : CAM busses disappearing. Once this is fixed or avoided and the problem : still shows up, we can blame buffer cache / filesystem code. : : As I suggested before, a good fix is to create one CAM bus per USB root : hub, and use that to attach all umass devices to. This will also get rid : of the one-bus-per-umass-device which is visually unappealling. That might work. It might also be useful to see if the DragonFly patches to allow this port over or not... Warner