From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 29 20:50:13 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0983C1065672 for ; Fri, 29 Apr 2011 20:50:13 +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 ED4AF8FC1D for ; Fri, 29 Apr 2011 20:50:12 +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 p3TKoCZL067547 for ; Fri, 29 Apr 2011 20:50:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p3TKoCZE067541; Fri, 29 Apr 2011 20:50:12 GMT (envelope-from gnats) Date: Fri, 29 Apr 2011 20:50:12 GMT Message-Id: <201104292050.p3TKoCZE067541@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Arnaud Lacombe X-Mailman-Approved-At: Sat, 30 Apr 2011 02:08:36 +0000 Cc: Subject: Re: amd64/156725: USB stack stall cause complete system input loss X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Arnaud Lacombe List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 20:50:13 -0000 The following reply was made to PR amd64/156725; it has been noted by GNATS. From: Arnaud Lacombe To: bug-followup@FreeBSD.org, lacombar@gmail.com Cc: Subject: Re: amd64/156725: USB stack stall cause complete system input loss Date: Fri, 29 Apr 2011 16:48:52 -0400 this bug is tightly related to amd64/156726. Considering the following scenario: 1) plug a snd_uaudio(4)-based device 2) open aumix(1) on, pcmN, the mixer device attached to the previously attached device 3) unplug the snd_uaudio(4)-based device [the USB stack busy wait pcmN detach] 4) close aumix(1) [pcmN finally detach] If there is no USB activity (ie, no attach/detach, but "normal" hid activity), the USB stack recovers. If another USB device is attached/detached while the stack busy wait on pcmN detachment (between step 3 and step 4), events ends up being queued. Once step 4 is done, events gets processed, however, once completed the USB stall, ie. no more mouse or keyboard. At this point, I do not see any USB related message while the system halts.