From owner-freebsd-current@FreeBSD.ORG Sat Mar 28 09:58:05 2009 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 42B3E1065670; Sat, 28 Mar 2009 09:58:05 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id 7899B8FC13; Sat, 28 Mar 2009 09:58:04 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=YzV9F2SBnUsA:10 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=M3u0mSUAQvXDMBrYJysA:9 a=bRha355O32NOxW_ZTU8A:7 a=FvJHxpOHjkXp_08be0YydoDBEwYA:4 a=LY0hPdMaydYA:10 a=aFaPMYQp8PMbobuw:21 a=kQ1_zI9j1OA0SKLK:21 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1220195322; Sat, 28 Mar 2009 10:58:03 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sat, 28 Mar 2009 11:00:32 +0100 User-Agent: KMail/1.9.7 References: <20090328095030.GD64269@e.0x20.net> In-Reply-To: <20090328095030.GD64269@e.0x20.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200903281100.33957.hselasky@c2i.net> Cc: Lars Engels , current@freebsd.org Subject: Re: Problems with usb bluetooth device 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: Sat, 28 Mar 2009 09:58:05 -0000 On Saturday 28 March 2009, Lars Engels wrote: > Hi all, > > yesterday I bought a shiny new hama usb bluetooth dongle but I am having > some problems using it: > > before loading ng_ubt: > usb2_alloc_device:1480: set address 2 failed (ignored) > usb2_alloc_device:1516: getting device descriptor at addr 2 failed! > usb2_req_re_enumerate:1421: addr=2, set address failed! (ignored) > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > usb2_req_re_enumerate:1421: addr=2, set address failed! (ignored) > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > ugen0.2: <> at usbus0 (disconnected) > after loading ng_ubt: > uhub_reattach_port:413: could not allocate new device! > ubt0: 2.00/1.00, addr 2> on usbus2 ^^^^^^^^^^ > internal bluetooth device > WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() > WARNING: attempt to net_add_domain(netgraph) after domainfinalize() > ugen0.2: at usbus0 > ubt1: 2.00/48.39, addr 2> on usbus0 ubt1: ubt_bulk_read_callback:837: bulk-in > transfer failed: USB_ERR_STALLED ubt1: ubt_intr_read_callback:741: > interrupt transfer failed: USB_ERR_STALLED ubt1: at uhub0, port 1, addr 2 > (disconnected) > ugen0.2: at usbus0 (disconnected) > device re-inserted: > usb2_alloc_device:1480: set address 2 failed (ignored) > usb2_alloc_device:1516: getting device descriptor at addr 2 failed! > usb2_req_re_enumerate:1421: addr=2, set address failed! (ignored) > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > usb2_req_re_enumerate:1421: addr=2, set address failed! (ignored) > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > ugen0.2: <> at usbus0 (disconnected) > uhub_reattach_port:413: could not allocate new device! > > So the device is no longer recognized after I re-connect it. usbconfig does > not show it: ugen0.1: at usbus0, cfg=0 md=HOST > spd=FULL (12Mbps) pwr=ON ugen1.1: at usbus1, cfg=0 > md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: at usbus2, > cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: at > usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: Intel> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen2.2: Bluetooth 2.0 plus EDR Broadcom Corp> at usbus2, cfg=0 md=HOST spd=FULL > (12Mbps > pwr=ON > > It only lists the internal device... > > My CURRENT was compiled two days ago, so I should be up-to-date. Does it work when you use an external USB HUB? Does this device have some kind of autoinstall on it? You could try enabling uhci/ehci debugging. sysctl hw.usb2.uhci.debug = 15 Then we would know the exact cause of the error. --HPS