On St, 2006-11-29 at 10:20 -0500, Alan Stern wrote:
> On Tue, 28 Nov 2006, Milan Plzik wrote:
>
> > Hello,
> >
> > I noticed that since upgrade (probably 2.6.17 to 2.6.18, but I'm not
> > sure - it might happen sooner), the USB bluetooth dongle stopped to work
> > correctly for the most of time - here is what happens and the device is
> > not recognized:
> >
> > usb 2-1: new full speed USB device using uhci_hcd and address 2
> > usb 2-1: device descriptor read/64, error -71
> > usb 2-1: device descriptor read/64, error -71
> > usb 2-1: new full speed USB device using uhci_hcd and address 3
> > usb 2-1: device descriptor read/64, error -71
> > usb 2-1: device descriptor read/64, error -71
> > usb 2-1: new full speed USB device using uhci_hcd and address 4
> > usb 2-1: device not accepting address 4, error -71
> > usb 2-1: new full speed USB device using uhci_hcd and address 5
> > usb 2-1: device not accepting address 5, error -71
> >
> > However, under some (not-yet-discovered) circumstanced I have been
> > able to get it working (it was after resuming and the dongle was already
> > inserted in USB port, but I'm not sure if this helped). USB dongle works
> > correctly on other system.
> >
> > The system is x86_64 gentoo with suspend2-sources-2.6.18 kernel
> > (basically vanilla one with just suspend2 patch). Test was done after
> > reboot, not resume. Dmesg output is below.
>
> These are exactly the error messages you would see if the USB hardware in
> your computer stopped working (either the controller itself or possibly
> the cables connecting the motherboard to the port in the case).
Well, this is a laptop:-), so ports should be connected and in the
same port, serial-to-usb adapter (some FTDI stuff) works correctly, as
USB flash disk does.
>
> Of course, they are also the error messages you would see if the USB
> dongle stopped working -- but you said that it does work on a different
> system.
Yes, even on the same, under some circumstances.
The system I have uses VIA chipset, which even before didn't like some
hardware, such as some PDAs, which simply did not get enumerated (both
windows and linux on both sides). So it even might be mixture of
hardware/software problem.
lspci says:
...
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
...
<just for record>
There is also another issue with similar symptoms, but with this one,
I can't guarrantee it is not mine faut. On ARM system, which has
embedded USB controller (OHCI in this case), I tried to fix the glue for
it (controller is on platform bus), but once everything was fixed, the
connected device (embedded wifi card, which worked in 2.4 series kernel
and even maybe with 2.6.13). The kernel is 2.6.16, but handhelds.org one
(though I guess usbcore doesn't have much reasons to be modified) - it
possibly could also be affected.
The controller seems to work correctly (OHCI takes care about
everything, glue just enables controller), but when I enable the wifi
adapter, I'm just getting -110 or -71 when reading from device (depends
on use_old_scheme_first), even during enumeration. But again, this might
or might not be related at all to it.
</just for record>
>
> Alan Stern
>
Milan Plzik
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
