From owner-freebsd-usb@FreeBSD.ORG Sat Aug 10 15:10:03 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 D933E14B for ; Sat, 10 Aug 2013 15:10:03 +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 C68322145 for ; Sat, 10 Aug 2013 15:10:03 +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 r7AFA2AY024895 for ; Sat, 10 Aug 2013 15:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r7AFA2pE024894; Sat, 10 Aug 2013 15:10:02 GMT (envelope-from gnats) Date: Sat, 10 Aug 2013 15:10:02 GMT Message-Id: <201308101510.r7AFA2pE024894@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org Cc: From: Antonis Anastasiadis Subject: Re: usb/181159: Problem attaching USB device X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Antonis Anastasiadis 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:10:03 -0000 The following reply was made to PR usb/181159; it has been noted by GNATS. From: Antonis Anastasiadis To: Hans Petter Selasky Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: usb/181159: Problem attaching USB device Date: Sat, 10 Aug 2013 17:53:47 +0300 =D3=F4=E9=F2 10 =C1=F5=E3 2013, 4:52 =EC.=EC., =EF/=E7 Hans Petter = Selasky =DD=E3=F1=E1=F8=E5: >=20 > Try to double the values one by one. >=20 > Any change? >=20 > Need to reboot or re-plug the device before testing. >=20 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.=