From owner-freebsd-current@FreeBSD.ORG Wed Nov 5 09:17:23 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 A1FD11065670; Wed, 5 Nov 2008 09:17:23 +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 5FDC88FC1D; Wed, 5 Nov 2008 09:17:23 +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 mA59H5xB019545; Wed, 5 Nov 2008 02:17:05 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 05 Nov 2008 02:18:17 -0700 (MST) Message-Id: <20081105.021817.-332174942.imp@bsdimp.com> To: hselasky@c2i.net From: "M. Warner Losh" In-Reply-To: <200811050914.44225.hselasky@c2i.net> References: <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> <200811050914.44225.hselasky@c2i.net> 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, 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 09:17:23 -0000 In message: <200811050914.44225.hselasky@c2i.net> Hans Petter Selasky writes: : On Wednesday 05 November 2008, Lars Engels wrote: : : Hi Lars, : : > Now I just removed everything but usb2_core from the kernel config and : > load the modules manually. So far it runs pretty good. : > : > 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? Warner