From owner-freebsd-usb@FreeBSD.ORG Sat Aug 10 15:00:01 2013 Return-Path: Delivered-To: freebsd-usb@smarthost.ysv.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 6EE0CE26 for ; Sat, 10 Aug 2013 15:00:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5BD7E20D8 for ; Sat, 10 Aug 2013 15:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r7AF01mA022945 for ; Sat, 10 Aug 2013 15:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r7AF01jO022944; Sat, 10 Aug 2013 15:00:01 GMT (envelope-from gnats) Date: Sat, 10 Aug 2013 15:00:01 GMT Message-Id: <201308101500.r7AF01jO022944@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org Cc: From: Hans Petter Selasky Subject: Re: usb/181159: Problem attaching USB device X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Hans Petter Selasky List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Aug 2013 15:00:01 -0000 The following reply was made to PR usb/181159; it has been noted by GNATS. From: Hans Petter Selasky To: Antonis Anastasiadis Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: usb/181159: Problem attaching USB device Date: Sat, 10 Aug 2013 16:57:58 +0200 On 08/10/13 16:53, Antonis Anastasiadis wrote: > > Στις 10 Αυγ 2013, 4:52 μ.μ., ο/η Hans Petter Selasky έγραψε: >> >> Try to double the values one by one. >> >> Any change? >> >> Need to reboot or re-plug the device before testing. >> > > I've managed to up them until the following values, rebooting after each change. > > hw.usb.timings.port_reset_delay: 800 > hw.usb.timings.port_root_reset_delay: 4000 > hw.usb.timings.port_reset_recovery: 4000 > hw.usb.timings.port_powerup_delay: 300 > hw.usb.timings.port_resume_delay: 640 > hw.usb.timings.set_address_settle: 160 > hw.usb.timings.resume_delay: 4000 > hw.usb.timings.resume_wait: 800 > hw.usb.timings.resume_recovery: 800 > hw.usb.timings.extra_power_up_time: 320 > > The problem still persists, although the dmesg flood rate is considerably smaller now. I guess this is to be expected. > > Unfortunately, this USB device is allocated by request for troubleshooting purposes, and I cannot have access to it for more than a few hours at a time. > Hi, I'll check the code a bit later today or tomorrow. What you could try is to identify the parent HUB or RootHUB and then set config 255 , then config 0. Maybe the device will enumerate then. usbconfig -d X.1 set_config 255 usbconfig -d X.1 set_config 0 --HPS