From owner-freebsd-hackers@FreeBSD.ORG Sun May 11 05:05:10 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D955C37B401 for ; Sun, 11 May 2003 05:05:10 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.65.60]) by mx1.FreeBSD.org (Postfix) with SMTP id 7569743FA3 for ; Sun, 11 May 2003 05:05:09 -0700 (PDT) (envelope-from mdcki@gmx.net) Received: (qmail 20476 invoked by uid 65534); 11 May 2003 12:05:08 -0000 Received: from cvpn016.gwdg.de (EHLO gmx.net) (134.76.22.16) by mail.gmx.net (mp002-rz3) with SMTP; 11 May 2003 14:05:08 +0200 Message-ID: <3EBE3CB4.1000401@gmx.net> Date: Sun, 11 May 2003 14:06:12 +0200 From: Marcin Dalecki User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4a) Gecko/20030419 X-Accept-Language: en-us, en, pl, ru MIME-Version: 1.0 To: ticso@cicely.de References: <2E7E8A35375D1449A6F28D5E022E67310AC4D2@USSC8MS04.Global.Cwintra.Com> <3EBD2F95.9090807@gmx.net> <20030511005127.GD1922@cicely9.cicely.de> In-Reply-To: <20030511005127.GD1922@cicely9.cicely.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: "Yevmenkin, Maksim" Subject: Re: USB link cable? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2003 12:05:11 -0000 Bernd Walter wrote: > > > I really doubt that the udbp driver is guilty of this. > An USB driver has no chance to break a device permanently by accident > unless it has a very broken design. > > What does FreeBSD tell you now on probing the device? > The working end results in: ugen0: Prolific Technology Inc. PL2301 Host-Host interface, rev 1.00/0.00, addr 2 The kaputt end results in: ugen0: at uhub0 port 1 (addr 2) disconnected ugen0: detached uhub0: device problem, disabling port 1 Linux is a bit more elaborative on error reporting: hub.c: new USB device 00:02.3-1.1, assigned address 5 usb.c: USB device not accepting new address=5 (error=-32) hub.c: new USB device 00:02.3-1.1, assigned address 6 usb.c: USB device not accepting new address=6 (error=-32) It looks really as if the IO drivers on this end are burned. Unfortunately the device is one of those melded in soft PVC kind of, so I can't open it for further investigation. Hmm I may try anyway with a knife out of couriosity... It certainly started during the experimentation on the BSD side. But I did feed all data through udbp0: and never used ugen0 devices. It's really just a bit curious now.