USB device not accepting address: error -110
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Fedora) |
Won't Fix
|
Medium
|
|||
linux (Ubuntu) |
Won't Fix
|
Medium
|
KAPIL DUBEY | ||
linux-source-2.6.15 (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Binary package hint: linux-image-
I have a USB devices: mouse, camera, ipod and printer plugged in. The only device that works is the printer. Everything used to work in 2.6.15-25-k7. Mouse works with PS2 converter but not straight into USB.
**lsusb output:
Bus 004 Device 001: ID 0000:0000
Bus 001 Device 003: ID 03f0:7204 Hewlett-Packard DeskJet 36xx
Bus 001 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
**dmesg output:
[17355309.768000] usb 4-2: device not accepting address 78, error -110
[17355309.880000] usb 4-2: new high speed USB device using ehci_hcd and address 79
[17355320.304000] usb 4-2: device not accepting address 79, error -110
[17355320.552000] usb 4-5: new high speed USB device using ehci_hcd and address 80
[17355332.116000] usb 4-5: device not accepting address 80, error -110
[17355332.228000] usb 4-5: new high speed USB device using ehci_hcd and address 81
[17355343.792000] usb 4-5: device not accepting address 81, error -110
[17355343.908000] usb 4-5: new high speed USB device using ehci_hcd and address 82
[17355354.340000] usb 4-5: device not accepting address 82, error -110
[17355354.456000] usb 4-5: new high speed USB device using ehci_hcd and address 83
[17355364.892000] usb 4-5: device not accepting address 83, error -110
[17355365.140000] usb 4-2: new high speed USB device using ehci_hcd and address 84
description: | updated |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dean (dean-s-wood) wrote : | #1 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Luke Hoersten (lukehoersten) wrote : | #2 |
Dean, do you have any more resources of information about this problem? Can you list what devices you were trying to mount? I find it very strange that my printer still works but mouse, camera, ipod, and usb key do not.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Luke Hoersten (lukehoersten) wrote : | #3 |
Now none of my USB devices work, not even my printer.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Chuck Short (zulcss) wrote : | #4 |
Please attach the output of dmesg as an attachment.
Thanks
Chuck
Changed in linux-source-2.6.15: | |
importance: | Untriaged → Medium |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dean (dean-s-wood) wrote : Re: [Bug 54273] Re: USB device not accepting address: error -110 | #5 |
Hi,
Please find attached a copy of dmesg. I tried it twice and have attached
both as they appear slightly different whendetecting the usb hub but I
don't know enough to tell if this is relevant.
The second one also contains the repeated error message which is sent.
Thanks
Dean
On 20/08/06, ChuckShort <email address hidden> wrote:
>
> Please attach the output of dmesg as an attachment.
>
> Thanks
> Chuck
>
> ** Changed in: linux-source-2.6.15 (Ubuntu)
> Importance: Untriaged => Medium
>
> --
> USB device not accepting address: error -110
> https:/
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Gustavo Azambuja (gazambuja) wrote : | #6 |
- sudo dmesg > /home/gustavo/dmesg.txt Edit (14.6 KiB, text/plain)
I have similar problem, the camera USB: work, the pendrive: not work.
-My system:
gustavo@gustavo:~$ uname -a
Linux gustavo 2.6.15-26-386 #1 PREEMPT Thu Aug 3 02:52:00 UTC 2006 i686 GNU/Linux
gustavo@gustavo:~$ lspci
0000:00:00.0 Host bridge: Silicon Integrated Systems [SiS] 651 Host (rev 02)
0000:00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge)
0000:00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS962 [MuTIOL Media IO] (rev 25)
0000:00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
0000:00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
0000:00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0)
0000:00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
0000:00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
0000:00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
0000:00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
0000:00:0f.0 Communication controller: Agere Systems V.92 56K WinModem (rev 03)
0000:01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760/761 PCI/AGP VGA Display Adapter
-The syslog:
gustavo@gustavo:~$ sudo tail /var/log/syslog
Aug 23 09:26:41 localhost kernel: [85687.276188] usb 3-3: new high speed USB device using ehci_hcd and address 6
Aug 23 09:26:41 localhost kernel: [85687.387994] usb 3-3: device descriptor read/64, error -32
Aug 23 09:26:41 localhost kernel: [85687.603635] usb 3-3: device descriptor read/64, error -32
Aug 23 09:26:42 localhost kernel: [85687.819276] usb 3-3: new high speed USB device using ehci_hcd and address 7
Aug 23 09:26:42 localhost kernel: [85687.931089] usb 3-3: device descriptor read/64, error -32
Aug 23 09:26:42 localhost kernel: [85688.146733] usb 3-3: device descriptor read/64, error -32
Aug 23 09:26:42 localhost kernel: [85688.362371] usb 3-3: new high speed USB device using ehci_hcd and address 8
Aug 23 09:26:42 localhost kernel: [85688.769678] usb 3-3: device not accepting address 8, error -32
Aug 23 09:26:43 localhost kernel: [85688.881505] usb 3-3: new high speed USB device using ehci_hcd and address 9
Aug 23 09:26:43 localhost kernel: [85689.288818] usb 3-3: device not accepting address 9, error -32
Attach dmesg.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Gustavo Azambuja (gazambuja) wrote : | #7 |
ok, ok, I'm stupid, after write the comment, i search more info and find this:
http://
Q: Why doesn't USB work at all? I get "device not accepting address".
A: This can be one of several problems:
* High speed devices sometimes have problems with cables used to connect them. They're more sensitive to signal quality issues than older usb 1.1 full or low speed devices. If the device works OK at full speed on the same system, after you "rmmod ehci-hcd", this is likely the problem you're seeing. There are a lot of things you can do to change signal quality........ [cont]
with this simple test "rmmod ehci-hcd" my pendrive USB work fine!!!
ok, good luck for all, and look the FAQ ;)
PD: sorry for my english (i'm spanish speaker)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Luke Hoersten (lukehoersten) wrote : | #8 |
Thanks for the advice. I will try this but I'm not sure this is the problem because *all* of my USB devices do not work so I know its not a problem with the cable quality. It may be a hardware bus problem but when I tried the 686 kernel instead of the k7 kernel, the errors do not occur and all my USB devices work fine.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
QuinnHarris (ubuntu-quinnh) wrote : | #9 |
USB worked fine in 2.6.15-25-386 but no longer int 2.6.15-26-386 and edgy 2.6.17-7-386.
"rmmod ehci_hcd" does allow USB devices to work at 1.1 speeds.
This appears to be a duplicate of bug #24925
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joel Oliver (joelol75) wrote : | #10 |
Confirming as well. I believe it is a problem with the BIOS in my case as I cannot mount 2 different USB devices in WinXP (Dual boot, no I never really use XP) and these work fine on my other Edgy system. One is a 80GB hard drive usb and the other is a ATI remote wonder. WinXP sees them right off the bat and says they are 'MALFUNTIONING' and to replace them. The device name usually pops up, doesn't get the name though....
System is GigaByte GA-M55plus-S3G (F6 BIOS)
Athlon 64x2 4200+ (32bit Edgy)
Integrated Geforce6100
NForce 430
I believe the 6100/430 part is the important one as my 'google' research shows this problem all over with 6100/6150 on ASUS boards as well.
Things I tried:
modprobe -r ehci_usb
Change usb 2.0 to 1.1 in bios (Changed error messages)
Found F7 BIOS update (12/21/06 release)
Booting with the irqpoll noapic nolapic acpi=off options (In various combos and created a keyboard that doubles everything i type.
Before the changes I get:
[ 85.867469] ohci_hcd 0000:00:0b.0: wakeup
[ 86.251175] usb 2-1: new full speed USB device using ohci_hcd and address 2
[ 86.435057] usb 2-1: device descriptor read/64, error -110
[ 86.722452] usb 2-1: device descriptor read/64, error -110
[ 87.002272] usb 2-1: new full speed USB device using ohci_hcd and address 3
[ 87.186153] usb 2-1: device descriptor read/64, error -110
[ 87.473969] usb 2-1: device descriptor read/64, error -110
[ 87.753792] usb 2-1: new full speed USB device using ohci_hcd and address 4
[ 88.169514] usb 2-1: device not accepting address 4, error -110
[ 88.345406] usb 2-1: new full speed USB device using ohci_hcd and address 5
[ 88.761134] usb 2-1: device not accepting address 5, error -110
[ 136.218973] usb 2-7: new full speed USB device using ohci_hcd and address 6
[ 136.402352] usb 2-7: device descriptor read/64, error -110
[ 136.690166] usb 2-7: device descriptor read/64, error -110
[ 136.969985] usb 2-7: new full speed USB device using ohci_hcd and address 7
[ 137.153870] usb 2-7: device descriptor read/64, error -110
[ 137.441683] usb 2-7: device descriptor read/64, error -110
[ 137.721499] usb 2-7: new full speed USB device using ohci_hcd and address 8
[ 138.137226] usb 2-7: device not accepting address 8, error -110
[ 138.313118] usb 2-7: new full speed USB device using ohci_hcd and address 9
[ 138.728844] usb 2-7: device not accepting address 9, error -110
[ 139.032652] usb 2-8: new full speed USB device using ohci_hcd and address 10
[ 139.216537] usb 2-8: device descriptor read/64, error -110
[ 139.504347] usb 2-8: device descriptor read/64, error -110
[ 139.784166] usb 2-8: new full speed USB device using ohci_hcd and address 11
[ 139.968048] usb 2-8: device descriptor read/64, error -110
[ 140.255861] usb 2-8: device descriptor read/64, error -110
[ 140.535682] usb 2-8: new full speed USB device using ohci_hcd and address 12
[ 140.951408] usb 2-8: device not accepting address 12, error -110
[ 141.127300] usb 2-8: new full speed USB device using ohci_hcd and address 13
[ 141.543040] usb 2-8: device not accepting address 13, error -110
After update:
[17180154.220000] ohci_hcd 0000:00:0b.0: wakeup
[17180188.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
nassausky (nassausky) wrote : | #11 |
Found out it's probably an internal cabling problem (maybe noise interference going to the front or faulty ports) Plugged my usb thumbdrive into the rear port and it now works.
My suggestion is if nothing else works, try something simple like this.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Luke Hoersten (lukehoersten) wrote : | #12 |
Changing ports and devices does not work. It happens with all of them. On the other hand, I did notice that this only happens when my iPod is plugged in on boot. I've tried different cables with the same problem and it happens on any port. There is no problem if I simply boot without my iPod.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Tero Karvinen (karvinen+launchpad) wrote : Mobo USB ports work after BIOS update | #13 |
My problem was bypassed by updating BIOS and using USB ports on the motherboard. At least the USB drive was automatically mounted after that.
I had the "not accepting address: error" on both freshly installed Gutsy and a previous Ubuntu release. Probably all Ubuntus after some kernel version were affected. I also have seen this same problem on other computers. Before finding a bypass, I had tried many solutions proposed in this bug and many similar USB mounting bugs in Launchpad.
To bypass the problem
0) Prequisites: I had Ubuntu 7.10 Desktop amd64, motherboard Intel Guardfish dq695gf with BIOS 5773. Problem: USB key is not mounted when connected, but it prints some lines to syslog and dmesg.
1) BIOS Update: Downloaded latest BIOS update 6002 CO6002P.ISO from Intel, burned to CD. USB related updates were mentioned in BIOS release notes. Updated BIOS. Booted.
2) Mobo ports: Connected USB stick to motherboard USB port on the back of the computer.
3) Success: Rythmbox "Music Player" automatically started. I could play music from the USB stick. Thus, the problem was bypassed.
4) Side effects: Front USB ports don't work at all anymore, and no lines are printed to dmesg or syslog when USB stick is connected. USB lights are not lit when connected to front USB ports.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Andreas Warberg (andreas-warberg) wrote : | #14 |
- dmesg_dell_inspiron_5100.txt Edit (22.5 KiB, text/plain)
I have this issue on a Dell Inspiron 5100 with latest BIOS.
It has two high-speed usb ports. Until recently I operated with a single external USB disk in one of the ports, which works fine.
I tried adding an extra usb disk but it fails with the same message. The first usb disk continues to work, however.
I have attached my dmesg output.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Buzz (buzz-piersol) wrote : | #15 |
I am still using "sudo modprobe -r ehci_hcd" in order to use my USB flash drives.
from my dmesg:
=======
[15571.551295] usb 1-2: new high speed USB device using ehci_hcd and address 3
[15581.914390] usb 1-2: device not accepting address 3, error -110
[15582.026381] usb 1-2: new high speed USB device using ehci_hcd and address 4
[15592.445060] usb 1-2: device not accepting address 4, error -110
[15592.557054] usb 1-2: new high speed USB device using ehci_hcd and address 5
[15599.457827] usb 1-2: device not accepting address 5, error -110
[15599.569817] usb 1-2: new high speed USB device using ehci_hcd and address 6
[15606.471610] usb 1-2: device not accepting address 6, error -110
=======
also recently updated my BIOS to the latest version.
also get this message shortly after each bootup. Wonder if it's related:
=======
[ 292.819263] irq 7: nobody cared (try booting with the "irqpoll" option)
=======
I haven't used "irqpoll" but from what I've read it is used when a system is really broken. However, I do use "noapic" as a boot option.
Just wondering why this bug still exists as I have seen reports back to 05? I'd like to see USB2.0 speeds again...
Buzz
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
atdt911 (ori-ab) wrote : | #16 |
I'm having this problem on my wi-fi usb dongle (zd1201 chipset).
sometimes it works, but sometimes it won't accept address and i get "device descriptor read/64, error -110".
I recently upgraded my H/W (p35+ich9) and it became worse - i can now get the device working only if is connected before boot, and even then
it sometimes fails with this error. i tried connecting it to different ports with no success.
had this problem ever since feisty on all kernels. now using hardy beta with 2.6.24-15-generic.
(see also bug #212888 for more details/logs)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
atdt911 (ori-ab) wrote : | #17 |
forgot to add that in my previous H/W configuration (nforce2 chipset) i solved this problem by unplugging then plugging the device back again.
unfortunately it doesnt work with my new H/W config.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
sniffy (konwal1) wrote : | #18 |
I solved the problem on my Desktop-PC by shutting down and unplugging the PC for a while to become unloaded.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Cleber Santz (clebersantz) wrote : | #19 |
I have the same here, i try to plug my phone Sony K790 (work fine until kernel 2.6.24-16-generic) and lsusb return only laptop cam
$ lsusb
Bus 005 Device 002: ID 0c45:62c0 Microdia
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
$ uname -a
Linux clbr 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Cleber Santz (clebersantz) wrote : | #20 |
My Kingstop 1GB pendrive works fine
$ lsusb
Bus 005 Device 005: ID 13fe:1d00 Kingston Technology Company Inc. DataTraveler 2.0 1GB Flash Drive
Bus 005 Device 002: ID 0c45:62c0 Microdia
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Leann Ogasawara (leannogasawara) wrote : | #21 |
Hi Guys,
This appears to be a duplicate of bug 88746. Care to take a look? I realize it's a rather long thread but I'd draw your attention to https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pete Deremer (sportman1280-deactivatedaccount) wrote : | #22 |
[100008.464546] Buffer I/O error on device sdb2, logical block 532
[100008.464548] lost page write due to I/O error on sdb2
[100008.464555] Buffer I/O error on device sdb2, logical block 532
[100008.464557] lost page write due to I/O error on sdb2
[100008.466165] Buffer I/O error on device sdb2, logical block 1
[100008.466168] lost page write due to I/O error on sdb2
[152280.623453] sudo[5532]: segfault at 00000000 eip 080529ee esp bff10860 error 4
[152280.643581] sudo[5534]: segfault at 00000000 eip 080529ee esp bfb5dcb0 error 4
[152280.662175] sudo[5536]: segfault at 00000000 eip 080529ee esp bf80c160 error 4
[157245.524620] usb 3-1.1: new full speed USB device using uhci_hcd and address 7
[157245.608578] usb 3-1.1: device descriptor read/64, error -71
[157245.796484] usb 3-1.1: device descriptor read/64, error -71
[157245.972398] usb 3-1.1: new full speed USB device using uhci_hcd and address 8
[157246.056358] usb 3-1.1: device descriptor read/64, error -71
[157246.248263] usb 3-1.1: device descriptor read/64, error -71
[157246.424177] usb 3-1.1: new full speed USB device using uhci_hcd and address 9
[157246.834572] usb 3-1.1: device not accepting address 9, error -71
[157246.907941] usb 3-1.1: new full speed USB device using uhci_hcd and address 10
[157247.318314] usb 3-1.1: device not accepting address 10, error -71
jderemer@player:~$
A little different but still same issue with not getting the address
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | New → Triaged |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
sin (sinsinapsi-gmail) wrote : | #23 |
Sorry, I think i've have à similar bug,
I've problems with wifi usb "hercules" Guillemot.inc
usb 2.0 802.11g -support 802.11b
sometimes wifi don't work and i get this error
usb 2-1: device descriptor read/64, error -62
[ 24.654600]usb 2-1: device descriptor read/64, error -62
[ 24.654600]usb 2-1: new full speed USB device using ohci_hcd and address 4
[ 24.654600]usb 2-1: device not accepting address 4, error -62
[ 24.830432] usb 2-1: new full speed USB device using ohci_hcd and address 5
[ 25.238037] usb 2-1: device not accepting address 5, error -62
I'm note sure that it's a similar or related problem because I cannot find anybody that have "error -62"
in his output
so i cannot find help anymore.
I hope
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Meltedfusion (emmanuelvlz) wrote : | #24 |
I too have the same usb issue. I have a toshiba laptop running 8.04 LTS 64 bit edition not only does my wifi not work but the 4 USB ports do not work with my thumb drive or mobile phone. However i have a built in USB camera that seems to be recognized. The Dmsg is as follows:
395.053061] APIC error on CPU1: 00(40)
[ 395.053830] APIC error on CPU0: 00(40)
[ 680.494599] usb 1-1: new high speed USB device using ehci_hcd and address 5
[ 686.874851] usb 1-2: new high speed USB device using ehci_hcd and address 6
[ 692.442643] usb 1-3: new high speed USB device using ehci_hcd and address 7
[ 700.383035] usb 1-3: device descriptor read/64, error -110
[ 707.197979] usb 1-3: device descriptor read/64, error -110
[ 707.276424] usb 1-3: new high speed USB device using ehci_hcd and address 8
[ 713.971754] usb 1-3: device descriptor read/64, error -110
[ 720.577415] usb 1-3: device descriptor read/64, error -110
[ 720.655849] usb 1-3: new high speed USB device using ehci_hcd and address 9
[ 724.444208] usb 1-3: device not accepting address 9, error -110
[ 724.484889] usb 1-3: new high speed USB device using ehci_hcd and address 10
[ 730.422046] usb 1-3: device not accepting address 10, error -110
[ 744.426693] APIC error on CPU1: 40(40)
[ 744.428187] APIC error on CPU0: 40(40)
[ 883.423210] APIC error on CPU0: 40(40)
[ 883.421546] APIC error on CPU1: 40(40)
[ 953.627798] APIC error on CPU1: 40(40)
[ 953.629581] APIC error on CPU0: 40(40)
As i started looking through the dmseg i noticed this...
libata version 3.00 loaded.
[ 22.690860] usbcore: registered new device driver usb
[ 22.690938] ahci 0000:00:12.0: version 3.0
[ 22.690974] ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 22 (level, low) -> IRQ 22
[ 22.691200] ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit
[ 22.691206] ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP
[ 22.693798] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
[ 23.690280] ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
Im green to this so please excuse me if i put info in there that shouldnt be there.
The USB ports on my desktop seem to work fine front and back. I am running 8.04 LTS x86 on there and everything seems to be running fine. I'm going to try that on here and if it works i will post the update.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
reliable-robin-22 (nicolasdiogo) wrote : | #25 |
Hi,
i would like to add my voice to this chorus.
i have a laptop t61p lenovo that can not access a Corsair usb flash pen 8gb (flash voyager)
but on the same port i can use a sandisk 4gb without any problem.
another anomaly is that when i first received this pen drive with default format it worked fine.
but it now fails after i formatted using mkfs.vfat.
hope this helps to understand what is wrong.
Nicolas
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
lanzen (lanzen) wrote : | #26 |
I've just run into this bug.
Since a couple of days I've been trying to recover data from my notebook HD and for that purpose I got an empty usb box but ubuntu would not see it.
[ 9374.869868] usb 1-6: new high speed USB device using ehci_hcd and address 4
[ 9375.017124] usb 1-6: configuration #1 chosen from 1 choice
[ 9375.017014] scsi7 : SCSI emulation for USB Mass Storage devices
[ 9375.034946] usb-storage: device found at 4
[ 9375.034950] usb-storage: waiting for device to settle before scanning
[ 9380.033730] usb-storage: device scan complete
[ 9385.625628] usb 1-6: reset high speed USB device using ehci_hcd and address 4
[ 9395.862983] usb 1-6: reset high speed USB device using ehci_hcd and address 4
[ 9401.088551] usb 1-6: reset high speed USB device using ehci_hcd and address 4
[ 9416.181806] usb 1-6: device descriptor read/64, error -110
[ 9431.369147] usb 1-6: device descriptor read/64, error -110
Browsing around I eventually ended up here http://
modprobe -r ehci_hcd worked and I am now backing up.
[ 9955.313973] usb 2-5: new full speed USB device using ohci_hcd and address 4
[ 9955.530717] usb 2-5: configuration #2 chosen from 1 choice
[ 9955.557642] scsi8 : SCSI emulation for USB Mass Storage devices
Distributor ID: Ubuntu
Description: Ubuntu 8.04.1
Release: 8.04
Codename: hardy
2.6.24-21-generic #1 SMP Tue Aug 12 13:03:01 UTC 2008 x86_64
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
jacobS (jacsalomon) wrote : | #27 |
This bug continue in Hardy, in my case the USB 2.0 work fine, but if I plug a Low Speed Usb (such a mouse) the system refuses to accept adress.
Note: This not occurn in Hardy under a system with USB 1.1
Distributor ID: Ubuntu
Description: Ubuntu 8.04.1
Release: 8.04
Codename: hardy
Linux pentium4-desktop 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Leann Ogasawara (leannogasawara) wrote : | #28 |
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:
1) If you are comfortable installing packages on your own, the linux-image-
--or--
2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://
Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
EAB (adair-boder) wrote : | #29 |
I solved this issue by changing the USB cable. It must have been defective. :)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
chrono13 (chrono13) wrote : | #30 |
Possible duplicate: bug 261710
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jayotis Diggory (jayotis-d) wrote : | #31 |
Confirmed controller handoff problems between ehci_hcd & uhci_hcd causing
device descriptor read/64, error -71
device not accepting address 2, error -71
Intrepid kernel 2.6.27-3 seems to have corrected the error on this system.
error 110 looks to be a hardware connection issue, from what I've been reading in other website posts while searching for error 71. But defiantly give Intrepid a try before switching cable/ports and cold boots.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
jcasanov (jcasanov) wrote : | #32 |
I just installed ubuntu intrepid with kernel 2.6.27-* and error remains... (see bug 261710)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
harvest316 (harvest316) wrote : | #33 |
I can confirm that a cold boot rectifies this.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
harvest316 (harvest316) wrote : | #34 |
FYI: I have a Dell Dimension 5100 with a Samsung USB Memory Card Reader, and I'm on Intrepid 2.6.27.9.13
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
chrono13 (chrono13) wrote : | #35 |
A solution (increasing the timout) per Mario Italo, bug 261710 worked for me.
1. Always back up config files before editing them:
sudo cp /etc/modprobe.
Now open /etc/modprobe.
sudo gedit /etc/modprobe.
2. Add the line:
options scsi_mod inq_timeout=20
and save the file.
Seemingly reloading the module (scsi_mod) does not cause the new configuration to take hold. What worked for both he and I was to reinstall the kernel.
3. Type uname -a and take note or memorize the exact kernel version numer you are using.
4. Use the above kernel number to reinstall your kernel. For me it was:
sudo aptitude reinstall linux-image-
This will take a couple of minutes.
5. Reboot and test. This fixed it for Mario and has worked great for me. Note that there is probably a better way to make the new configuration take effect other the reinstalling the kernel. Whoever knows what that is could post that and we would have a better solution.
This confirms that the bug is just that the device does not wake up quickly enough. These instructions are for anyone who has these key(s) and is receiving the -110 (and possibly other) errors while attempting to use them.
A test to see if the above fix will fix your problem is to insert the key, and shut down the machine. Start it back up, if it recognizes the drive and mounts it (or lets you mount it), then the above steps should fix the bug and allow you to use the key normally.
Good luck, and thanks again to Mario Italo.
Solution originally found in report of bug 261710 (Corsair Flash Voyager 8GB USB key causes device descriptor read/64, error -110)
Posted this solution to bug 54273 (USB device not accepting address: error -110)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
zasq (zasq) wrote : | #36 |
Hi.
I use intrepid with 2.6.27-9-generic kernel on dell inspiron 1501 with the same problem. The workaround from Mario and chrono13 didn't work for me. I found this message in dmesg after doing it:
hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
What does that mean?
As it might be connected to this problem, let me tell you that I also have the following bugs:
https:/
(MP-BIOS bug: 8254 timer not connected to IO-APIC"
https:/
("Aperture beyond 4GB. Ignoring." message when booting)
https:/
(Re: ehci_hcd module causes I/O errors in USB 2.0 devices)
Devices like my printer or wd passport external hdd keep crashing. When I try to mount them again after such crashing (or just after having them unmounted manually before), they won't work anymore. I have to restart the whole system. Everything seems to be connected to an apic-error. (I need apic, so the option -noapic won't do. Besides, the problem should be solved and not hidden).
As it also might be a bios problem: I have the latest version of bios 2.6.3 .
Please let me know if you need more information.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Launchpad Janitor (janitor) wrote : Kernel team bugs | #37 |
Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Richard Ayotte (rich-ayotte) wrote : | #38 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Richard Ayotte (rich-ayotte) wrote : | #39 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Mary Gardiner (puzzlement) wrote : | #40 |
In some ways, there seem to be two problems here:
1. some people get these error messages, and their hardware doesn't work
2. some people get the "unable to enumerate USB device" warnings, but their hardware does work. Leann Ogasawara notes at https:/
However, in case #2 there is still a problem from an end-user point of view: the error message is logged to syslog once a second. This is undesirable for all kinds of reasons, disk use, annoyance if I have to give syslog to someone for *real* hardware problems, etc. The logging of this error should be radically reduced, I'd really prefer, say, once an hour to once a second.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Mark Stosberg (markstos) wrote : | #41 |
I had a laptop that suddenly started to the exhibit the error
"USB device not accepting address: error -110". A reboot did not seem to fix it, but a cold boot did. (I turned it all the way off, removed all devices from it, and briefly even removed the battery).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Michael Schwartzkopff (misch) wrote : | #42 |
Hi,
I see the same errors here on my notebook (kernel 2.6.27-11) when I connect my usb mouse.
When I remove uhci_hcd and reload it I get the error:
(...)
Feb 5 09:14:44 mucnb004 kernel: [ 1544.101840] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00003040
Feb 5 09:14:44 mucnb004 kernel: [ 1544.101840] usb usb4: configuration #1 chosen from 1 choice
Feb 5 09:14:44 mucnb004 kernel: [ 1544.101840] hub 4-0:1.0: USB hub found
Feb 5 09:14:44 mucnb004 kernel: [ 1544.101840] hub 4-0:1.0: 2 ports detected
Feb 5 09:14:44 mucnb004 kernel: [ 1544.120415] usb 2-2: device descriptor read/64, error -71
Feb 5 09:14:45 mucnb004 kernel: [ 1544.350616] usb 2-2: device descriptor read/64, error -71
Feb 5 09:14:45 mucnb004 kernel: [ 1544.640077] usb 2-2: new low speed USB device using uhci_hcd and address 3
Feb 5 09:14:45 mucnb004 kernel: [ 1544.760085] usb 2-2: device descriptor read/64, error -71
Feb 5 09:14:45 mucnb004 kernel: [ 1544.990109] usb 2-2: device descriptor read/64, error -71
Feb 5 09:14:45 mucnb004 kernel: [ 1545.220099] usb 2-2: new low speed USB device using uhci_hcd and address 4
Feb 5 09:14:46 mucnb004 kernel: [ 1545.640089] usb 2-2: device not accepting address 4, error -71
Feb 5 09:14:46 mucnb004 kernel: [ 1545.760124] usb 2-2: new low speed USB device using uhci_hcd and address 5
Feb 5 09:14:46 mucnb004 kernel: [ 1546.180100] usb 2-2: device not accepting address 5, error -71
Feb 5 09:14:46 mucnb004 kernel: [ 1546.180174] hub 2-0:1.0: unable to enumerate USB device on port 2
Feb 5 09:14:46 mucnb004 kernel: [ 1546.300113] usb 3-2: new full speed USB device using uhci_hcd and address 2
Feb 5 09:14:47 mucnb004 kernel: [ 1546.420116] usb 3-2: device descriptor read/64, error -71
Feb 5 09:14:47 mucnb004 kernel: [ 1546.450023] uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
Feb 5 09:14:47 mucnb004 kernel: [ 1546.450023] uhci_hcd 0000:00:1d.1: host controller halted, very bad!
Feb 5 09:14:47 mucnb004 kernel: [ 1546.450023] uhci_hcd 0000:00:1d.1: HC died; cleaning up
Feb 5 09:14:47 mucnb004 kernel: [ 1546.530137] hub 3-0:1.0: cannot reset port 2 (err = -19)
Feb 5 09:14:47 mucnb004 kernel: [ 1546.530173] hub 3-0:1.0: cannot disable port 2 (err = -19)
Feb 5 09:14:47 mucnb004 kernel: [ 1546.530218] hub 3-0:1.0: cannot reset port 2 (err = -19)
Feb 5 09:14:47 mucnb004 kernel: [ 1546.530237] hub 3-0:1.0: cannot disable port 2 (err = -19)
Feb 5 09:14:47 mucnb004 kernel: [ 1546.530257] hub 3-0:1.0: cannot reset port 2 (err = -19)
Feb 5 09:14:47 mucnb004 kernel: [ 1546.530275] hub 3-0:1.0: cannot disable port 2 (err = -19)
Feb 5 09:14:47 mucnb004 kernel: [ 1546.530296] hub 3-0:1.0: cannot reset port 2 (err = -19)
Feb 5 09:14:47 mucnb004 kernel: [ 1546.530314] hub 3-0:1.0: cannot disable port 2 (err = -19)
Feb 5 09:14:47 mucnb004 kernel: [ 1546.530330] hub 3-0:1.0: unable to enumerate USB device on port 2
Feb 5 09:14:47 mucnb004 kernel: [ 1546.530345] hub 3-0:1.0: cannot disable port 2 (err = -19)
Only a shutdown and restart of my notebook helps.
Michael.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Juan J. Martínez (jjmartinez) wrote : | #43 |
I have the same problem (error -71) with a Novatel Wireless 3G Broadband Modem (MC950D).
$ uname -a
Linux osvlap01 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.10
Release: 8.10
Codename: intrepid
[ 1029.860065] usb 4-2: new full speed USB device using uhci_hcd and address 29
[ 1029.984056] usb 4-2: device descriptor read/64, error -71
[ 1030.204185] usb 4-2: device descriptor read/64, error -71
[ 1030.420178] usb 4-2: new full speed USB device using uhci_hcd and address 30
[ 1030.540176] usb 4-2: device descriptor read/64, error -71
[ 1030.772055] usb 4-2: device descriptor read/64, error -71
[ 1030.985305] usb 4-2: new full speed USB device using uhci_hcd and address 31
[ 1031.396169] usb 4-2: device not accepting address 31, error -71
[ 1031.508166] usb 4-2: new full speed USB device using uhci_hcd and address 32
[ 1031.916165] usb 4-2: device not accepting address 32, error -71
[ 1031.916211] hub 4-0:1.0: unable to enumerate USB device on port 2
All the USB devices I have work OK.
My hardware is a Dell XPS M1330.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Rich (rincebrain) wrote : | #44 |
This seems to have devolved into a metabug - people are posting here with all kinds of USB errors, regardless of whether they match the original error code.
Can we sort these into other bugs and attempt to triage them, rather than having a giant metabug? Some of these may be machine-specific (e.g. the bug with some older ThinkPads and overdrawing the USB ports causing permanent damage), and others may just be damaged hardware, but it's clear that they're not all the same bug.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Greg J Preece (greg-preece) wrote : | #45 |
Hi all. I've been having the error -110 problem in Ubuntu Jaunty when using a CoolerMaster Xcraft 360 caddy with a standard SATA drive in it. If I boot into Ubuntu and try to mount the drive, I can't. I get a series of USB errors followed by the -110 error, as shown here.
However, I have found a slightly odd workaround. If I boot into Windows, mount the drive, then reboot into Ubuntu, the drive appears as normal, and works fine. If I un-mount the drive and try to re-mount it, I get the error again.
This leads me to believe it might have something to do with the way Ubuntu unmounts drives. Can't be certain, though, but I thought this might be a useful hint.
Changed in linux-source-2.6.15 (Ubuntu): | |
status: | New → Won't Fix |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#57 |
This is to reopen bug 446845 which was closed as fc9, when the problem is noted as still occurring. we could not get the original reporter to update the version
Description of problem:
After updating to kernel 2.6.25.
"hub 1-0:1.0: unable to enumerate USB device on port 3"
is being shown during boot.
This was indeed working prior to fc9, but stopped working and has never started working. This is both a message and an actual bug issue. At least for me my usb hardware worked prior to fc9 and then stopped at the same time that this message showed up and has never started working again.
Version-Release number of selected component (if applicable):
kernel 2.6.25.
How reproducible:
Always
Steps to Reproduce:
1. Boot kernel 2.6.25.
2.
3.
Actual Results:
Message on boot "hub 1-0:1.0: unable to enumerate USB device on port 3"
Expected Results:
Boot without this boot warning message. Enumerate USB problem solved.
Additional info:
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#58 |
Just checked this yet again. At present with kernel-
Bus 001 Device 009: ID 0424:2228 Standard Microsystems Corp. 9-in-2 Card
Reader
Bus 001 Device 008: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 006: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
With the device removed the message does not appear.
The USB slot on the device works. The card reader does not, with known-working cards. It did work, under F8:-(.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
zizo_halo (zizo-halo) wrote : | #46 |
this is what i get when i try to boot the live cd of ubunto 9.04 which prevent me from using this os in my desktop....
[56.932010] usb 1-2: device not accepting adress 5, error -110
[56.932073] hub 1-0: 1.0: unable to enumerate usb device on port 2
i wonder if the reason is from the processor since it's intel core 2 quad 2.4 GHZ???????????????
anyway what i notice that my keyborad and the the mouse turn off when the booting of ubunto starts!!!!!!!!!!
somebody plz help???
I'm average user not expert
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
eyrieowl (eyrieowl) wrote : | #47 |
- uname, version signature, lsusb, dmesg Edit (254.9 KiB, text/plain)
I'm gettting the "unable to enumerate error" in a brand new build of 9.10, AMD 64. The attached file contains uname, version signature, lsusb, dmesg. It's definitely a problem. The device in question, so far as I can tell, is my internal USB card-reader (its activity light is going like gangbusters). I recognize that this particular bug report is problematic due to it's meta-bug nature, but please don't lose sight of the fact that there are some real issues at work.
Thanks.
Changed in linux (Fedora): | |
status: | Unknown → Confirmed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Lucas C. (lucasoptura) wrote : | #48 |
For those guys at the end of their pitiful ropes...
My Sony Vaio was effected by this after an upgrade to 2.6.31-14-generic and I tried every suggestion from this site and ubuntuforums, long story short, the ultimate fix was to unplug my machine, remove the battery and go play guitar for 30 minutes. So, just in case you aren't doing that because you think that can't possibly be the problem (like I did), do it anyway. You may save yourself some time. I'm back to work now.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#59 |
Created attachment 375395
Usefull?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#60 |
I've been having this problem for years and it's a major pita.
Currently on F12, kernel-
The most annoying thing is that /var/log/messages is constantly being pumped full of this stuff making the log file useless.
dmesg is also full of this rendering it useless, see attached.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#61 |
Still a problem in fc12
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#62 |
This prevents my USB mouse from working and is a PITA. I use a KVM switch and need a mouse for everything else and then another mouse just for this machine running FEDORA/ Is it hard to fix?
Steve
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#63 |
There's no "this" that prevents your mouse from working, Steve. There's
a reason, but most likely it's different from Ray's or anyone else.
You should've filed your own bug, but no problem, I am going to clone
the bug for you.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#64 |
See bug 544368 for KVM (srb's problem).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#65 |
Interesting. I would wonder if "Need Real Name" doesn't indeed have the same problem. Ever since this problem showed up I have not been able to use usb devices on this machine. In this case all I have tried are flash drives. I end up having to put them in other machines and then cross mount them to use them.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#66 |
I am going from the statement that his USB mouse is not working.
I did try a USB mouse that works on my other machines during fc10 and it also fails. Have not tired it fc11 or fc12. Have not yet tried any flash drives fc12.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#67 |
See, this confuses me too much. Maybe it's just a duff HC, I cannot tell.
Steve's issue seems more precisely defined, so I can attack it.
If you can isolate the problem somehow, I or someone else may be able
to look at it.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#68 |
Thanks Pete and sorry for the incorrect report. I will follow up on #544368 with more specifics. Plus I will update my profile with a real name :-)
Steve Bourne
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#69 |
Well what do we need to do to define this better?
Right now I have one machine with this problem.
The same exact hardware worked/and still works fine under Unbuto(sp) in another location, but if they load fedora they get the same exact problem.
If I only have one hard drive and no cdrom on the machine this message goes away.
When the message is there USB devices don't work.
When the message is there USB devices which charge from the power lines will not charge.
If the message is not there the devices work fine and charge fine.
The good news on this is that while this is a production system it is the server which manages all of our backups so if you need me to take if off line for testing something this is very possible.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#70 |
I get this "unable to enumerate" message in /var/log/messages because of (I think) a card reader built in to my computer. I never need to use it, and I think it doesn't work. That's not a big deal to me. But like comment #3, it's pretty annoying that the error is being written to the file 3-4 times a second, endlessly. It'd be much better if it was written once at boot time, and maybe if the user tries to access the device (if possible). As it is, after a week my messages file is over 150 MB because of this. Should this constant writing be (or is it already) its own bug...? Thanks.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
iulian (iulian-ghinea) wrote : | #49 |
A solution for my case:
I have a scanner: HP Scanjet 4370 and it was not recognized by th system.
Errors that i received:
[486806.248034] usb 3-1: new low speed USB device using uhci_hcd and address 101
[486806.660012] usb 3-1: device not accepting address 101, error -71
I mention that I keep the scanner was always powered up - before and after the system was up.
Ubuntu didn't recognized it at all. After reading this thread I trid something and it worked:
I unpluged the power cord from the usb, waited few seconds and plugged it again. And then I received in dmesg:
[488990.724018] usb 1-4: new high speed USB device using ehci_hcd and address 6
[488990.874654] usb 1-4: configuration #1 chosen from 1 choice
Now the sanner was recognized and it works fine.
Thank you all for involving and for suggestions!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen) wrote : | #50 |
iulian is right.
This is all related to POWER.
I had the same problem with a powered USB hub.
It didn't work (and made lsusb hang!) and gave the same -110 error in dmesg
Until I removed the power from the usb-hub and plugged it in again.
At that point the usb-hub still worked for my mice, (but not my external HD, because that required more power).
Then I could turn the power on and the hub kept working and the drive also started to work.
I've had a similar problem with my printer, which made Ubuntu not boot at all in the past, if it was turned on when booting.
But it wasn't until I had this issue with the hub (that works both with and without power) than I could see that enumaration fails on powered USB devices if they were powered on during boot.
SO, dear Kernel developers (that are no longer reading this bug, from what I gather) .. the issue is:
USB devices that are externally powered, block usb enumeration, if you attach them with the power plugged in.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#71 |
This bug seams "live and kicking" still on Fedora 12 with kernel 2.6.31.
I tried to use external 160GB Imation device with Toshiba HDD and just got bunch of "unable to enumerate USB device on port" lines and the HDD didn't mount :(
After plugging it in windows machine it mounted the HDD without any issue, so I guess this is linux kernel issue and not device related issue.
This external USB HDD case has usb cable with two male USB-A connectors (one used for power+data and other used only for power) on one side and USB mini-A connector on other side.
I figured out that I could try to plug it in one USB-A to USB hub and give it powert via other USB-A directly from other USB port on laptop.
This works, and I don't get "unable to enumerate USB device on port" errors.
Do you need more info regarding my devices used, logs, or any other info?
Is this bug likely to be solved any time soon or is it too hard even for the most hard core kernel hackers? ;)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#72 |
I don't think a kernel hacker can fix insufficient power issues, no matter
how hardcore he or she is.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#73 |
The problem is not that there is insufficient power, but that the operating system is for some reason detecting insufficient power when indeed there is plenty of power. In fact in my case it detects insufficient power with no devices at all attached to the USB system and then disables the USB system. This is also a problem which windows and Ubuntu does not experience on exactly the same hardware. Also if I do have a device like a flash drive plugged into a USB port it is functional up until this error is experienced.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#74 |
Pete you missed the point, the same drive attached in the same way works when using windows, but fails when using ubuntu and fedora. Is this the same bug or should I report new one? And how come the same drive is connected over USB HUB there is no issue?!?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#75 |
In my case it works under ubuntu or at least it did last time I checked.
It has been commented that this is a very nonspecific error with many many causes. It sounds like maybe some kind of additional information about which thing caused this error in this case is in order.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#76 |
When I got this drive it was formated in fat32, I connected it to my friend's (2-3 years old) laptop running ubuntu 8.10, and using only ONE USB-A connection (data+power), other wasn't used. Drive worked without any issues.
I used mkfs.ext3 to format it and gave it to my friend to use it for a few days.
Next day he said the drive is "dead" but actually he was having "unable to enumerate USB device on port" issues now, even when using both USB-A connectors.
After taking 2.5" hdd drive out of it's original enclosure and using other one drive worked just fine (this was tested on my Fedora 12 laptop).
I haven't tested other enclosure + older ubuntu laptop.
This is all a mystery to me. Hope this additional information makes some sense to somebody, because it sure doesn't to me.
Changed in linux (Ubuntu): | |
status: | Triaged → Confirmed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#77 |
# uname -a
Linux nx7300 2.6.32.
# dmesg
hub 1-0:1.0: unable to enumerate USB device on port 6
hub 1-0:1.0: unable to enumerate USB device on port 6
hub 1-0:1.0: unable to enumerate USB device on port 6
hub 1-0:1.0: unable to enumerate USB device on port 6
hub 1-0:1.0: unable to enumerate USB device on port 6
Any updates regarding this bug?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#78 |
I can confirm this bug on Fedora 13 with 2.6.33.3-85 kernel.
I testet this issue on few different laptops, when booting into Windows on those same laptops USB HDD is recognized without problems and device works.
This is Linux kernel bug.
Do you need more feedback from me? How can I help so that this bug gets fixed sooner?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#79 |
Actually this appears to be a bug in the fedora distribution.
As you say the devices work in windows. They also work under other distributions.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#80 |
The device which caused the problem for me was a USB card reader, in the end I bought another one which has worked fine under Fedora. I'd be willing to donate my old problematic card reader to the cause if its of any use.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#81 |
Created attachment 421785
/var/log/messages
I'm having this problem with my 'SanDisk Sansa e260'. I used to work in F11, then didn't work in the last few months. I just upgraded to F13, and it still isn't working.
I don't have a Windows computer to test this on, but I am fairly sure that the MP3 itself works just fine. It doesn't have any 'USB mode' settings, it just operates as as storage device.
I am not plugged in through a hub, nor are there many USB devices attached to the machine.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#82 |
I still have this issue with latest F13 updates. Is there anyway to troubleshoot and find which patch is causing this issue?
Kernel devels do you have a suggestion? Is there some kernel I can test and report back if this bug is fixed or present?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#83 |
I can confirm this bug on Fedora 13 on my Lenovo T61
# uname -a
Linux lenovot61 2.6.33.
# dmesg
hub 2-0:1.0: unable to enumerate USB device on port 1
usb 2-1: new high speed USB device using ehci_hcd and address 12
usb 2-1: New USB device found, idVendor=0781, idProduct=74d0
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: SanDisk Sansa Clip+
usb 2-1: Manufacturer: SanDisk
usb 2-1: SerialNumber: 710FFA194451B6A
scsi10 : usb-storage 2-1:1.0
btusb_intr_
btusb_bulk_
btusb_bulk_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#84 |
Still the case for kernel version 2.6.33.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
L3ttuce (ifearx) wrote : | #51 |
I'm on Ubuntu Karmic 2.6.31-22-generic #60-Ubuntu SMP Thu May 27 00:22:23 UTC 2010 i686 GNU/Linux, on an Eee PC 1000H. Periodically and seemingly randomly, my internal bluetooth adapter will exhibit the above symptoms, and sytem logs will show messages along the lines of:
63.509374] usb 5-1: device descriptor read/64, error -110
The only modules loaded are usbhid and btusb.
I'm using Blueman to manage my bluetooth devices. The problem most usually occurs after I disable the adaptor, then re-enable it again with blueman's tray applet. No amount of fussing with services or modules or rebooting brings it back.
The only thing that appears to work consistently, so far is to power off the laptop, and remove the battery for a couple of seconds/minutes, plugging it back in and rebooting. I tried restarting dbus as well, but some rather nasty (unrelated) things happen after this, and I usually have to REISUB.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#85 |
Created attachment 446698
/var/log/messages
My MP3 players works again with kernel 2.6.34.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#86 |
I can confirm this. My player seems to be fully functional on 2.6.34.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#87 |
I don't think this will ever be fixed in F12.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ryan Fugger (rfugger) wrote : | #52 |
I have this problem on two laptops: a HP 530 and a Compaq CQ61, when plugging in my Sansa Clip music player, and also several times with external hard drives. My usb memory stick works fine, so I suspect that it only affects powered devices, as mentioned above.
I've had the issue on the HP since Karmic -- Intrepid and Jaunty worked OK, so I consider this a regression on that machine. I wondered if it was just flaky USB hardware, but now I have a new Compaq and it suffers the same issue. I reinstalled Windows on the HP, and now the Sansa connects just fine, so it is definitely a problem with Linux.
I've just attached the player to a few different ports on my Compaq, with subtly different results in the logs, so I'm attaching them here.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ryan Fugger (rfugger) wrote : | #53 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix". | #54 |
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.
Changed in linux (Ubuntu): | |
status: | Confirmed → Won't Fix |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#88 |
This bug is still present in Fedora 16 and in Rawhide. Please reopen it and relabel it from F12 to Rawhide.
This is hardware related.
Intel Chipset drivers have some bug, because same external USB device works if I reboot into Windows or if I try it on other non-intel machines.
Mine Smolt profile:
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#89 |
Should I create a new bug report?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#90 |
I don't know if you need a new one or not. If you do create a new bug not it here, and reference this one and the previous one in the new bug. Which makes me think that this is redundant. I don't know that anyone working on the software is actually paying attention to these bugs.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#91 |
(In reply to comment #33)
> I don't know if you need a new one or not. If you do create a new bug not it
> here, and reference this one and the previous one in the new bug. Which makes
> me think that this is redundant. I don't know that anyone working on the
> software is actually paying attention to these bugs.
There are approximately 1000 open kernel bugs.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#92 |
Well at least we have a status report. It would be nice if even if nothing was happening on a bug because of this backlog that we get a comment from someone to this effect every six months or so.
Is there anything we can be doing to help track down this bug?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#93 |
(In reply to comment #35)
> Well at least we have a status report. It would be nice if even if nothing
> was happening on a bug because of this backlog that we get a comment from
> someone to this effect every six months or so.
>
> Is there anything we can be doing to help track down this bug?
Yes, actually.
Likely one of the most helpful things you can do is email the upstream linux-usb mailing list and report the issue to them. They are the domain experts and having them directly in contact with the people having the issue eliminates the middle-man.
Things to note in the email would be:
- USB controller/chipset
- What kind of devices present this error (usb id)
- Which kernel(s) exhibit the problem
Given that this bug seems to have been around for a really long time, that last question might be a bit difficult to answer.
If anyone gets responses from upstream, we can help build test kernels and patches if needs be. Just put a URL to the mailing list archive there in this bug.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#94 |
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#97 |
Ray, are you still seeing this on the current builds ?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#98 |
It is still present with Fedora 17 3.5.5-1.fc17.x86_64 #1 SMP Tue Oct 2 22:24:00 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#99 |
I added this workaround to stop the message.
cd /sys/bus/
for i in `ls -d 0000:00:*`;do echo $i > unbind;sleep 5; echo $i > bind; done
Bus 001 Device 003: ID 0409:0058 NEC Corp. HighSpeed Hub
Bus 005 Device 004: ID 0461:4d20 Primax Electronics, Ltd
Bus 007 Device 003: ID 045e:00f1 Microsoft Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 03f0:2b11 Hewlett-Packard PSC 2170 series
Bus 001 Device 005: ID 1c6b:a222 Philips & Lite-ON Digital Solutions Corporation
Bus 001 Device 006: ID 0c45:184c Microdia VoIP Phone
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
00:00.0 Host bridge: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port (rev 13)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 13)
00:02.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 2 (rev 13)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13)
00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 13)
00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 13)
00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 13)
00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 13)
00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4
00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5
00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6
00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1
00:1c.2 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 3
00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1
00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2
00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3
00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller
00:1f.3 SMBus: Intel Corporation 82801JI ...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#100 |
Workaround did not work
(In reply to comment #42)
> I added this workaround to stop the message.
>
> cd /sys/bus/
> for i in `ls -d 0000:00:*`;do echo $i > unbind;sleep 5; echo $i > bind; done
>
>
> Bus 001 Device 003: ID 0409:0058 NEC Corp. HighSpeed Hub
> Bus 005 Device 004: ID 0461:4d20 Primax Electronics, Ltd
> Bus 007 Device 003: ID 045e:00f1 Microsoft Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 004: ID 03f0:2b11 Hewlett-Packard PSC 2170 series
> Bus 001 Device 005: ID 1c6b:a222 Philips & Lite-ON Digital Solutions
> Corporation
> Bus 001 Device 006: ID 0c45:184c Microdia VoIP Phone
> Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>
>
> 00:00.0 Host bridge: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port
> (rev 13)
> 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root
> Port 1 (rev 13)
> 00:02.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root
> Port 2 (rev 13)
> 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root
> Port 3 (rev 13)
> 00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root
> Port 7 (rev 13)
> 00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management
> Registers (rev 13)
> 00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad
> Registers (rev 13)
> 00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS
> Registers (rev 13)
> 00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev
> 13)
> 00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
> Controller #4
> 00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
> Controller #5
> 00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
> Controller #6
> 00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI
> Controller #2
> 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio
> Controller
> 00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express
> Root Port 1
> 00:1c.2 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express
> Root Port 3
> 00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
> Controller #1
> 00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
> Controller #2
> 00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
> Controller #3
> 00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI
> Controller #1
> 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
> 00:1f.0 ISA bridge: Inte...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#101 |
This bug appeared in kernel 3.5.5-1.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#102 |
Created attachment 623309
boot into recovery mode single user,
Latest kernel from update.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#103 |
suggest duplicate of 841738
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#104 |
I upgrade 3.5.6-1.fc17.x86_64 and I reattach the harddisk dock to the usb 3 port to get the error message to go away. I am now able to connect to the harddisk.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#105 |
I found a problem with usb3 sata docking station.
[ 1803.293840] JBD2: Error -5 detected when updating journal superblock for sdh1-8.
[ 1803.497225] usb 10-1: >new SuperSpeed USB device number 74 using xhci_hcd
[ 1803.510609] usb 10-1: >Parent hub missing LPM exit latency info. Power management will be impacted.
[ 1803.514364] usb 10-1: >New USB device found, idVendor=174c, idProduct=5106
[ 1803.514367] usb 10-1: >New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 1803.514368] usb 10-1: >Product: AS2105
[ 1803.514370] usb 10-1: >Manufacturer: ASMedia
[ 1803.514371] usb 10-1: >SerialNumber: 6VPHKLGG
[ 1803.515183] scsi24 : usb-storage 10-1:1.0
[ 1804.516773] scsi 24:0:0:0: >Direct-Access ST310005 24AS JC4B
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#106 |
# Mass update to all open bugs.
Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.
Please retest with this kernel, and let us know if your problem has been fixed.
In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with. Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.
If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem.
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#107 |
I met the alerts in all current Fedora 17 kernels when I have a remote keyboard and mouse and any other one usb device plugged in:
Bus 002 Device 004: ID 046d:c52e Logitech, Inc.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x046d Logitech, Inc.
idProduct 0xc52e
bcdDevice 23.01
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 59
bNumInterfaces 2
bConfigurat
iConfiguration 4
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 98mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 0
HID Device Descriptor:
bLength 9
bcdHID 1.11
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 8
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 0
HID Device Descriptor:
bLength 9
bcdHID 1.11
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#108 |
*** Bug 841738 has been marked as a duplicate of this bug. ***
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#109 |
Tested with kernel-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#110 |
(In reply to comment #49)
> # Mass update to all open bugs.
>
> Kernel 3.6.2-1.fc16 has just been pushed to updates.
> This update is a significant rebase from the previous version.
>
> Please retest with this kernel, and let us know if your problem has been
> fixed.
>
> In the event that you have upgraded to a newer release and the bug you
> reported
> is still present, please change the version field to the newest release you
> have
> encountered the issue with. Before doing so, please ensure you are testing
> the
> latest kernel update in that release and attach any new and relevant
> information
> you may have gathered.
>
> If you are not the original bug reporter and you still experience this bug,
> please file a new report, as it is possible that you may be seeing a
> different problem.
> (Please don't clone this bug, a fresh bug referencing this bug in the
> comment is sufficient).
Still happening on this kernel:
[chris@mythpiggy ~]$ uname -a
Linux mythpiggy 3.6.2-1.fc16.x86_64 #1 SMP Wed Oct 17 05:30:01 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[chris@mythpiggy ~]$ dmesg | more
[1118798.442395] hub 2-0:1.0: unable to enumerate USB device on port 8
[1118798.763054] hub 2-0:1.0: unable to enumerate USB device on port 8
[1118799.083728] hub 2-0:1.0: unable to enumerate USB device on port 8
,,,
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#111 |
The issue occurred on kernel-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#112 |
Latest kernel looks better:
[chris@mythpiggy ~]$ uname -a
Linux mythpiggy 3.6.5-2.fc16.x86_64 #1 SMP Thu Nov 1 03:49:27 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[chris@mythpiggy ~]$ dmesg | grep "unable to enumerate USB device"
[chris@mythpiggy ~]$
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#113 |
I can also confirm that my USB DAC now works with
Linux amd 3.6.5-1.fc17.x86_64 #1 SMP Wed Oct 31 19:37:18 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[ 1997.027722] usb 1-2: new high-speed USB device number 4 using ehci_hcd
[ 1997.144819] usb 1-2: config 1 has an invalid interface number: 3 but max is 2
[ 1997.144831] usb 1-2: config 1 has an invalid interface number: 3 but max is 2
[ 1997.144837] usb 1-2: config 1 has an invalid interface number: 3 but max is 2
[ 1997.144843] usb 1-2: config 1 has no interface number 1
[ 1997.145688] usb 1-2: New USB device found, idVendor=0644, idProduct=8038
[ 1997.145694] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1997.145700] usb 1-2: Product: TEAC USB AUDIO DEVICE
[ 1997.145704] usb 1-2: Manufacturer: TEAC
[ 1997.148991] input: TEAC TEAC USB AUDIO DEVICE as /devices/
[ 1997.149188] hid-generic 0003:0644:
[ 1997.185729] usbcore: registered new interface driver snd-usb-audio
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#114 |
Broken again in latest kernel:
Linux mythpiggy 3.6.6-1.fc16.x86_64 #1 SMP Mon Nov 5 16:56:43 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
dmesg output (partial)
[107902.444891] hub 2-0:1.0: unable to enumerate USB device on port 8
[107902.694623] hub 2-0:1.0: unable to enumerate USB device on port 8
[107902.944375] hub 2-0:1.0: unable to enumerate USB device on port 8
[107903.194115] hub 2-0:1.0: unable to enumerate USB device on port 8
[107903.443868] hub 2-0:1.0: unable to enumerate USB device on port 8
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#115 |
Still broken on latest kernel:
Linux mythpiggy 3.6.7-4.fc16.x86_64 #1 SMP Tue Nov 20 20:33:31 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[ 167.771290] hub 2-0:1.0: unable to enumerate USB device on port 8
[ 168.092018] hub 2-0:1.0: unable to enumerate USB device on port 8
[ 168.412681] hub 2-0:1.0: unable to enumerate USB device on port 8
[ 168.733344] hub 2-0:1.0: unable to enumerate USB device on port 8
[ 169.053976] hub 2-0:1.0: unable to enumerate USB device on port 8
[ 169.374652] hub 2-0:1.0: unable to enumerate USB device on port 8
[ 169.695325] hub 2-0:1.0: unable to enumerate USB device on port 8
Such brief respite in kernel 3.6.5-2
Now I'm getting hangs where Gnome Shell is unresponsive, Ctrl-Alt-F2 brings up a terminal but it's filled with endless "unable to enumerate USB device" messages, pumped out at about 3 every second.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#116 |
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#117 |
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Narcis Garcia (narcisgarcia) wrote : | #55 |
I had this problem with Ubuntu-Gnome 13.04 on a HP Pavilion g6 laptop. Some USB ports didn't work (as if they didn't exist).
My workaround has been to add "nomodeset" parameter to kernel boot parameters.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
penalvch (penalvch) wrote : | #56 |
n0PxN0p, please do not mark this report a duplicate of another, or vice versa as per https:/
Changed in linux (Ubuntu): | |
assignee: | nobody → KAPIL DUBEY (kapil08dubey-w) |
Changed in linux (Fedora): | |
importance: | Unknown → Medium |
status: | Confirmed → Won't Fix |
I have exactly the same problem. Printouts are identical.
Error messages stop when ehci_hcd is removed but am still unable to mount usb. I have looked around to find a solution and it seems this is a reasonably common problem.