From owner-freebsd-current@FreeBSD.ORG Sat Aug 10 13:22:42 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5B089B36; Sat, 10 Aug 2013 13:22:42 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E187F2BB6; Sat, 10 Aug 2013 13:22:41 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 64A6F6A6004; Sat, 10 Aug 2013 15:22:39 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id r7ADMdWn058559; Sat, 10 Aug 2013 15:22:39 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.7/8.14.7/Submit) id r7ADMd92057441; Sat, 10 Aug 2013 15:22:39 +0200 (CEST) (envelope-from lars) Date: Sat, 10 Aug 2013 15:22:39 +0200 From: Lars Engels To: Hans Petter Selasky Subject: Re: Problems with usb bluetooth device Message-ID: <20130810132239.GR85426@e-new.0x20.net> References: <20090328095030.GD64269@e.0x20.net> <200903281100.33957.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kg2J3k9IiiSZbiqb" Content-Disposition: inline In-Reply-To: <200903281100.33957.hselasky@c2i.net> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.4-RELEASE User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org, current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 10 Aug 2013 13:22:42 -0000 --Kg2J3k9IiiSZbiqb Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 28, 2009 at 11:00:32AM +0100, Hans Petter Selasky wrote: > 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=3D2, set address failed! (ignored) > > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 faile= d! > > usb2_req_re_enumerate:1421: addr=3D2, set address failed! (ignored) > > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 faile= d! > > 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=3D2, set address failed! (ignored) > > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 faile= d! > > usb2_req_re_enumerate:1421: addr=3D2, set address failed! (ignored) > > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 faile= d! > > 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=3D0 md=3DHOST > > spd=3DFULL (12Mbps) pwr=3DON ugen1.1: at usbus1, = cfg=3D0 > > md=3DHOST spd=3DFULL (12Mbps) pwr=3DON ugen2.1: a= t usbus2, > > cfg=3D0 md=3DHOST spd=3DFULL (12Mbps) pwr=3DON ugen3.1: at > > usbus3, cfg=3D0 md=3DHOST spd=3DFULL (12Mbps) pwr=3DON ugen4.1: > Intel> at usbus4, cfg=3D0 md=3DHOST spd=3DHIGH (480Mbps) pwr=3DON ugen2= =2E2: > Bluetooth 2.0 plus EDR Broadcom Corp> at usbus2, cfg=3D0 md=3DHOST spd= =3DFULL > > (12Mbps = =20 > > pwr=3DON > > > > It only lists the internal device... > > > > My CURRENT was compiled two days ago, so I should be up-to-date. >=20 > Does it work when you use an external USB HUB? >=20 > Does this device have some kind of autoinstall on it? >=20 > You could try enabling uhci/ehci debugging. > sysctl hw.usb2.uhci.debug =3D 15 >=20 > Then we would know the exact cause of the error. Just for your info: Aug 10 15:21:45 milhouse kernel: ubt1: on usbus3 Aug 10 15:21:45 milhouse devd: Executing '/etc/rc.d/bluetooth quietstart ub= t1' After 4 years, the device now works without an external hub. ;-)) Lars --Kg2J3k9IiiSZbiqb Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iEYEARECAAYFAlIGPp8ACgkQKc512sD3afhiigCgkPl+RABCQj3XQvrjFyFU/7Cp 0CIAoLPB+wkWQXd0/ImE+fGQpbT//SLH =6p8/ -----END PGP SIGNATURE----- --Kg2J3k9IiiSZbiqb--