From owner-freebsd-current@FreeBSD.ORG Wed Nov 5 10:04:38 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 3FBF9106564A; Wed, 5 Nov 2008 10:04:38 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx1.rink.nu (gloom.rink.nu [213.34.49.2]) by mx1.freebsd.org (Postfix) with ESMTP id EF6818FC12; Wed, 5 Nov 2008 10:04:37 +0000 (UTC) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx1.rink.nu (Postfix) with ESMTP id 770646D439; Wed, 5 Nov 2008 11:04:37 +0100 (CET) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx1.rink.nu ([213.34.49.2]) by localhost (gloom.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O6cUQTZFNn5H; Wed, 5 Nov 2008 11:04:33 +0100 (CET) Received: by mx1.rink.nu (Postfix, from userid 1000) id B72EA6D42B; Wed, 5 Nov 2008 11:04:33 +0100 (CET) Date: Wed, 5 Nov 2008 11:04:33 +0100 From: Rink Springer To: "M. Warner Losh" Message-ID: <20081105100433.GA43232@rink.nu> References: <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> <200811050914.44225.hselasky@c2i.net> <20081105.021817.-332174942.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081105.021817.-332174942.imp@bsdimp.com> User-Agent: Mutt/1.5.18 (2008-05-17) 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 10:04:38 -0000 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. Regards, Rink -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder