svn commit: r186730 - in head: lib/libusb20 sys/dev/usb2/controller sys/dev/usb2/core sys/dev/usb2/ethernet sys/dev/usb2/image sys/dev/usb2/include sys/dev/usb2/serial sys/dev/usb2/sound sys/dev/us...

[Hans Petter Selasky]

On Tuesday 06 January 2009, Stanislav Sedov wrote:
> On Tue, 6 Jan 2009 12:43:03 +0300
>
> Stanislav Sedov <stas at FreeBSD.org> mentioned:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Tue, 6 Jan 2009 09:36:49 +0100
> >
> > Hans Petter Selasky <hselasky at c2i.net> mentioned:
> > > Hi,
> > >
> > > I'm trying to push these patches into -current. Can you tell us what
> > > CPU architecture you are using? And how much RAM?
> >
> > That will be nice to have these fixes in tree.
> > I'm using Core2Quad Q9400 w/ 4Gb RAM running amd64.
>
> BTW, I'm still experiencing problems with some kinds of devices.
> E.g. Anydata E100X modem (ubsa) fails to select configuration and
> attach both on amd64 and arm with following messages in the log.
>
>   usb2_alloc_device:1423: set address 2 failed (ignored)
>   usb2_alloc_device:1458: getting device descriptor at addr 2 failed!
>   usb2_req_re_enumerate:1362: addr=2, set address failed! (ignored)
>   usb2_req_re_enumerate:1375: getting device descriptor at addr 2 failed!
>   ugen0.2: <AnyDATA Corporation> at usbus0
>
> Do you by a chance know what is going on?

Hi,

As long as your device shows up like "ugen0.2" it is detected properly and 
will function. Check with "usbconfig".

Suggestions:

usbconfig -u 0 -a 2 reset
usbconfig -u 0 -a 2 dump_device_desc

The failures indicate that the firmware on your USB device is not reponding 
correctly at the time the set address command is being sent to the device.

As you can see the new USB stack will try to re-enumerate the device one time.

Have you loaded the correct driver for your serial device?

kldload usb2_serial_bsa

or

kldload usb2_serial_u3g

or

kldload usb2_serial_gensa

--HPS