From owner-freebsd-usb@FreeBSD.ORG Mon May 2 06:30:15 2011 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABFDD1065673 for ; Mon, 2 May 2011 06:30:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9C82A8FC16 for ; Mon, 2 May 2011 06:30:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p426UF20078032 for ; Mon, 2 May 2011 06:30:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p426UFej078028; Mon, 2 May 2011 06:30:15 GMT (envelope-from gnats) Date: Mon, 2 May 2011 06:30:15 GMT Message-Id: <201105020630.p426UFej078028@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Hans Petter Selasky Cc: Subject: Re: usb/156725: USB stack stall cause complete system input loss X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hans Petter Selasky List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2011 06:30:15 -0000 The following reply was made to PR usb/156725; it has been noted by GNATS. From: Hans Petter Selasky To: freebsd-usb@freebsd.org, FreeBSD-gnats-submit@freebsd.org Cc: linimon@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: usb/156725: USB stack stall cause complete system input loss Date: Mon, 2 May 2011 08:28:48 +0200 On Monday 02 May 2011 02:26:29 linimon@freebsd.org wrote: > Synopsis: USB stack stall cause complete system input loss > > Responsible-Changed-From-To: freebsd-amd64->freebsd-usb > Responsible-Changed-By: linimon > Responsible-Changed-When: Mon May 2 00:25:49 UTC 2011 > Responsible-Changed-Why: > reclassify. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=156725 Hi, All attach and detach methods are run from a single thread, the root HUB thread. If any device driver is blocking the detach routine for some reason, other devices on the same USB controller will be prevented from enumerating aswell. --HPS