Date: Mon, 04 Feb 2013 15:20:48 -0600 From: Karl Denninger <karl@denninger.net> To: freebsd-stable@FreeBSD.org Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... Message-ID: <51102630.9030509@denninger.net> In-Reply-To: <1360012382.93359.489.camel@revolution.hippie.lan> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/4/2013 3:13 PM, Ian Lepore wrote: > On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: >> On 2/4/2013 2:06 PM, Ian Lepore wrote: >>> On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: >>>> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD >>>> 9.1-STABLE #16 r244942 >>>> >>>> and it returns.... >>>> >>>> ugen4.4: <vendor 0x0409> at usbus4 >>>> uhub6: <vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 4> >>>> on usbus4 >>>> uhub_attach: port 1 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 2 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 3 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 4 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 5 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 6 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 7 power on failed, USB_ERR_STALLED >>>> uhub6: 7 ports with 7 removable, self powered >>>> >>>> Yuck. >>>> >>>> The last time it was working was on a FreeBSD 7 box (yeah, I know, >>>> rather old) but I never had problems there. And it appears that all of >>>> the device declarations that I used to have to put in the kernel as >>>> non-standard stuff are now in GENERIC, so I would expect it to work. >>>> >>>> Ideas as to what may have gotten hosed up here? >>>> >>> Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. >>> >>> FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and >>> 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's >>> parts program different vendor/product info and IDs have to be added to >>> code to recognize them, that's the only trouble one usually encounters. >>> >>> -- Ian >> Well, that sorta kinda worked. >> >> Except that it still is identifying it as a hub too, and the two collide >> and crash the stack. >> >> But I can't find anything that is looking at the PID (0x0050) or the >> definition (HUB_0050) anywhere in the code. >> >> I'll go pull the NEC defs and set up something else instead of simply >> adding it to the FTDI probe list. >> > It seems to me you have a problem with a hub (perhaps the root hub or a > motherboard hub if you don't have an external one) and this has nothing > to do with the ftdi device at all. Or the usb serial device is damaged > somehow so that the vendor and product ID are reading as garbage and > being mistaken for a hub. > > Have you tried the ftdi adapter on another port/hub/computer? Have you > tried plugging something else into the port you're trying to use for the > ftdi adapter, like a thumb drive or something? > > -- Ian The machine is fine. The adapter is fine too -- I powered up the old machine and it works too, and recognizes the adapter immediately (on FreeBSD-Stable 7.) No problems with either. I get identical behavior on multiple ports on the back of the machine and the machine itself is known to be ok and has a USB KVM attached to it which is working, along with a USB-communicating UPS which is also working. When I added the definition it picked it up as an 8-port adapter with 8 FTDI ports on it, but then it ALSO tried to attach it as a 7-port hub (which is what usbdevs says it is) -- although I cannot find ANYWHERE in the code under that directory that references that VID/PID tuple. The second attachment attempt blew up the first (which makes sense.) Since the code obviously does know how to find hubs, there has to be something else going on -- digging through it now to see if I can isolate how it determines something is a "hub" without having a structure with all the hubs defined in it, which I cannot find. -- -- Karl Denninger /The Market Ticker ®/ <http://market-ticker.org>; Cuda Systems LLC
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51102630.9030509>