From owner-freebsd-current@FreeBSD.ORG Thu Sep 11 08:11:35 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD7351065676; Thu, 11 Sep 2008 08:11:35 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.freebsd.org (Postfix) with ESMTP id 2E3098FC22; Thu, 11 Sep 2008 08:11:34 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=3dBypTT4MX8A:10 a=FyBB3-7IvmoA:10 a=ZtwMFzhc6XSROYQlMkMA/A==:17 a=PLKaUx0NHm0iIjSv34UA:9 a=avy4jcLu0dMg-gKMBLBrV-n4OQoA:4 a=LY0hPdMaydYA:10 Received: from [62.113.133.218] (account mc467741@c2i.net [62.113.133.218] verified) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 21348764; Thu, 11 Sep 2008 10:11:32 +0200 From: Hans Petter Selasky To: Volker Date: Thu, 11 Sep 2008 10:13:22 +0200 User-Agent: KMail/1.9.7 References: <20080819211814.6CD685B4D@mail.bitblocks.com> <48B0EA50.2090105@mawer.org> <48B3299F.5080101@vwsoft.com> In-Reply-To: <48B3299F.5080101@vwsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809111013.23994.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org, current@freebsd.org, "M. Warner Losh" , Antony Mawer Subject: Re: "legacy" usb stack fixes (was: Re: HEADSUP new usb code coming in.) 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: Thu, 11 Sep 2008 08:11:35 -0000 On Monday 25 August 2008, Volker wrote: > > > Anyway, I've already had those crashes even with the "new" usb stack > (but it doesn't happen everytime - YMMV). > Hi, I also see crashes with my new stuff and the umass driver when the USB device is un-plugged too early. The backtraces I've got so far does not indicate a USB problem, though .... --HPS