From owner-freebsd-usb@FreeBSD.ORG Sat Jul 23 15:44:12 2011 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 564801065670 for ; Sat, 23 Jul 2011 15:44:12 +0000 (UTC) (envelope-from peerst@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0CA128FC12 for ; Sat, 23 Jul 2011 15:44:11 +0000 (UTC) Received: by vws18 with SMTP id 18so2945949vws.13 for ; Sat, 23 Jul 2011 08:44:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=YH6mFELl9xSj2xIEqdXcWKHo6pHQR9KrkTVK004dBQU=; b=LG5Eq61zDOI6rlVRvQhHHQD7K95d/lEs9MM2Rx/Lr0/2u/ePcIWjMz+1eIusjPEiBg AVb8l14LOgeU4N4Z40KdNNpmLoEhD+pJDMjJUQ3F+plVm/KUMfS11yNXiGhPLr16/Yd8 u+xO9bv1podc9Tcne85intpaq/VGCkJFvUyBI= MIME-Version: 1.0 Received: by 10.52.31.38 with SMTP id x6mr2750866vdh.492.1311435851192; Sat, 23 Jul 2011 08:44:11 -0700 (PDT) Received: by 10.52.188.102 with HTTP; Sat, 23 Jul 2011 08:44:11 -0700 (PDT) In-Reply-To: <201107231717.34403.hselasky@c2i.net> References: <201107211249.03972.hselasky@c2i.net> <201107231717.34403.hselasky@c2i.net> Date: Sat, 23 Jul 2011 17:44:11 +0200 Message-ID: From: Peer Stritzinger To: Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-usb Subject: Re: Powercycling USB device on hub X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jul 2011 15:44:12 -0000 Hi, On Sat, Jul 23, 2011 at 5:17 PM, Hans Petter Selasky wro= te: > On Saturday 23 July 2011 17:18:34 Peer Stritzinger wrote: >> =A0$ sudo usbconfig -u 3 -a 1 reset >> usbconfig: could not reset device: Device not configured >> >> and after this all devices hat are on this bus are no longer visible >> to usbconfig until the next reboot. > > This is a known issue which was fixed in stable. Great. Since power-cycling needs to reset the HUB I now have the problem to find out on which HUB in the system my device hangs. There are two HUB's on the same root HUB and I don't want to power-cycle all devices. Is there a way to learn the physical structure of a USB bus? -- Peer > > --HPS >