From owner-freebsd-current Wed Nov 6 10: 3:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47DA637B401; Wed, 6 Nov 2002 10:03:31 -0800 (PST) Received: from scl8owa02.int.exodus.net (scl8out02.exodus.net [66.35.230.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id BECB843E3B; Wed, 6 Nov 2002 10:03:30 -0800 (PST) (envelope-from Maksim.Yevmenkin@exodus.net) Received: from scl8owa01.int.exodus.net ([66.35.230.241]) by scl8owa02.int.exodus.net with Microsoft SMTPSVC(5.0.2195.5329); Wed, 6 Nov 2002 10:03:30 -0800 Received: from exodus.net ([206.220.227.147]) by scl8owa01.int.exodus.net over TLS secured channel with Microsoft SMTPSVC(5.0.2195.5329); Wed, 6 Nov 2002 10:03:29 -0800 Message-ID: <3DC95971.75A58001@exodus.net> Date: Wed, 06 Nov 2002 10:03:29 -0800 From: Maksim Yevmenkin X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Josef Karthauser Cc: current@freebsd.org Subject: Re: USB problem (Who owns USB code in -current?) References: <3DC6BD74.25097511@exodus.net> <20021106130658.GB8523@genius.tao.org.uk> <3DC94D17.DC5D8D6@exodus.net> <20021106175553.GB11543@genius.tao.org.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Nov 2002 18:03:29.0781 (UTC) FILETIME=[CFE29A50:01C285BE] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Josef, > > > > This problem is FreeBSD-specific and seems related to > > > > Bluetooth USB dongles only. I have been contacted by other > > > > people who have the same problem. I do not know what is so > > > > special about Bluetooth USB dongles. USB mouse, for example, > > > > works fine. Can it be power related? Both Windows and > > > > Linux do not have this problem which makes me think that > > > > there is something different about FreeBSD way of doing > > > > things. > > > > > > Compile the kernel with 'option USB_DEBUG' and then tweak the hw.usb > > > sysctls to get debug output for your controller, the usb stack and the > > > uhub. Maybe this will shed some light on the problem. > > > > i *did* compile my kernel with USB_DEBUG and *did* tweak > > sysctl's. i even attached the dump to my previous message. > > I didn't see the dump, just the output of usbdevs. Maybe I missed it. > > > it seems there is some kind of communication error on the > > bus and stack can not get device descriptor. i need to know > > what might cause these communication errors. > > It's got to be a bug in the uhub area. You said that it works ok if the > device is plugged in directly? > > What I'd like to see is the output with: > > hw.*.usb.debug=50 > hw.*.uhub.debug=50 i set all sysctl's to 99 and put the all the dumps at http://www.geocities.com/m_evmenkin/usb/ may be attachment was too big for the list. thanks, max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message