From owner-freebsd-usb@FreeBSD.ORG Thu Sep 11 20:13:56 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF42C106566B for ; Thu, 11 Sep 2008 20:13:56 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outS.internet-mail-service.net (outs.internet-mail-service.net [216.240.47.242]) by mx1.freebsd.org (Postfix) with ESMTP id C70CD8FC12 for ; Thu, 11 Sep 2008 20:13:56 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id C348E2447; Thu, 11 Sep 2008 13:13:56 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id ED2FA2D605F; Thu, 11 Sep 2008 13:13:55 -0700 (PDT) Message-ID: <48C97C04.6030603@elischer.org> Date: Thu, 11 Sep 2008 13:13:56 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: Volker References: <20080819211814.6CD685B4D@mail.bitblocks.com> <48B0EA50.2090105@mawer.org> <48B3299F.5080101@vwsoft.com> <200809111013.23994.hselasky@c2i.net> <48C97ACA.70307@vwsoft.com> In-Reply-To: <48C97ACA.70307@vwsoft.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Antony Mawer , freebsd-usb@freebsd.org Subject: Re: "legacy" usb stack fixes X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2008 20:13:57 -0000 Volker wrote: > On 09/11/08 10:13, Hans Petter Selasky wrote: >> 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 >> > > // dropped current@ from CC > > Hans Petter, > > the device unplug problem is not just with usb, but these devices are > the most frequent unplugged devices so far. > > Early this week, I discovered a new problem. I've fetched fresh RELENG_7 > sources, patched your usb stack in and recompiled kernel (using usb, not > usb2). > > I've seen situations with a process holding open file descriptors for a > ugen device being killed but a thread was still hanging in "usbdrain" > state (sleeping on a mutex for draining). The process is still holding > open file descriptors (I see output from ``fstat | grep ugen'' listing > the already killed process), even while the process itself is already > killed and not in the process list as a whole. > > Only a thread of that former process can be seen by ``ps -alxcH'', but > it can't be killed. what is the thread waiting on? > > I'm pretty sure I'm able to patch kern_exit.c to have that process being > freed completely but I'm also pretty sure, this will just kill a symptom > but not the source. While in that situation, the usb port does not react > to plug/unplug events anymore. > > I haven't been able to debug that situation as I do have too much stress > at other places as well. Probably I'll find the time tomorrow for debugging. > > BTW, can you give a quick explanation about usb2? What's different, > better? What needs to be done at the driver side to port something over > to usb2? > > Thanks, > > Volker > > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org"