Google
  Web www.spinics.net

Re: Device not accepting address, error -110 and others

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Hi Alan and others,

On Tue, Jul 13, 2010 at 5:35 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote:
> On Tue, 13 Jul 2010, Leandro Melo de Sales wrote:
>
>> Hi list,
>>     since I updated to some of new linux kernels versions, I started
>> to experimenting many problems with my usb devices / hub, which makes
>> my computer works in a very strange manner. Researching on this
>> direction on the web, I noticed that many people have the same/similar
>> problem as mine, where always linux kernel kprints the following
>> message to the dmesg output using this template: usb X-X: device not
>> accepting address XX, error -XXX.
>
> If you return to the older kernel version, do the problems go away?
>

Yes!

>>     Are kernel developers, mainly the usb team, aware of this problem?
>
> There's a usb team??  Where do I sign up to join?!  :-)
>

:p

> More seriously...  No, of course not -- how could anybody be aware of
> your problem before you tell us?
>

I have noticed many people having the same/similar problem, this is
why I thought kernel developers already know this issue.

>> What should I have to do to find a solution for my case? This is
>> happening with my laptop. I need to know if this could be a hardware
>> problem, because my laptop is still under guarantee and if it is a
>> hardware problem, I will contact the seller.
>>      Please, any suggestion/tip will be greatfully accepted. Thank you!
>
> If you test several USB devices, and they all work on different
> computers but fail on your laptop, then probably there's something
> wrong with the laptop.
>

I have only a usb mouse plugged, and even when I don't have any device
plugged I got the usb errors.

>> Kernel version:
>> # uname -a
>> Linux leandro-laptop 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11
>> 08:03:28 UTC 2010 x86_64 GNU/Linux
>>
>> Example of dmes output:
>>
>> [ 2029.790225] usb 7-1: new full speed USB device using uhci_hcd and address 10
>> [ 2044.910100] usb 7-1: device descriptor read/64, error -110
>> [ 2060.140082] usb 7-1: device descriptor read/64, error -110
>> [ 2060.370101] usb 7-1: new full speed USB device using uhci_hcd and address 11
>> [ 2075.492621] usb 7-1: device descriptor read/64, error -110
>> [ 2090.720082] usb 7-1: device descriptor read/64, error -110
>> [ 2090.950089] usb 7-1: new full speed USB device using uhci_hcd and address 12
>> [ 2101.370344] usb 7-1: device not accepting address 12, error -110
>> [ 2101.490132] usb 7-1: new full speed USB device using uhci_hcd and address 13
>> [ 2111.910085] usb 7-1: device not accepting address 13, error -110
>> [ 2111.910123] hub 7-0:1.0: unable to enumerate USB device on port 1
>> [ 2112.034915] usb 7-2: new full speed USB device using uhci_hcd and address 14
>> [ 2127.150161] usb 7-2: device descriptor read/64, error -110
>> [ 2142.380160] usb 7-2: device descriptor read/64, error -110
>> [ 2142.610230] usb 7-2: new full speed USB device using uhci_hcd and address 15
>> [ 2157.730188] usb 7-2: device descriptor read/64, error -110
>
> It's possible that this is caused by bad interrupt routing.  What shows
> up in /proc/interrupts?  You could try booting with "acpi=off" or
> "pci=noacpi" on the boot command line.
>

The current output for my /proc/interrupts are:

           CPU0       CPU1
  0:     659506     727717   IO-APIC-edge      timer
  1:          5      13186   IO-APIC-edge      i8042
  4:         29          8   IO-APIC-edge      serial
  8:          1          0   IO-APIC-edge      rtc0
  9:        625          4   IO-APIC-fasteoi   acpi
 12:       1211         53   IO-APIC-edge      i8042
 16:          1        160   IO-APIC-fasteoi   uhci_hcd:usb3
 18:     113023          1   IO-APIC-fasteoi   uhci_hcd:usb8
 19:          6        125   IO-APIC-fasteoi   ehci_hcd:usb1,
uhci_hcd:usb5, uhci_hcd:usb7
 21:          0          0   IO-APIC-fasteoi   uhci_hcd:usb4, mmc0
 22:        282       1590   IO-APIC-fasteoi   yenta, HDA Intel
 23:        307        303   IO-APIC-fasteoi   ehci_hcd:usb2,
uhci_hcd:usb6, ohci1394
 26:      53117       2097   PCI-MSI-edge      ahci
 27:          4       2608   PCI-MSI-edge      eth0
 28:      79216          5   PCI-MSI-edge      i915
 29:     120325     128748   PCI-MSI-edge      iwlagn
NMI:          0          0   Non-maskable interrupts
LOC:     729345     131170   Local timer interrupts
SPU:          0          0   Spurious interrupts
PMI:          0          0   Performance monitoring interrupts
PND:          0          0   Performance pending work
RES:      17109      17985   Rescheduling interrupts
CAL:        216        238   Function call interrupts
TLB:       1920       2141   TLB shootdowns
TRM:          0          0   Thermal event interrupts
THR:          0          0   Threshold APIC interrupts
MCE:          0          0   Machine check exceptions
MCP:         18         18   Machine check polls
ERR:          0
MIS:          0

Is it possible to take any conclusion for the content of my /proc/interrupts?

I tried to boot with "acpi=off" and later with "pci=noacpi" but the
errors continue... What error -110 means? any other clue?

> Or you could try using a 32-bit kernel instead of a 64-bit kernel.
>

Ok, will do. Thanks!

> Alan Stern
>
>

Leandro.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


B and H Foto and Electronics Corp.

[Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Free Online Dating]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Devices]     [Old Linux USB Devel Archive]

Add to Google Powered by Linux