From owner-freebsd-usb@FreeBSD.ORG Thu Nov 10 08:32:02 2011 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 8B0F91065674 for ; Thu, 10 Nov 2011 08:32:02 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe08.c2i.net [212.247.154.226]) by mx1.freebsd.org (Postfix) with ESMTP id 1B4B98FC0C for ; Thu, 10 Nov 2011 08:32:01 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe08.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 202529327; Thu, 10 Nov 2011 09:31:59 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Thu, 10 Nov 2011 09:29:07 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <86FB7D63AF95574BB762C0C3E1F269150F8F50A5@RTPMVEXC1-PRD.hq.netapp.com> In-Reply-To: <86FB7D63AF95574BB762C0C3E1F269150F8F50A5@RTPMVEXC1-PRD.hq.netapp.com> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201111100929.07536.hselasky@c2i.net> Cc: "Shah, Vishal" , "Ranaweera, Samantha" Subject: Re: usb_alloc_device: Failure selecting configuration index 0:USB_ERR_TIMEOUT, port 1, addr 2 (ignored) 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, 10 Nov 2011 08:32:02 -0000 On Thursday 10 November 2011 05:08:30 Shah, Vishal wrote: > usb_alloc_device: Failure selecting configuration index > 0:USB_ERR_TIMEOUT, port 1, addr 2 (ignored)\r\r\n Hi, The set config message is sent on the control endpoint. The set config message doesn't have any data stage, so the USB stack is waiting for the status stage callback. Either that is caused by: 1) Lost interrupt on EHCI or 2) Device never sends the status stage (needs a bus analyzer for this). Quirks you can set in /boot/loader.conf: hw.usb.ehci.lostintrbug: 0 hw.usb.ehci.iaadbug: 0 --HPS