now using hardy beta with 2.6.24-15-generic. (see also bug #212888 for more details/logs) atdt911 (ori-ab) wrote on 2008-04-08: #17 forgot to add that in my previous H/W configuration (nforce2 chipset) i Some USB ports didn't work (as if they didn't exist). 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 No one else seems to have discovered this, I've been reading other posts talking about unloading modules, and many other more complicated troubleshooting methods and fixes when I found your page. navigate here
USB has an over-current protection, which gets triggered when power consumption from the port is too high. bill about 3 years ago Thanks for this too!! I often have problems with my USB ports - they don't detect my USB mouse. Jacob Buscher 3 months ago Thanks you so much! https://ubuntuforums.org/showthread.php?t=797789
I plug some in, and get those "device descriptor read/64, error #" messages, yet, without doing anything to the system and using the same usb cable, I can plug in any Steve7233 March 5, 2016 at 22:41 Even with sudo I get permission denied! Share this:EmailMorePrintTwitterFacebookLinkedInGoogleReddit Related This entry was posted in Linux, Tips and tagged Errors on June 26, 2008 by Guy. I alsouse the same microSD card on both systems.What can cause this error?
about 1 year ago Thanks, helped me to safe a lot of time! I saved the BIOS (never updated) with the dafault settings and I have never modify any parameters in the GRUB. Last edited by flogger; 29th December 2014 at 06:18 PM. Kernel Usb 5 2 Device Descriptor Read 64 Error 71 I had a logitech USB keyboard on a ThinkPad T420 and apart from the lower right USB port all others threw this error.
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. Juan jose 3 months ago ¡¡Muchas gracias!! It would be nice to discover the reason, not because of the price of a new keyboard but just for learning. https://access.redhat.com/solutions/676683 dardino over 4 years ago some one knows how to fix the problem without rebooting?
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 Usb Device Not Accepting Address Error 71 Can we sort these into other bugs and attempt to triage them, rather than having a giant metabug? If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. It's a good example of why looking through unanswered posts is a good way to kill time when you're bored.
USB-Interfaces don't work. Shev77 about 3 years ago Thank you very much! Usb Device Descriptor Read 64 Error 71 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 2 1 Device Descriptor Read 64 Error 71 Both too much and not enough information.
Thanks anyway - good to see that someone is looking through all the unanswered threads. check over here Michael Schwartzkopff (misch) wrote on 2009-02-05: #42 Hi, I see the same errors here on my notebook (kernel 2.6.27-11) when I connect my usb mouse. I've had the issue on the HP since Karmic -- Intrepid and Jaunty worked OK, so I consider this a regression on that machine. Report a bug This report contains Public information Edit Everyone can see this information. Usb 5 2 Device Descriptor Read 64 Error 71
Whoever knows what that is could post that and we would have a better solution. Affecting: linux (Ubuntu) Filed here by: atdt911 When: 2008-04-08 Assigned: 2015-07-20 Completed: 2011-07-19 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Leave a Reply Cancel reply Your email address will not be published. his comment is here To visualize it, think of IRQ as single lane road that is shared by 2 trucks, if one truck misbehaves or breaks down there the authority blocks the road and those
Update Thu 25 Dec 13:32:24 HST 2014 I realized something, this may be hardware related so before you try anything see if USB devices are being listed Code: $ lsusb Bus Device Descriptor Read/64 Error 32 Journal recovered, inodes number corrected, and after a 2 second wait my drive was read. My workaround has been to add "nomodeset" parameter to kernel boot parameters.
also get this message shortly after each bootup. Comment 4 Pete Zaitcev 2007-01-12 15:45:30 EST It was suggested that such things happen during the port sharing between ehci and uhci. done.
Enabling unmasked SIMD FPU exception support... Usb Error Codes 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.
Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Until recently I operated with a single external USB disk in one of the ports, which works fine. Makes sense that it was an over-currenting problem. weblink Seemingly reloading the module (scsi_mod) does not cause the new configuration to take hold.
chivi 11 months ago Nice short article. The device in question, so far as I can tell, is my internal USB card-reader (its activity light is going like gangbusters). Comment 6 Harald Braun 2007-01-21 14:15:42 EST I think, the bug cannot be closed. I also have seen this same problem on other computers.
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 I'd like to see USB2.0 speeds again... Turned it back on, checked dmesg and... Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 4128760k swap on /dev/VolGroup00/LogVol01.
Thanks! Thank you very much!!! Code blocks~~~ Code surrounded in tildes is easier to read ~~~ Links/URLs[Red Hat Customer Portal](https://access.redhat.com) Learn more Close Hello, I'm Paul. 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
sorted it, can't remember how though. Paul Philippov over 1 year ago Jesper, I guess that in order to be reset by the peer the connection has to be initiated by the host first. We Acted. gracias sensei!!!
i tried connecting it to different ports with no success. USB lights are not lit when connected to front USB ports. Using 3 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 80000000 (gap: 7ffff000:7ec01000)
Detected 2785.203 MHz processor.
Built 1 zonelists. sometimes it works, but sometimes it won't accept address and i get "device descriptor read/64, error -110".
Jeffrey Lebowski 3 months ago And sorry for all the typos... will smith about 5 years ago God bless you!